rail_state["AssistOptions"]["Other"] = "avoid" in homu statefile changes

Yiyotop / ro-rail

Automatically exported from code.google.com/p/ro-rail

0 stars 0 forks source link

rail_state["AssistOptions"]["Other"] = "avoid" in homu statefile changes #54

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago

What steps will reproduce the problem?
1. As you recommend in Wiki, I set in both homu and merc state-files: 
rail_state["AssistOptions"]["Other"] = "avoid".
2. But, when I relog my alchemist in RO, that option in homu statefile changes 
to "indifferent". Merc statefile not changes.

What is the expected outcome? What do you see instead?
I wish that both homu and merc were attacking different targets.
Instead, both merc and homu attacking same target.
What revision of the product are you using?
R205

What type of homunculus/mercenary are you using?
Vanilmirth, Archer 9 level.

Please provide any additional information below.
-

Original issue reported on code.google.com by nierena...@gmail.com on 9 Jan 2011 at 6:25

GoogleCodeExporter commented 8 years ago

I can't reproduce this. Can you try making the change before starting Ragnarok, 
to verify that the state-file is not being overwritten by your homu before you 
relog?

Original comment by faithful...@gmail.com on 12 Jan 2011 at 4:41

Changed state: Pending

GoogleCodeExporter commented 8 years ago

OK, I'll do it on weekend.

Original comment by nierena...@gmail.com on 13 Jan 2011 at 11:58

GoogleCodeExporter commented 8 years ago

[deleted comment]

GoogleCodeExporter commented 8 years ago

Did a test today - nothing changes in both files. Maybe it was my own error in 
configuration.
I changed file for homu before starting RO and it works OK.
But both of them (homu and archer) keep attacking same targets anyway. Don't 
know, maybe wrong settings somewhere ...
Maybe there is no issue, then. Sorry for bothering you.

Original comment by nierena...@gmail.com on 15 Jan 2011 at 7:40

GoogleCodeExporter commented 8 years ago

Avoid doesn't completely restrict the AI from attacking the same target. If 
there are no other potential targets, they will still attack the same target. 
It should take effect when there are many monsters on the screen (that would 
not be kill stealing). If it still doesn't work as intended, please open a new 
issue.

Original comment by faithful...@gmail.com on 15 Jan 2011 at 7:56

Changed state: Invalid