Harvest bot targeting everything ... ?

[copenhagen69]

First off ... yes i have it set up as a travel path and yes it worked fine before this weeks patch...
i am trying to run my harvest bot in the noob zone and it targets every animal out there. I had to add them to my friends list so i wont attack them. a few of my buddies are also having this problem in higher level zones. Our paths worked just fine before the Runes patch tuesday and the rom update today. i was just wondering if anyone else is having this problem or knows how to fix it.

should we just remake the paths since there has been a lot of new updates? or is it just a little bug that is gonna be worked out soon?

thanks

[Administrator]

I believe this bug is a result in one of the recent patches by d003232. Thanks for the report. It will be looked at and hopefully will result in a fix within the next day or so.

[copenhagen69]

I believe this bug is a result in one of the recent patches by d003232. Thanks for the report. It will be looked at and hopefully will result in a fix within the next day or so.

thanks for the great support and fast action as always!! you guys are great!

[d003232]

i am trying to run my harvest bot in the noob zone and it targets every animal out there. I had to add them to my friends list so i wont attack them.

Can you attach you profile to the post? I will then take a look. thx.

[copenhagen69]

Code: Select all

- <profile>
- <options>
  <option name="HP_LOW" value="85" /> 
  <option name="HP_LOW_POTION" value="40" /> 
  <option name="MP_LOW_POTION" value="50" /> 
  <option name="COMBAT_TYPE" value="melee" /> 
  <option name="COMBAT_DISTANCE" value="200" /> 
  <option name="ANTI_KS" value="true" /> 
  <option name="WAYPOINTS" value="Harvest2.xml" /> 
  <option name="RETURNPATH" value="Harvest2.xml" /> 
  <option name="PATH_TYPE" value="waypoints" /> 
  <option name="WANDER_RADIUS" value="500" /> 
  <option name="WAYPOINT_DEVIATION" value="5" /> 
  <option name="LOOT" value="true" /> 
  <option name="LOOT_TIME" value="2000" /> 
  <option name="LOOT_DISTANCE" value="100" /> 
  <option name="ENERGY_STORAGE_1" value="rage" /> 
  <option name="ENERGY_STORAGE_2" value="none" /> 
  <option name="POTION_COOLDOWN" value="15" /> 
  <option name="MAX_FIGHT_TIME" value="15" /> 
  <option name="DOT_PERCENT" value="90" /> 
  </options>
- <friends>
  <friend name="Fungus" /> 
  <friend name="Young Wolf" /> 
  <friend name="Young Bear" /> 
  <friend name="Wolf Cub" /> 
  </friends>
- <hotkeys>
  <hotkey name="HP_POTION" key="VK_MINUS" /> 
  <hotkey name="MP_POTION" key="VK_EQUAL" /> 
  <hotkey name="ATTACK" key="VK_1" /> 
  <hotkey name="RES_MACRO" key="VK_9" /> 
  </hotkeys>
  <skills /> 
  <onDeath>-- Additional Lua code to execute on death pauseOnDeath(); -- Stop the script</onDeath> 
  <onLeaveCombat>-- Additional Lua code to execute after killing an enemy</onLeaveCombat> 
  <onSkillCast>-- Additional Lua code to execute when casting a skill -- Note: arg1 contains the skill being used. -- i.e. arg1.Name will be the name of the skill being cast.</onSkillCast> 
  </profile>

[d003232]

I could not reproduce, what you describe. If you have a waypoint file type 'TRAVEL' it will never attack mobs by itself. To look for the reason, pls also post your waypoint file, or at least the first view lines.

Independent from that can you also prevent targeting with the options:

Code: Select all

	<option name="TARGET_LEVELDIF_BELOW" value="2" />
	<option name="TARGET_LEVELDIF_ABOVE" value="2" />

If you set both values to '0' it will only attack mobs of your own level. If you set both to '-1' it will attack nothing.

[Czachaaa]

I had that bug too, but i fixed it. Just change in your waypoint file at the beggining:
<waypoints>
to
<waypoints type="TRAVEL">

and it will be working fine

[copenhagen69]

first 13 lines of my harvest path ... worked just fine before the patches this week ...

Code: Select all

