stiv uploaded file warzone2100.gdmp-2N4f2p (11.2 KiB)

[moveDroidToNoFormation] Bad movement position

stiv uploaded file warzone2100.gdmp-tQF1ir (11.2 KiB)

revision 10604 - error [moveDroidToNoFormation] Bad movement position

stiv changed owner from `` to DylanDog

stiv changed status from new to assigned

DylanDog commented

I am not sure this is an issue related to the AI script, I see this message error appearing on events which has nothing to do with droid movements at all. I will update this ticket with more information soon.

DylanDog changed owner from DylanDog to stiv

DylanDog commented

Recently I got the following message too:

error   |02:20:30: [moveDroidToNoFormation] Bad movement position
error   |02:20:30: [moveDroidToNoFormation] Assert in Warzone: ../../../src/move.c:443 (x > 0 && y > 0), last script event: 'showPlayerInfo'
error   |02:20:30: [SendDroidMove] SendDroidMove: Invalid move order
error   |02:20:30: [SendDroidMove] Assert in Warzone: ../../../src/multibot.c:447 (x > 0 && y > 0), last script event: 'showPlayerInfo'

now the event showPlayerInfo is an "empty" event (I use sometimes to fill it with some debug report):

// ============================ Debug messages====================
event showPlayerInfo (inactive)
{
  ASSERT(player >= 0 and player < 8,      "player out of bounds: showPlayerInfo " & player, player);
  boolResult = true;
}

Therefore the error message is strange as I do not see the reason of having a crash in moveDroidToNoFormation()

Even worse the following:

error   |02:29:32: [moveDroidToNoFormation] Bad movement position
error   |02:29:32: [moveDroidToNoFormation] Assert in Warzone: ../../../src/move.c:443 (x > 0 && y > 0), last script event: 'weatherStop'
error   |02:29:32: [SendDroidMove] SendDroidMove: Invalid move order
error   |02:29:32: [SendDroidMove] Assert in Warzone: ../../../src/multibot.c:447 (x > 0 && y > 0), last script event: 'weatherStop'

DyDo has no event called weatherStop

stiv can you maybe have a look?

DylanDog changed status from assigned to closed

DylanDog set resolution to fixed

DylanDog commented

Fixed this on DyDo 2.1.3. I still do not think it is an AI script issue. I think the problem is created by the following line

orderDroid(droid, DORDER_RUN);

I have now removed this from the AI script and the issue does not appear anymore.