PDA

View Full Version : Junk Data in ZASM Export



ZoriaRPG
07-27-2016, 01:57 AM
When exporting ZASM during compilation, there is a junk Init script, with a bunch of garbled char, and a phantom incarnation of a GhostZH script, that are both output to the log, despite neither existing.

These are carryovers in the quest file template from 2.50.0 beta.

Saffith
07-27-2016, 01:56 PM
I don't know why those are there. They somehow got assigned to global slots numbered greater than 3, which I don't think have ever been valid. It shouldn't be hard to clear them out.

ZoriaRPG
07-28-2016, 12:17 AM
#define NUMSCRIPTFFC 512
#define NUMSCRIPTFFCOLD 256
#define NUMSCRIPTITEM 256
#define NUMSCRIPTGUYS 256
#define NUMSCRIPTWEAPONS 256
#define NUMSCRIPTGLOBAL 4
#define NUMSCRIPTGLOBALOLD 3
#define NUMSCRIPTLINK 3
#define NUMSCRIPTSCREEN 256

(zdefs.h)

extern ffscript *globalscripts[NUMSCRIPTGLOBAL];

zq_class.cpp

Nope. Although I'm not even sure where, or if globalscripts[] it is ever actually defined, else if it runs entirely from that extern. I suppose it's possible that NUMSCRIPTGLOBAL was defined as 5 or 6 at some point, or something, to cause that. I'm not sure where the junk data was stored though, as it'd be outside the bounds of globalscripts[].