Yiyotop / ro-rail

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

Level 10 archer mercenary appears unresponsive #52

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. When i go into orc dungeon with the mercenary it will just stand there and 
will not attack, move, use skills. Even manual trying to get it to attack or 
move will fail.
2. I just started using this AI the other day though so it could be user error 
on my part.
3.

What is the expected outcome? What do you see instead?
The mercenary should attack and use skills as expected

What revision of the product are you using?
202 i think, not quite sure where to find that.

What type of homunculus/mercenary are you using?
Level 10 Archer mercenary

Please provide any additional information below.
I have used the spear level 10 mercenary in payon dungeon and that has worked 
fine with the AI, not sure what the problem is here.

Original issue reported on code.google.com by travismo...@gmail.com on 4 Jan 2011 at 3:42

GoogleCodeExporter commented 8 years ago
It seems as though the level 10 archer mercenary is causing a Lua error in 
RAIL. (Once RAIL is loaded, it prevents Ragnarok from popping up the Lua error 
boxes. Instead it logs them to TraceAI.txt and restarts itself.) I can't 
simulate it outside of RO, and I don't have access to a level 10 archer 
mercenary to test within RO.

Please perform the following actions to help troubleshoot: turn on /traceai, 
try to use the level 10 archer mercenary, wait a minute or two, and then attach 
the TraceAI.txt file to this issue.

Thanks in advance.

Original comment by faithful...@gmail.com on 5 Jan 2011 at 4:25

GoogleCodeExporter commented 8 years ago

Original comment by travismo...@gmail.com on 9 Jan 2011 at 4:17

Attachments:

GoogleCodeExporter commented 8 years ago
Thanks for reporting this. It should be fixed in revision 206. Please update 
your copy and verify that it works now.

Original comment by faithful...@gmail.com on 9 Jan 2011 at 4:57

GoogleCodeExporter commented 8 years ago
it is fixed, thank you

Original comment by travismo...@gmail.com on 12 Jan 2011 at 8:00