It seems that the mission header parser cannot handle true and false. It will both parse to false. On the other hand, setting it to 1, does parse to true. As the parsing is likely done by the engine, we cannot fix this on our side, so we'll have to advocate using integers instead in the documentations.
It seems that the mission header parser cannot handle
true
andfalse
. It will both parse tofalse
. On the other hand, setting it to1
, does parse totrue
. As the parsing is likely done by the engine, we cannot fix this on our side, so we'll have to advocate using integers instead in the documentations.