search

Yiyotop / ro-rail

Automatically exported from code.google.com/p/ro-rail
0 stars 0 forks source link

AI.lua cannot read or missing. #28

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1.Switch AI using /hoai
2.Logout-Login to do change.
3.Then crashes.

What is the expected outcome? What do you see instead?
Its supposed to use ro-rail AI's. It crashes my game.

What revision of the product are you using?
Revision 172

What type of homunculus/mercenary are you using?
All crash my game.

Please provide any additional information below.

Original issue reported on code.google.com by uFKd.CoD...@gmail.com on 11 Jul 2010 at 4:17

Attachments:

GoogleCodeExporter commented 8 years ago 
You should change the folder name to USER_AI

Original comment by simon.as...@gmail.com on 11 Jul 2010 at 5:50

GoogleCodeExporter commented 8 years ago 
Alright I tried that and it works fine. Thank you for the help.

Original comment by uFKd.CoD...@gmail.com on 11 Jul 2010 at 6:09

GoogleCodeExporter commented 8 years ago 
I am having the same problem, although when I tried changing the name of the 
folder, my game kept crashing regardless... On a private server, does that have 
something to do with it?

Original comment by sm.jent...@gmail.com on 13 Jul 2010 at 12:06

GoogleCodeExporter commented 8 years ago 
Let me see your the whole AI folder.

One of the problem can be that you don't have the default RO AI that is palced 
outside of the USER_AI folder. If you have this problem, download the default 
AI by Gravity through the file I attached.
This may or may not help you, giving more information will help.

I used it in private server too :)
works well though a little bit buggy.

Original comment by simon.as...@gmail.com on 13 Jul 2010 at 9:30

Attachments:

GoogleCodeExporter commented 8 years ago 
Got it fixed with those files, thanks for the help!

Original comment by sm.jent...@gmail.com on 13 Jul 2010 at 2:29

GoogleCodeExporter commented 8 years ago 
Thanks for answering these issue reports, simon. I'm closing this issue as 
problems have been resolved.

Original comment by faithful...@gmail.com on 16 Jul 2010 at 9:51