Tests that don't and fatals that aren't.
Posted: 20 Oct 2005 15:12
Action 7/9 test 09 does not function as advertised, and, under certain circumstances, fatal action Bs do not turn the flag grey.
The attached archive contains a newgrf setup which displays both of these bugs.
PlaneSetAIAR.grf tests for the presence of PlaneSet[w].grf (GRFid "JS" 01 01):Sprite 5 does not skip sprites 6 and 7. If I change the test to 06, it works (at least with the given newgrfw.cfg).
PlaneSetAIAR.grf also takes a parameter. The low two bits control which of its 2 parts (auto-replace and AI management) are activated (set bit to deactivate). I test it for equality with 3[0], and if so, fail with:When given a parameter with the low two bits set, the action B is apparently processed, but it does not turn the flag grey. The message appears, but the flag remains a red/green toggle.
[0] After ANDing with 3 and setting bit 1 if autoreplace off.
The attached archive contains a newgrf setup which displays both of these bugs.
PlaneSetAIAR.grf tests for the presence of PlaneSet[w].grf (GRFid "JS" 01 01):
Code: Select all
5 * 9 07 88 04 09 "JS" 01 01 02
6 * 20 0B 02 1F 02 "PlaneSet[w].grf" 00
7 * 6 07 83 01 03 FF 00PlaneSetAIAR.grf also takes a parameter. The low two bits control which of its 2 parts (auto-replace and AI management) are activated (set bit to deactivate). I test it for equality with 3[0], and if so, fail with:
Code: Select all
14 * 25 0B 03 1F FF 80 " has nothing to do." 00[0] After ANDing with 3 and setting bit 1 if autoreplace off.