Yeah, if this actually does fix the problem, it'd be a good idea to let the devs know because apparently they are quite baffled because it's hard to reproduce.

totally hope this works. sick of clicking pentinance 10 times in a row only to find out my oak just stands there playing with his own @#$%.

I pm'd GPG the details of the bug so hopefully they'll have it fixed soon.

Here's the bug in a nutshell - when you target a skill on an enemy that you are not facing, your DG will turn to face them before firing the skill.  The skill activation code essentially says:

An astute reader will wonder what happens if the target moves while you are turning to face them?  Well, what happens is you have only told the engine to turn to where the target was when you clicked the skill.  If the target has moved then it could happen that you finish your turn without ever facing the target.  If this happens then the code above hangs forever waiting.  If your target happens to turn around and move in front of you, your skill will activate all of a sudden.  Only other way out of the hang is to issue a new movement order, which essentially cancels your skill activation.

The problem is most common when you are very close to your target, since a tiny movement by the target causes a large change in relative direction, making it easy for him to move out of your turning field of view.  If you are turning clockwise and your target is moving clockwise then you hit the bug.  If you are turning clockwise and your target is moving counterclockwise then you do not hit the bug since he will cross in front of you at some point in your turn.

This mod essentially changes the code above to:

Keep in mind the actual code is alot more complicated than the above which is why the bug is not easily seen when looking at the real code.

FINALLY!

Yes Tiny, for the 100th time, we get it. There is no escaping your endless onslaught of DG bashing on IRC and forums. Funny you are still around with all the negativity towards DG and its devs/mods. You probably have no understanding of how programming works either. Which means you have no idea how hard it can be to find problems like that. Which means you are...........

Brilliant!! Someone deserves a new car for this, cough bman

Rofl, that's priceless. Good work. Hopefully they can use your experience to fix it in 1.01

doesnt matter, if he did it, then devs shoul've seen it too.

Keep in mind that GPG has been working under massive crunch for several months now (before and after release).  Sometimes it takes a set of fresh eyes to find a problem.  And given that they couldn't repro the problem themselves (I can't say why, since it seemed to be a very common problem), they had no idea where in the code to look.  Makes it hard to debug.

I've had the problem enough times to suspect it was related to turning and so I knew what section of code to look at (well...I knew what section of code to look for...it took a while to find the section related to turning...).

Anyway, don't knock GPG too much.  This is an excellent game marred by a bad MP design, which as I understand it, is Stardock's problem since they are the ones that built Impulse Reactor.  The in-game bugs are few and this is the only really annoying one.  they did an excellent job QA'ing the actual gameplay.

the mod is written in lua.  My example code above was just some pseudo-code and I have a tendency to use C-syntax when writing pseudo-code since I prefer it over lua syntax.

I'll say just this:

GPG, please release the SDK to the people and be done with it.

Ffs, this bug was from the beta and it was reported back then and it's still not fixed 1 month after the game was released. And now some dude fixes it? Lol.