#2154: bug or feature?: artillery stays assigned to sensor if nexus-turret
"steals" it. assertion triggered.
------------------------------------------------+---------------------------
Reporter: corvusco...@… | Type: bug
Status: new | Priority: minor
Milestone: unspecified | Component: Engine: other
Version: 2.3.5 (rc 3) | Keywords: assertion
nexus turret sensor
Operating System: All/Non-Specific | Blocked By:
Blocking: |
------------------------------------------------+---------------------------
I got a lot of those in the logs:
{{{
error |12:12:18: [actionUpdateDroid] Assert in Warzone: action.c:2281
((psDroid->psTarget->type == OBJ_DROID || psDroid->psTarget->type ==
OBJ_STRUCTURE) && (psDroid->psTarget->player == psDroid->player)), last
script event: 'N/A'
error |12:12:18: [actionUpdateDroid] DACTION_FIRESUPPORT: incorrect
target type
}}}
What happened was, I had a lot of artillery units assigned to a sensor
tank.
But the sensor tank was "infected/stolen" by an enemy "nexus" tower,
making it one of his.
Subsequently the - now enemy - sensor targeted one of my own nearby units.
And my artillery fired! Friendly fire!!! RUN!!!
Personally I don't think that behaviour really is a bug, but rather a
really cool side effect of "taking over the right unit"
(though it would be cool if there'd be a quick way to re-assign a big
amount of artillery units to a new sensor - currently one has to right-
click them one-by one ;)
However the above assertion gets triggered, which indicates this "case"
was not taken into account in action.c.
Somebody might want to go over it and fix at least the assertion to take
this case into account.
Adding map+savegame
--
Ticket URL: <http://developer.wz2100.net/ticket/2154>
Warzone 2100 Trac <http://developer.wz2100.net/>
The Warzone 2100 Project
_______________________________________________
Warzone-dev mailing list
[email protected]
https://mail.gna.org/listinfo/warzone-dev
