Open ike3 opened 10 years ago
Yes this issue seems to be most bots. When I locate a random bot they are just standing there looking like they are ready to cast but do nothing. I have only seen one bot actually move in the 3 days I tried the new Trinity commits.
They target object's that only can be seen by GM but are not attackable so they stuck there forever trying to kill script triger objects.
I don't think so. Just created a java-based simple monitoring site which shows live bot states. Most bots have no target at all and they are just staying. The real issue is that the 'move random' strategy was missing. Added it in [ai-0.36-73] so bots should move properly now.
Basic? Looks nice :), i just can't wait for the bots to become more like normal players (ie doing stuff players should do)
yeah glad you found it makes sense I was trying to get bots to do move random and they didn't move until I used grind command
I have also noticed this happening if my voidwalker pet tags the 2nd of two mobs and gets the agro first, once the random bots finished off the first mob they completely ignore the second mob. If I put my pet on passive I have yet to see this happen.
Tested in depth,with melees bots. For example with a feral cat,if u don't move the mobs over him,he will attack only doing white melee attacks (so no yellow attacks with spells,and so low dps). he starts doing real damage only when mobs are over him and after waking uo up him with follow command.When there are a group of mobs,it happens that he finish to kill one mob,an then he stays doing nothing even if there are other mobs near.
anyone having trouble w mages just jumping and not attacking??
I think the problem is in bool MovementAction::MoveTo(uint32 mapId, float x, float y, float z)
if (distance > sPlayerbotAIConfig.contactDistance)
So it the distance is less than 0.5f the bot is not moving. Without the check the bot would move indefinetely due to floating point calculation problems so the distance would never be zero.
Also there is another movement in bool MovementAction::MoveNear(WorldObject* target, float distance)
distance += target->GetObjectSize() / 2.0f;
So the bot is supposed to be just near the target. It seems that for some mobs the size is incorrect and the bot is thinking that it is touching the target but the distance is not enough for melee/spell.
I can only suggest I'm not a programmer :)
If u want i post my test on variuos pg's at level 80 vs heroic boss. I wrote my notes about every problematic class bot and my vote.
The fast one is that Death Knights,Rogues and Retribution paladins have serious problems because they doesn't attack/move or they do only white damages. The other classes have some issues but not so important. The best class i tested as melee,is the warrior fury,he tends to follow the tank and do the best to attack the mobs.
This is my table :+1:
Wasn't sure where to send private messages, but just wanted to thank you for all the work you do with the bots. Even at their current state, its a marvelous thing to be able to play WoW like this alone.
Please don't give up this great work! TY!
I still got this problem with version ai-0.36-144 on trinity-3.3.5. I added a bot within my logged-in account, a priest, she didn't accept "heal" or "do heal" whisper. She tells "heal: impossible". But I tried to use this character, heal spell has no problem. I set heal strategy with "co +heal", but she just give me an attack state, but do nothing there. No damage output, no heal output...
Random bots have same problem...
Sometimes something prevents bot to reach target and they just stay at the distance doing nothing. Attacking the target or even getting close could trigger bot movement and attack. Seems more actual for spell casters. Investigation is required.