Incinerate issues

[TC9869]

I've encountered a problem quite a few times today and thought I'd post about it here, the next time I see it I'm going to try to get a log.

The bot stands just out of max range and spams incinerate, too far away to aggro the mob and make it run at me and too far to hit, so it stands there infinitely doing the same thing. Added faster projectiles to make the flames go farther, hoping that would help, but it didn't.

Also occasionally I've seen the bot just be stupid and cast when it wasn't hitting, I suspect the cause was close corners, the fires were probably hitting the edge of a building and the bot was failing to correct/accommodate.

 

[pushedx]

This is a known issue that should be resolved once the new input and action using gets integrated into the bot. There's no ETA on it, on than as soon as it's done and tested, but it's the main thing being worked on right now and tested internally.

The issue with Incinerate, like Freezing Pulse, is that the mechanics of the skill make the client stand in place to attack at a location, rather than moving into range then using the skill. The fix would be to move into skill range first, and then start casting the skill. The Exile CR right now relies on the client moving the character correctly. Most of the time, it does for most skills. However, a few skills need custom logic to work correctly.

With the current system we have, the client isn't moving properly when stuff is called from behavior trees (which is how CRs work) due to how we have to do things (spread out across many game ticks). Fixing the logic for skills like Incinerate to work better is not possible right now, so that's why the new changes are being worked on. We hope to fix a lot of random movement issues, skill using issues, and random chest/door/object interaction issues (although there will always be weird little things happening in this game).

 

[TC9869]

Awesome, thanks for the update!

 

[Azoth]

I ran into this problem a lot too. Faster Projectiles DOES help, if you get enough of it. You can add a max range to Incinerate, but that'll run into situations where a ranged mob will be standing outside the range you set. Depending on the logic for your other spells, you could a) Still cast incinerate, if you didn't remove the default Incinerate at the bottom of the priority list, b) cast another spell, c) use default attack, d) stand still not doing anything.

Using a secondary spell, like Firestorm, for mobs that are out of Incinerate range is always an option. Are you running an Incinerate build with Cast on Damage Taken Lightning Warp? That helps tremendously with range issues.