Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Valguris]

I stepped up to a friendly derelict behemoth (Marauder?). Then I clicked the tile on the other side of the behemoth to move there. Cogmind would jump over the behemoth to the destination and then immediately jump back. If I order to move further away, the move right after jumping over the behemoth is often in the wrong direction.

This bug happened in version 8.2, but I didn't see anything similar appearing in the patch notes for Beta 9.

[Kyzrati]

Weird, easy to repeat, just saw it. No idea why that started happening, pretty sure this worked fine before... Maybe something up with one of the new flight movement QoL features? Especially interesting that it's not an issue with keyboard movement though.

Even weirder, it only happens with 2x2 bots, not 3x3!

[Valguris]

My uneducated guess is that Cogmind tries to follow the highlighted path exactly, but does not take into account that 2 tiles were skipped, so for the next step it goes towards one of the skipped tiles, resulting in a weird behaviour.
Maybe if you skip 3 tiles, Cogmind tries to move onto a tile that is not adjacent to it, and therefore recalculates the path?

[Kyzrati]

I've written a reply here several times and keep rewriting it as I think of new stuff xD

Yeah that does seem to be the case--it's creating a path, hopping to the target, but still has old positions so it's trying to go to those next and ends up hopping back. Still have to locate the actual source but yeah...

[Kyzrati]

Okay, fixed for next release, just needed to remove the extra cells that were jumped from their path. Surprised that's been in there for so long! (Although the fact that it only happens when there are no enemies in view, and only at certain angles, makes it less likely to be discovered...)

It wasn't happening for even larger bots because after the jump there was a disconnect in the path, so it couldn't follow and gave up. 2x2 was small enough that there was no disconnect--they were still adjacent to the next cell in the path, but it would send them in the reverse direction!