Allow homunculus to return to user after killing target.

[GoogleCodeExporter]

What feature would enhance usability or efficiency?
Have a function to allow the Homunculus to return to its owner after it kills a 
target

What steps would demonstrate the improvement granted by the recommended
feature?
1. Sometimes my homunculus gets sniped by a monster from off screen ,e.g. Orc 
Archers. Allowing the homunculus to return to the owner will draw the monster 
closer and thus within screen range and allowing the homunculus to fight back.
2. By having the homunculus next to the owner, it takes less time on average to 
reach the next target monster when it spawns. If the homunculus were 14 cells 
above you and a monster spawns 14 cells below you, the homunculus would have to 
travel all the way across the screen. Whereas if the homunculus were to return 
to its owner (when there is not monster), it would have to travel only 
half-screen.

What is the current behavior in the above situation?
Homunculus stays put after killing a monster either it be 4 cells away or 14 
cells away. It does not return to its owner. It will still aquire new targets 
from said spot normally.

What revision of the product are you using?
171 2010-06-19

What type of homunculus/mercenary are you using?
Vanilmirth

Please provide any additional information below.
There should be a function that by enabling it, the homunculus will return 
within range of 'follow distance' or a different 'set distance' entirely.

Original issue reported on code.google.com by HyperFr...@gmail.com on 22 Jul 2010 at 4:51

• Merged into: #4

[GoogleCodeExporter]

Look in statefile for strings

rail_state["IdleMovement"] = {}
rail_state["IdleMovement"]["BeginAfterIdleTime"] = 300
rail_state["IdleMovement"]["MoveType"] = "return"

Homunculus will return to your char.

Original comment by nierena...@gmail.com on 23 Jul 2010 at 11:40

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

It's here, but on another page of issues :) Issue 4.

>The first can take either "none" or "return", the second is the number of 
>milliseconds that RAIL needs to be idle before it will start the motion.

Not much documentation for now, let's hope that Wiki will grow bigger with 
time...

Original comment by nierena...@gmail.com on 26 Aug 2010 at 10:47

[GoogleCodeExporter]

Closing this issue, as a duplicate of issue 4. Thanks, nierenator, for helping 
out.

Original comment by faithful...@gmail.com on 2 Sep 2010 at 3:51

• Changed state: Duplicate