"kiting" combat rotation?
- Thread starter xeratzy
- Start date
naut
Community Developer
- Joined
- Feb 9, 2012
- Messages
- 277
- Reaction score
- 21
To my knowledge there is no current method to calculate a position x yards from a mob, any coding I have done revolves around detecting and moving to the mob location.
Because to my knowledge it lacks the ability to calculate a position away from a mob, you cannot force movement to that position.
Because to my knowledge it lacks the ability to calculate a position away from a mob, you cannot force movement to that position.
Hypothetically you could, there are some good resources out there,eq . Anti-Gravity Movement - RoboWiki while this is for something completely else (2d space for robots fighting) you could utilize the idea to flag the coordinates with mobs and achieve you moving to position which has the least weight.
The previous Beta version had some experimental kite logic. However, it did more harm than good for most people due to the nature of trying to run generic kiting logic.
The issue comes down to needing to design CR logic around various tilesets, rather than trying to make code that works across them all. In large open tilesets, you can easily kite around mobs and the logic is pretty simple. In small closed tilesets, you can't. If you have a build that needs kiting, you need really specific logic to kite in the small closed areas that would otherwise interfere with everyone else.
There's two ways you can implement kiting logic. You can either try to keep moving "backwards", away from the mob until you back yourself into a corner, and then try to re-position, or you can simply move back to a fixed locationn that was deemed safe. AreaStateCache.Current.CurrentAnchorPoint exists for that reason; it's the point you first spawn in an instance, and in the old logic, was used to move back to when you needed to kite.
In both cases though, there are various combat scenarios you need to code around. Around doorways, regardless if there is/was a door there or not, if you kite out of LoS, your default logic would then try to get into LoS by running back into the room. Your kite logic would then trigger again, if you didn't limit it, and you'd run back and forth trying to do a hit and run, but mostly be unsuccessful. This happens a lot in certain tilesets and really diminishes the purpose behind kiting.
So for now, the ExampleRoutine provided doesn't try to do any of that stuff, but it's not meant to be a final solution for CRs. The combat model is tricky in this game, and trying to write one routine that handles everything correctly is quite an undertaking. From a design perspective, a much more advanced CR design is needed to be able to handle this issue and others correctly in context of the game.
The issue comes down to needing to design CR logic around various tilesets, rather than trying to make code that works across them all. In large open tilesets, you can easily kite around mobs and the logic is pretty simple. In small closed tilesets, you can't. If you have a build that needs kiting, you need really specific logic to kite in the small closed areas that would otherwise interfere with everyone else.
There's two ways you can implement kiting logic. You can either try to keep moving "backwards", away from the mob until you back yourself into a corner, and then try to re-position, or you can simply move back to a fixed locationn that was deemed safe. AreaStateCache.Current.CurrentAnchorPoint exists for that reason; it's the point you first spawn in an instance, and in the old logic, was used to move back to when you needed to kite.
In both cases though, there are various combat scenarios you need to code around. Around doorways, regardless if there is/was a door there or not, if you kite out of LoS, your default logic would then try to get into LoS by running back into the room. Your kite logic would then trigger again, if you didn't limit it, and you'd run back and forth trying to do a hit and run, but mostly be unsuccessful. This happens a lot in certain tilesets and really diminishes the purpose behind kiting.
So for now, the ExampleRoutine provided doesn't try to do any of that stuff, but it's not meant to be a final solution for CRs. The combat model is tricky in this game, and trying to write one routine that handles everything correctly is quite an undertaking. From a design perspective, a much more advanced CR design is needed to be able to handle this issue and others correctly in context of the game.
darkbluefirefly
Community Developer
- Joined
- Nov 8, 2013
- Messages
- 1,927
- Reaction score
- 18
just gear your chars better.. like seriously, why rush anything, the bot can run 24/7 that's 4 times longer then you can play a day..
actually, i'm pretty well geared, it's just that if it was possible, kitting would improve surviving a lot.
Havent had any real issue with surviving beyond. Just set it up to dc on magnus and the beyond uniques, have a decent health pool and be capped.