Set up aggro timeout and management of RoM Bot

[Chemico]

Hello guys (and girls, of course)

The bot is working great at all, mostly for doing easy stuff when i am lazy and sit next to the PC to read a book or surf in the internet or something like that. Sometimes, for example, i let the bot farm some mobs to gather daily items. works great, but there is one issue. when my char comes nearer to a mob fighting with NPC / another player and this mob uses AoE- Skills, my char will get involved into the fight (onscreen message of the fight having begun) and the bot will stand still or just run straight forward into the direction it moved as the fight message popped up. This will last for about 3 to five seconds, then the bot will try to get back to the last waypoint and the micromacro window says "aggro timeout [German Version: Aggro Wartezeit überschritten.]" in red letters. this gets very annoying when my char doesnt leave the fight again, so the bot will just continue to stand still or will overrun the targeted waypoint again and say aggro timeout.

So is there a way to edit aggro management of the bot or maybe just disable / adjust that aggro timeout timer? basicly i want it target only specific mobs (which can be archieved through setting up the botting char profile.xml) and simultaneously only fight back mobs which actually have me as a target when i get into fight. Please help me find the way to go!

In advance, sorry for my english if it is too hard to understand, i am still practicing.

Greetz from germany

[MiesterMan]

I'd suggest to enable kill stealing in profile:

Code: Select all

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

[Chemico]

Thank you, i´ll try that, but i dont see yet how that prevents the bot from waiting for the attacker. Actually i don´t want it waiting for attackers, i want it just follow the waypoints, attack the mobs i specified in the pofile.xml and ignore a specific mob even if this mob gets me into fight. It shall only be fought back when it actually harms my char.

[lisa]

The bot is actually designed to do exactly what it is doing. So if you are in combat, usually because something is attacking you, it waits for what ever it is to actually hit you and then it retaliates. In your case how ever this isnt the case as you or it is being hit with aoe but it is attacking something else.

I'll have to think on this.

[rock5]

I thought the bot had a check, that when it detects agrro, it searches for mobs that are targeting it. If not it moves on.

[MiesterMan]

I thought the bot had a check, that when it detects agrro, it searches for mobs that are targeting it. If not it moves on.

That was my most recent observation. I was impressed by the improve so I assumed it was still present.

In this case your bot is in combat but won't attack because someone else has aggro. Or at least that's what I was guessing. I could be wrong, wouldn't be the first time.

[Chemico]

Let me describe the situation. In Xaviera there is the daily quest in Inferno garden to collect watchdog meat / guard dog meat. Some of these dogs are spawning near a power core surrounded with 4 magicians. These magicians do not attack you, they are red, but they are concentrated on the core. The problem are 4 green "adventurer"- NPCs patrolling the Inferno Garden. They take a route to destroy all of the ten power cores spread all over the Inferno Garden, so they will sooner or later cross the first of these power cores which is in the dog spawning area. They will attack everything within their range, so when they reach the area of the ore, they will attack the magicians guarding the core. One or two of these magicians will cast some kind of AoE which will make every player or allied green NPC in range 50% slower. This is the AoE i spoke about. It instantly gets me into fight when i let the bot kill some dogs to get the meat. when this is happening, the bot will react weird. it will continue to run into the direction it ran when the fight begun, and five seconds afterward, it will tell me "Aggro time out reached" (German: "Aggro Wartezeit überschritten") and go back into the direction of the last waypoint in target. If it is still in fight, it will overrun that waypoint once again until the timeout has been reached.

With this in mind, i want the bot to completly ignore the magicians until they target me directly. If they only fight those green adventurers back (which sadly spawn almost instantly again outside Inferno Garden and patrol it again), the only effect they have on me is this slowing debuff AoE lasting for about ten seconds. they do not damage me directly. Thats why i asked if it is possible to teach the bot to decide between aggro from / getting in a fight with a mob targetting me (like crossing some red mob´s pulling radius) and aggro from / getting in a fight with a mob not actually having me as a target thus ignoring me and just using AoE skills for their primary target and its allies. Either this way or just telling the bot not to wait for attackers, just follow the waypoints and fight back any unwanted attackers not being in the list of specified mob targets when they damage me.

Overall it works great, but this only situation makes it behave strange and even let it run into edges where it doesnt find its way back thus telling me my char is stuck.

[lisa]

I'll check out the spot later tonight, see what I can come up with.

[Murky]

any luck on this?

my bot also doesn't attack mobs fighting each other

[rock5]

It looks like when the bot detects aggro it looks for a mob that has it targeted which is what it should do. But if it doesn't find one then it waits 4 seconds. We could probably remove that 4 second pause because if a mob is attacking you the search should find it.

The only problem I foresee is the search for the mob use evalTargetDefault. So if a mob does have you targeted and it's evaluated as not a valid target eg. it's too high a level, then it will continue and ignore it until it damages you.

