Game->SetScreenState() doesn't always work — Quarantined Bugs

Saffith 01 Mar 2010, 04:53

ffc script SetFlags
{
    void run()
    {
        Game->SetScreenState(1, 0x01, ST_DOORUP, true);
        Game->SetScreenState(1, 0x01, ST_DOORDOWN, true);
        Game->SetScreenState(1, 0x01, ST_DOORLEFT, true);
        Game->SetScreenState(1, 0x01, ST_DOORRIGHT, true);
        Game->SetScreenState(1, 0x01, ST_SECRET, true);
        
        Game->SetScreenState(2, 0x00, ST_DOORUP, true);
        Game->SetScreenState(2, 0x00, ST_DOORDOWN, true);
        Game->SetScreenState(2, 0x00, ST_DOORLEFT, true);
        Game->SetScreenState(2, 0x00, ST_DOORRIGHT, true);
        Game->SetScreenState(2, 0x00, ST_SECRET, true);
    }
}

Apparently, the second set simply isn't working. Doesn't seem to like map #2.

raiu 01 Mar 2010, 05:32

many builds ago, i had a similar problem, but it was that it didn't work on screen 00, that might be the problem there?

Saffith 01 Mar 2010, 20:30

Nah, shouldn't be that; I first ran into it on screen 63.

raiu 01 Mar 2010, 22:17

yeah, that was several builds ago that it didnt work, i think its fixed now, but it was worth a mention :/

_L_ 05 Mar 2010, 09:07

OK! The bug seems to be that SetScreenState and GetScreenState count maps from 0 upward instead of 1 upward. (Actually it's always done that, but this isn't consistent with other ZScript commands, not to mention ZQuest itself.)

Saffith 06 Mar 2010, 22:51

Worse than that... Seems it was treating maps as being 144 screens instead of 136. Should be good now, though.