Turns out this isn't debug-related

Or if it was, it was repurposed: <NUM is used by the 'you got X
missiles' script.
This commit is contained in:
Clownacy 2019-10-14 21:00:04 +00:00
parent 883f5470db
commit 253b33d34f

View file

@ -41,7 +41,7 @@
TEXT_SCRIPT gTS;
int gNumberTextScript[4]; // Seems to be for debugging
int gNumberTextScript[4];
char text[0x100];
RECT gRect_line = {0, 0, 216, 16};
@ -643,10 +643,9 @@ int TextScriptProc()
w = GetTextScriptNo(gTS.p_read + 4);
x = GetTextScriptNo(gTS.p_read + 9);
// Looks like Pixel left some debug code in. Oops.
gNumberTextScript[0] = x;
#ifndef FIX_BUGS
// z is uninitialised. Probably a leftover from copypasting.
// z is uninitialised. Probably a leftover from copypasting this from elsewhere.
gNumberTextScript[1] = z;
#endif
@ -1209,11 +1208,7 @@ int TextScriptProc()
}
else if (IS_COMMAND('N','U','M'))
{
// This seems to be a command used for debugging TSC scripts:
// It prints a selected char in the gNumberTextScript array.
// gNumberTextScript is only used by the '<AM+' command, and
// even then, part of it's assigned to an uninitialised
// variable, while the other half of it is completely unused.
// This supports up to four different values, but only one is actually used (a second is used erroneously)
z = GetTextScriptNo(gTS.p_read + 4);
SetNumberTextScript(z);
gTS.p_read += 8;