There's 2 ways I can think to fix this. 1. remove the eval function so it will find any mobs that are targeting you, or 2. add a check to the top of the evalTargetDefault function to return true if the mob is targeting you. I'm not 100% sure of all the consequences of these so would appreciate other programmers input.

[lisa]

. remove the eval function so it will find any mobs that are targeting you

If this also checks pet or party members then this would be fine I think, if it doesn't check pet or party then this would be bad.

2. add a check to the top of the evalTargetDefault function to return true if the mob is targeting you.

If you did thise then it pretty much makes all the code thereafter useless if target is targeting you, prob not best option.
First bit I can see where issue would be is height check.

So option 1 would be better aslong as it also checks pet and party

[rock5]

2. add a check to the top of the evalTargetDefault function to return true if the mob is targeting you.

If you did thise then it pretty much makes all the code thereafter useless if target is targeting you, prob not best option.
First bit I can see where issue would be is height check.

The logic of this is if a mob is attacking you the other checks aren't relevant. If it's too high a level you don't want to ignore it if it attacks you. If it's too high, if it's attacking you it will come to you're level. It wont remain out of reach. See what I mean?

. remove the eval function so it will find any mobs that are targeting you

If this also checks pet or party members then this would be fine I think, if it doesn't check pet or party then this would be bad.

What we are talking about is the search for aggro mobs when it detects aggro. I don't think that has anything to do with party or pets.

The second option might be safer because it affects less but I think there is a fundamental problem that needs fixing. evalTargetDefault essentially has to decide if we should attack a target. As it is now it's deciding that we shouldn't attack a mob that is attacking you because it doesn't pass one of the criteria. Doesn't that seem wrong?

[lisa]

If it's too high, if it's attacking you it will come to you're level. It wont remain out of reach. See what I mean?

A caster type wouldn't move.

What we are talking about is the search for aggro mobs when it detects aggro. I don't think that has anything to do with party or pets.

If a mob is attacking your pet and you just ignore it, pet may die, pet is also your tank and will get agro off you majority of the time. Without checking for mob targeting pet you will always just continue with the WP and thats not what you want.

If you have agro because a party member is being attacked then you would want to kill it, ignoring the mob and continuing WP and leaving party member behind isn't really working as a team.

[rock5]

What we are talking about is the search for aggro mobs when it detects aggro. I don't think that has anything to do with party or pets.

If a mob is attacking your pet and you just ignore it, pet may die, pet is also your tank and will get agro off you majority of the time. Without checking for mob targeting pet you will always just continue with the WP and thats not what you want.

If you have agro because a party member is being attacked then you would want to kill it, ignoring the mob and continuing WP and leaving party member behind isn't really working as a team.

How does it work now? Does it attack mobs attacking your pet or party members?

We could always add that too. If mob has you targeted or party targeted or pet targeted then target is valid regarless of other checks. Ah but what if your party member was far away, just in range to detect?

[lisa]

Ah but what if your party member was far away, just in range to detect?

Target memory range is around 250, so if it is beyond that it won't show as targeting anything.

Yeah I set up bot when I did party to also check party members for being targeted by mobs when looking for enemies.

in CPlayer:findEnemy(aggroOnly, _id, evalFunc, ignore)

Code: Select all

(( (pawn.TargetPtr == self.Address or (pawn.TargetPtr == self.PetPtr and self.PetPtr ~= 0) or (_target.Name == GetPartyMemberName(1) )  or (_target.Name == GetPartyMemberName(2) ) or (_target.Name == GetPartyMemberName(3) ) or (_target.Name == GetPartyMemberName(4) ) or (_target.Name == GetPartyMemberName(5) ) )

[bobdole]

When I talked about the bot going haywire and off course the above is exactly my issue, so dumb down the fix for me please.

[lisa]

When I talked about the bot going haywire and off course the above is exactly my issue, so dumb down the fix for me please.

Actually we are still deciding on best way to do it and then it will be commited, it's not a copy this code here type issue.

[bobdole]

I agree 100%, this needs to be a function that can be turned on or off via a profile setting.

[rock5]

I just had another look at the evalTargetDefault function and it does deal with aggro, eg. if mob level too high then dont target unless it's attacking you.

So what was the problem we were trying to solve? Ah yes, if your drawn into combat but nothing is attacking you. I think my original idea to just remove the 4 second wait should fix it. Everything that has come after that has probably been a waste of time.

So just try this. At line 571 replace this section that waits 4 seconds with just a break.

Code: Select all

				if( os.difftime(os.time(), aggroWaitStart) > 4 ) then
					cprintf(cli.red, language[34]);		-- Aggro wait time out
					break;
				end;

replace with

Code: Select all

break

[bobdole]

I didn't see the issue as clear as the OP but the big problem is when the bot does pause for aggro wait timeout it doesn't always stop but rather just runs or rides the mount the entire wait time.