waypoints type="TRAVEL" not work

[zbynio]

instead of TRAVEL is to RUN the whole time
I think it does not wait for aggro and target selection
os.time not work?
The time format does not work in 100%
i check - if mob attacking - player.Battling=true

symptoms :

method: harvest(), harvest(id) and target_object(id)
waypoints type="TRAVEL"
1. character run and mob attacking - allways dont stop and message language[113]
2. character harvest and mob attacking - allways ignore mob and collection is not successful. After break harvest run to next waypoint and... read 1

[Valleyguy]

instead of TRAVEL is to RUN the whole time
I think it does not wait for aggro and target selection
os.time not work?
The time format does not work in 100%
i check - if mob attacking - player.Battling=true

symptoms :

method: harvest(), harvest(id) and target_object(id)
waypoints type="TRAVEL"
1. character run and mob attacking - allways dont stop and message language[113]
2. character harvest and mob attacking - allways ignore mob and collection is not successful. After break harvest run to next waypoint and... read 1

ok besides your English being terrible here i think what your asking is if you want your bot to fight and not run away change WAYPOINTS TYPE = Normal

[Administrator]

Waypoint type TRAVEL seams to be working as intended. RUN is the broken one. Or, at least, I believe we decided to keep them this way (though it has changed several times, so it's getting confusing). These problems should be fixed with r489, so update again.

TRAVEL does not fight back when under attack. This is typically used when mounted and traveling back to town.

RUN does not target enemies, but will fight back against aggressive targets.

[zbynio]

...your English being terrible here...
@Valleyguy sorry about that. My English is really terrible.

@Administrator
TRAVEL type previously allowed to move from point to point without catching mobs. However, when the figure was fastened it faced and fought. I understand that now it will operate type RUN?

edit
Yes.
Work fine
And again the sun is shining in collecting the herb... lalala
Thank you

[rock5]

Waypoint type TRAVEL seams to be working as intended. RUN is the broken one. Or, at least, I believe we decided to keep them this way (though it has changed several times, so it's getting confusing). These problems should be fixed with r489, so update again.

TRAVEL does not fight back when under attack. This is typically used when mounted and traveling back to town.

RUN does not target enemies, but will fight back against aggressive targets.

Why would you switch them for? And how will it work in v489?

[Administrator]

Why would you switch them for? And how will it work in v489?

RUN and TRAVEL were introducted at different times. The meaning of them changed when we added TRAVEL, and then things got switched around again at a later date.

They are, as of r489, as they "should" be. There was just a few bugs preventing RUN from working correctly, along with old (messed up) language strings which was causing confusion. RUN (as in run along the path; not run from enemies) will run through the path only stopping to fight off aggressive enemies, while TRAVEL travels without stopping.

[rock5]

RUN (as in run along the path; not run from enemies) will run through the path only stopping to fight off aggressive enemies, while TRAVEL travels without stopping.

I just created a new waypoint file and set it to "RUN" because I wanted it to "fight off aggressive enemies". While testing, a monster attacked me but my character ignored it. I tried "Travel" and when a monster attacked me it fought back.

So now it's back to the way I remember it?

Edit: I spoke too soon. It was ignoring the monster because it was harvesting an object. On further testing it fought back in both "RUN" and "TRAVEL" mode.

[Valleyguy]

RUN (as in run along the path; not run from enemies) will run through the path only stopping to fight off aggressive enemies, while TRAVEL travels without stopping.

I just created a new waypoint file and set it to "RUN" because I wanted it to "fight off aggressive enemies". While testing, a monster attacked me but my character ignored it. I tried "Travel" and when a monster attacked me it fought back.

So now it's back to the way I remember it?

Edit: I spoke too soon. It was ignoring the monster because it was harvesting an object. On further testing it fought back in both "RUN" and "TRAVEL" mode.

i did similar testing in my new 1-10 elf bot im trying to build here run works just fine it runs and fights back when aggroed travel ignored them all....and i died as a result of 10 boars eating at my lvl 10 elf... i dont see a problem with the current svn ... (current as of yesterdays update i did aug-18-2010)

[rock5]

I'm not sure if "run" is working as intended. I'm using "run" with one of my waypoint files. In some places the waypoints are far apart. I've noticed that when traveling between these waypoints it ignores the attacking mobs until it reaches the next waypoint. It can collect 2-3 mobs along the way.

Shouldn't it attack mobs as soon as they attack you while traveling between waypoints?

[Administrator]

Yeah, that's possible. I think it's because the first 1 or 2 seconds after leaving a waypoint, it won't check for valid targets or aggressive enemies. Any additional information you can provide would help.

[rock5]

Yeah, that's possible. I think it's because the first 1 or 2 seconds after leaving a waypoint, it won't check for valid targets or aggressive enemies. Any additional information you can provide would help.

I just did a test with 2 points about 30s apart and with many red mobs between. I even used the default profile. When moving to the next waypoint it ignored all mobs. It only attacked when it reached a waypoint.

[rock5]

Looks like an easy fix is to delete line 1627 of player.lua

Code: Select all

	 	    waypoint.Type ~= WPT_RUN  and	-- only stop if not waypoint type RUN

It attacks as soon as a mob attacks but I noticed something funny. After killing the first mob it returned to the first waypoint. Then headed to waypoint 2 again. It killed another mob on the way then head back to waypoint 1 again. It did this 3 times before it was able to pass the halfway mark. Then when it killed a mob it continued to the second waypoint. I'm not sure if this is working as intended but it looks funny and can waste a lot of time.

[rock5]

Looks like an easy fix is to delete line 1627 of player.lua

Code: Select all

	 	    waypoint.Type ~= WPT_RUN  and	-- only stop if not waypoint type RUN

I've added this change to rev 497.