<waypoints>
	<!-- # 1 --><waypoint x="-3813" z="-8391" type="TRAVEL"></waypoint>
	<!-- # 2 --><waypoint x="-4029" z="-8461" type="TRAVEL">player:harvest();</waypoint>
	<!-- # 3 --><waypoint x="-4057" z="-8772" type="TRAVEL"></waypoint>
	<!-- # 4 --><waypoint x="-4057" z="-8772" type="TRAVEL"></waypoint>
	<!-- # 5 --><waypoint x="-4097" z="-8829" type="TRAVEL">player:harvest();</waypoint>
	<!-- # 6 --><waypoint x="-4163" z="-8879" type="TRAVEL"></waypoint>
	<!-- # 7 --><waypoint x="-4200" z="-9126" type="TRAVEL">player:harvest();</waypoint>
	<!-- # 8 --><waypoint x="-3889" z="-9073" type="TRAVEL">player:harvest();</waypoint>
	<!-- # 9 --><waypoint x="-3940" z="-9079" type="TRAVEL">player:harvest();</waypoint>
	<!-- #10 --><waypoint x="-3684" z="-8998" type="TRAVEL">player:harvest();</waypoint>
	<!-- #11 --><waypoint x="-3460" z="-9218" type="TRAVEL"></waypoint>
	<!-- #12 --><waypoint x="-3121" z="-9115" type="TRAVEL"></waypoint>
	<!-- #13 --><waypoint x="-2984" z="-9551" type="TRAVEL"></waypoint>

I had that bug too, but i fixed it. Just change in your waypoint file at the beggining:
<waypoints>
to
<waypoints type="TRAVEL">

and it will be working fine

i noticed you have waypoints type= .... i just have type (which worked fine in the past ...) do i need to switch it to that?

[d003232]

That looks good. You can now define the type at the beginning for the whole file:

Code: Select all

waypoints type="TRAVEL">
   <!-- # 1 --><waypoint x="-3813" z="-8391"></waypoint>
   <!-- # 2 --><waypoint x="-4029" z="-8461">player:harvest();</waypoint>
   <!-- # 3 --><waypoint x="-4057" z="-8772"></waypoint>
   <!-- # 4 --><waypoint x="-4057" z="-8772"></waypoint>

But both ways are ok. There seem to be a bug, if you don't define a type in the top and only at the singel waypoints. In that case the 'empty' default overwrites the the single waypoints. Hope you understand what I mean.

[d003232]

I did a fix with SVN 106.

Defined travel types in <waypoint> tags are no more overwriten by values from top <waypoints> tag. Only if no type in the <waypoint> tag is define, it inherit the value from the <waypoints> tag. And the default for the <waypoints> tag is "NORMAL".

[BlackGod]

I did a fix with SVN 106.

Defined travel types in <waypoint> tags are no more overwriten by values from top <waypoints> tag. Only if no type in the <waypoint> tag is define, it inherit the value from the <waypoints> tag. And the default for the <waypoints> tag is "NORMAL".

Thanks for the fix!
I had the same problem... but now everything works perfectly!
thx again^^

[copenhagen69]

I did a fix with SVN 106.

Defined travel types in <waypoint> tags are no more overwriten by values from top <waypoints> tag. Only if no type in the <waypoint> tag is define, it inherit the value from the <waypoints> tag. And the default for the <waypoints> tag is "NORMAL".

Thanks for the fix!
I had the same problem... but now everything works perfectly!
thx again^^

what did you do to fix it?
mine is still tab targeting everything .... i updated SVN today too just to make sure i had the latest of everything ..

[xxsinz]

Did you bother to make <waypoints> to <waypoints type="TRAVEL"> in your waypoint file?

[copenhagen69]

Did you bother to make <waypoints> to <waypoints type="TRAVEL"> in your waypoint file?

i did on one path and not another ... but both had the old school type=travel in each line ...

i update (mainly deleted all the red exclamation files in my folders since they would not update and turn green) and SVN updated it all again and now its working as it should be ...

so thanks for the help everyone thats how i fixed my harvest problem so hopefully this helps others with their problems too

[xxsinz]

It was never a problem, it was just a update... So instead of putting travel on each line, you just put it once at the top.

[wallofchaos]

Lots of friends having the same problem.

Mine works.
All i did was DL the new ROM. deleted mine and put the new one in. replaced my waypoint and profiles.

The only thing I notice now is that it acts very very sluggish. kinda acts like rubber banding with server lag.
Not sure why this is happening.
Also my camera angle will NOT stay where it used to. Making a lot of missed nodes.
but still working at least. Thanks for the updates.

[d003232]

Just use option:

Code: Select all

<option name="QUICK_TURN" value="false" />

if you want to have the old /turning type. Or set the camera distance to maximum, if you want to avoid the zoom in / zoom out.

What do you mean with 'acts very very sluggish'? The movement speed should be more flowing. With ferwer short stops.