Read-only archive of the Armageddon Games Forums Archive (2000–2026) · About this archive

[842] Scripting Corrupting Quest

7 replies · 1,901 views · Started 24 July 2008

Uh, let's see I can't really nail down exactly how this happens but I think it's something to changing a line in a script like this:

this->Y+16; (a line that needed fixing) to this:
this->Y += 16;

But you have to compile in a changed .z file in order to get this corruption. If you change it in the buffer it comes out alright.

When I do this and save it stays on the "Saving Maps..." for a long time and then when you load the quest it says "Reading Maps...ok. Bad Token! Searching..."

Then EVERYTHING is screwed up, I mean 99% of maps are gone and the 1% that are still there are garbled messes. There may be other ways to achieve this too, but this is the situation I keep running into it in.

Beware those who test this, make sure backups are made right before.

So, to be precise, you change a .z file, then load it into the buffer, then compile... and it messes up the saving of maps?

Pretty much, I think it's something specific in changing the .z file, cause I don't get it ever time.

My script file has changed greatly since then, but if you still want it I'll PM it to you.

Also, no matter how hard I try I can't replicate this in 846, seems like it's only on 842 to me. I mean, I ran into this often and on many occasions in 842, but I haven't had a problem yet with 846.

I saw this with 842, but it's gone in 846. I don't know what the trigger was, though. However, I was using scripting as well.

When saving, I don't know what it was writing, but my normally 830 kb quest ballooned to 24 Megs (!!), and was totally corrupted.

Either way, whatever it was, 846 fixed it.