"GUY" bug — Exterminated Bugs — Armageddon Games Forums Archive

Freedom 05 Feb 2010, 09:32

since the olden days most people removed ama in their tilesets and left a blank tile there so they could put their guy in the room where they wanted him for the message string.
That slot now, although empty, is placing a black square in all of my string rooms where the guy would be standing.

This just started after I was doing the 8 bit recoloring and reported that bug, at the same time these two things happened I got a header error and the quest would no longer open.

I then placed it in a separate folder and opened a old back up to continue working with ZC and sent a zipped copy to Jman, it opened for him, and so I tried it again and then it opened for me.
That makes me believe that it somehow messed with the engine and wouldn't allow that quest to open until another was opened and somehow somewhere reset my engine to allow that quest to open again, it was on reopening it that I started seeing the black square, it didn't do that beforehand.

The order of things here was this, I made the screen, added the guy and string to a dupe screen, saved it, tested it in the player, went back in and did the color thing for 8 bit, (bug) reported on the other thread, saved, closed, and then got the header error (reported on another thread) trying to reopen it.

somehow these events are tied together

EDIT
ok EDIT...
This the darknut bug seems to have been caused by opening my header error quest in 1154 and moving it back to the 1099, I see many changes have been made to the enemy editor.
the ama guy problem is also not present in the 1154 that I reported with the 1099.

so I guess I've just been forced to upgrade against my wishes.

let's not forget the header error guys, that sent me down this all day long path of frenzied hair pulling ;O)

so we are back then maybe to the 8 bit color thing that may have caused my header error

jman2050 05 Feb 2010, 16:40

Did you attempt to open a copy of the quest (not saved in 1154) with 1099? If THAT one continues to give you a header error then I could more easily identify what's going on here, cause this behavior sounds very strange and its connection with messing up the header loading is definitely not clear just from the description alone.

Freedom 05 Feb 2010, 17:48

jman2050 wrote:Did you attempt to open a copy of the quest (not saved in 1154) with 1099? If THAT one continues to give you a header error then I could more easily identify what's going on here, cause this behavior sounds very strange and its connection with messing up the header loading is definitely not clear just from the description alone.

when it first messed up I made a copy of it and put it in a folder called error
and also dropped a copy into the folder with the 1154 and unzipped and installed it, I hadn't used the 1154 yet.
It also errored in the 1154.
Then when you told me it opened in the 1154 for you I tried it again, and sure enough it did open that time.
ecstatic ;O) that I hadn't lost my 4 days of work and without thinking, I grabbed that copy and dropped it in the 1099.
doing that produced the guy bug and the darknut bug.
today I grabbed an original copy of the error quest from the error folder, and tried it in the 1099 and now it opens, without said darknut and guy bugs of course.
Why it wouldn't open then, and will now I have no clue, unless it was completely closing zquest and exiting windows as well that was the difference.
it still somehow seems tied to the 8 bit color thing, but L has fixed that now so.......

Nicholas Steel 06 Feb 2010, 04:36

Maybe scan your RAM with memtest86+ for 4 or more hours (currently the newest), wipe your HDD free space as well as a general disk check to mark any bad sectors that may not already be known, etc. just to confirm your computer IS running healthy.

Once all that is done I would believe you about your computer being as solid as a rock ._.

edit: bah, I come off sounding like a insignificant prick picking at you >.>

Freedom 06 Feb 2010, 07:05

franpa,
my computer didn't cause the problem.
I'm on a FRESH laptop.
I got careless and caused 2 of the problems by not thinking and dropping the quest back in 1099 after it finally opened in the 1154, but IT was the one that sent me down the path that got me there in the first place.
I wouldn't have been doing that had it not screwed up.

Think of it as the tiger woods scenario...
dumbass wrecked the shit out of his truck, but his other choice was to stand in his living room and let his wife whup that arse with a golf club ;O)
In short... he did the right thing and FUCKED UP

Nicholas Steel 06 Feb 2010, 07:30

Doesn't matter how fresh a RAM stick is, it can be faulty the very instant it comes off the production line, get faulty during transit from excessive pressure from god knows what else was placed on the box etc. and companies like DELL and HP etc. aren't immune to this problem either.

Your RAM may work in most situations but under very very specific ones, it will fail, hence why Memtest 86 and memtest 86+ exist.

Freedom 06 Feb 2010, 07:38

and it could be what it really was too, a bug in zelda classic.
I see no reason to chase bugs any further than where they originated

Instead of wondering all about my PC why aren't you reporting some of these bugs, I've been back farting with it for what.... 3 weeks and have found some extremely obvious bugs that anyone looking should have picked right up on, yet you've been here the whole time, didn't, and now you're questioning my computer.

Nicholas Steel 06 Feb 2010, 14:28

I've been busy playing Majora's Mask ._. but I'll try to find some time even though I rarely used Zquest. Most testing I'll do will be with the Player btw.