priezm / ro-rail

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

System "Moving" (Behavior, Option) #22

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What feature would enhance usability or efficiency?
To add options:
 + In fight: 
        - Distance until Homunculus begins chasing owner.

 + Not in fight: 
        - Distance until Homunculus begins chasing owner

What steps would demonstrate the improvement granted by the recommended
feature?
1. More flexible and exact adjustment.
2. Homunculus will not stack and lag behind(I hope for it).
3. When Homunculus in fight, will allow to move to the alchemist on the big 
distance (for example to bring still the monster's) while Homunculus will 
continue fight.

What is the current behavior in the above situation?
Homunculus very often stack and lags behind the alchemist, even at rail_state 
["FollowDistance"] = 2

What revision of the product are you using?
"$Id: Version.lua 168 2010-05-12

What type of homunculus/mercenary are you using?
Vanilmirth

Please provide any additional information below.
Excuse for my English. I used the Online-translator Translate.ru

Original issue reported on code.google.com by rid.lin....@gmail.com on 8 Jun 2010 at 7:58

GoogleCodeExporter commented 8 years ago
I suggest to look realization of following in MirAI. When I use it, my homun 
stack or lags behind me 1 of 100 times, when I use RAIL - to my regret, 1 of 
2-3.
Again, excuse me for my awful English.

Original comment by rid.lin....@gmail.com on 29 Jun 2010 at 5:17

GoogleCodeExporter commented 8 years ago
I will look into the following system shortly. I may completely rewrite it 
again, if needed.

Original comment by faithful...@gmail.com on 8 Jul 2010 at 11:48

GoogleCodeExporter commented 8 years ago
I will implement a new option shortly, named BeginChaseDistance or similar, 
that will alllow you to override the distance at which the homunculus/mercenary 
begins running to the owner.

Original comment by faithful...@gmail.com on 21 Nov 2010 at 10:59

GoogleCodeExporter commented 8 years ago
Revision 188 adds an option BeginChaseDistance that allows specification of the 
number of tiles before the AI begins to chase after the owner. The default of 
-1 will calculate this based on MaxDistance and the movement speed of the 
owner. The minimum is FollowDistance and the maximum is MaxDistance.

Original comment by faithful...@gmail.com on 2 Dec 2010 at 6:01

GoogleCodeExporter commented 8 years ago
I make two movie's for compare:
1. As looks SystemMovements what I wished it to 
see.(http://narod.ru/disk/1285258001/ragexe%202010-12-12%2020-26-52-21.avi.AVI.h
tml and 
http://narod.ru/disk/1285207001/ragexe%202010-12-12%2020-29-05-57.avi.AVI.html)
2. As looks SystemMovements now. 
(http://narod.ru/disk/1285533001/ragexe%202010-12-12%2020-34-18-12.avi.AVI.html)

Whether probably to make as in first two movie's?

Original comment by rid.lin....@gmail.com on 12 Dec 2010 at 8:26

GoogleCodeExporter commented 8 years ago
With the latest revision, this behavior is possible. The following setting 
should set it as you wish:

rail_state["BeginFollowDistance"] = 8
rail_state["FollowDistance"] = 2
rail_state["IdleMovement"] = {}
rail_state["IdleMovement"]["BeginAfterIdleTime"] = 0
rail_state["IdleMovement"]["MoveType"] = "return"

Make sure that you update first, because I have only tested this with revision 
198. It may not work as intended with earlier versions.

Please tell me if that works as you want.

Original comment by faithful...@gmail.com on 14 Dec 2010 at 3:10

GoogleCodeExporter commented 8 years ago
Yaahhhooo!!!
Big Thanks. Works as I wanted. 
My <a href="/p/ro-rail/source/detail?r=199">revision - 199</a>

Original comment by rid.lin....@gmail.com on 14 Dec 2010 at 9:27