"Ghost Aggro" Problem

[Auto Pilot]

Started using RoM Bot a few days ago and I have to say it's a really great script (and weirdly "intuitive" to use for a command line tool )

But when I tried to level my 2nd class today I encountered a very weird issue, bot seems to keep believing it has aggro :
- On every waypoint I get a mess "Waiting on aggressive enemies" message
- Bot doesn't detect ennnemies anymore while running to next waypoint
- It seems to be "lagged out", it's configured to heal itself when health drops below 70%, but it only starts healing around 20-40% HP (which doesn't help on a squishy mage fighting some mobs 2-3 levels above his level)

Waypoint file shouldn't be the cause, they're the same I used to painlessly level my first class and really basic ones (just coords and some harvest commands, no fancy stuff)
Profile file doesn't seem like it could be an issue either, I just copied the one from my main class (priest) and just changed the skill section to use the mage nukes instead of priest ones.

I tried looking quickly in source code for the code around parts printing the "Waiting ..." message, but it wasn't really helpfull except for confirming that it's related to some aggro issue. So anyone got a similar issue and managed to fix it ? Or any ideas of what I should check ?

[rock5]

It's strange that it was working for your first class but not for your second. It implies a problem with your profile. Does the first class still work?

Did you update the bot recently? Because I did make a change to aggro detection in rev 579, but it's working for me and I can't see how the changes can cause the problem you described?

The strange thing is, both places where the message "Waiting on aggressive enemies" appears, are in the "while player.Battling" loop. Which means that message can only appear if you or a party member has aggro.

Another thing to check is whether you have any conflicting files from your last bot update. Check if any of the files in the 'rom' folder have yellow icons next to them.

[Auto Pilot]

Main class is still working more than fine (that part is probably the one that bothers me the most since waypoints are the same for both and profiles are identical too except for skill list)

And I'm still using rev572, I'll try to update later (I'm back botting on main class atm) and see if solves the issue (there shouldn't be any update conflict atm since I'm a new user and this was the first version I used).

Also it certainly has something to do with aggro detection, since bot seemed to keep acting as if it had perma aggro (it was using the short-term damage buffs - which have the inbattle attribute set to true in profile - while running from a waypoint to another).

[lisa]

There are places and more specifically "ghost" mobs. I have encounted it in few places and you seem to get agro from a mob which the game thinks is very far away and therefore you can't kill it as you can't even see it. Even while playing manually as a healer in instances I have noticed the "in combat" bug and it makes it impossible to resurect newbs.

I haven't been able to come up with a way to fix this as yet.
I haven't had a chance to test the new revisions on some problem areas that I know it always occurs. rock5 may have already solved the issue.

[rock5]

rock5 may have already solved the issue.

I don't remember doing any work on that. I think I remember Administrator might have tackled it, although I don't remember what the result was.

[Auto Pilot]

Hadn't encountered since my last post until earlier today (and same really weird thing, this time I had just stopped bot to add a new spell to profile and it went in "ghost aggro mode" when restarting it).

I thought it might be a RoM related issue too, so after restarting bot a few times (and removing the change I did to profile) I switched to another channel and it stopped detecting those ghost mobs immediatly. It might be a really hard one to fix (if the bot can even make the difference between a ghost mob and real one) since it just happens randomly

[lisa]

lol had this 1 today

Code: Select all

Engaging enemy [******] in combat.
Use 3: MAGE_FLAME          =>   * Failed to cast *
Use 7: MAGE_FIREBALL       =>   ***** (26224/26224)
Use 3: MAGE_FLAME          =>   * Failed to cast *
Moving in | Suggested range: 200 | Distance: 20091
Use 8: MAGE_ENERGY_INFLUX  =>   ******* (26224/26224)

check out the distance, bot started walking to it lol