Flashback to god knows how long ago!
I was making the engine for the ecco the dolphin zzt game and I was using the type of transport where the passage duplicates on the player (called the koopo method, apparently). So I end up with a passage that I want to turn back into a dark blue solid. Now, there is no way to do this so I decide that, for now, I'll just #put e blue solid. But I fucked up and #put e #blue solid. Now I don't know what the fuck it means when a solid is #blue, but holy shit it motherfucking worked and I got a dark blue solid.
Flashforward to today!
I am reading the user articles and there is this article about the koopo bug. This reminds me of how that thing ended up working out for me. So I test it out, see? And #put e #blue solid or #red fake or whatever makes a black solid, except when there is a passage there. In that case, the passage becomes a solid of the passage color.
So what I'm asking you all is what the fuck?
As long as I'm making a new topic, let's talk about this 'koopo bug'. With Ecco, I have encountered maybe a hundred bugs, and they should all be fixed at this point. So I wonder, does this koopo bug happen all the time, because I'm not sure if it has happened to me.
I hope post this makes sense because I've had a few and I don't want to go back and change things around.
#put e #blue solid
Moderators: Commodore, Zenith Nadir
- superbowl shuffle
- Official Clamp School Defender
- Posts: 418
- Joined: Mon Apr 07, 2003 4:52 am
- Location: CAsE SenSiTiVe
#put e #blue solid
[size=75:lh51rn9h][b:lh51rn9h]When the 5 o'clock whistle blows, so do I.[/b:lh51rn9h]
[/size:lh51rn9h]
[/size:lh51rn9h]
-
- viovis
- Posts: 48
- Joined: Tue Oct 05, 2004 3:55 am
- Location: jorja
- Contact:
- superbowl shuffle
- Official Clamp School Defender
- Posts: 418
- Joined: Mon Apr 07, 2003 4:52 am
- Location: CAsE SenSiTiVe
I always mark on the title screen when I begin a game and I created the first world file 11:16 PM Sunday July 27, 2003. But that was several weeks after I had started on the engine. So I've been working on it for a year and a half, though I haven't touched it much lately. Also, I had created a similar but much simpler Ecco engine around 2001 or so. I nearly finished the first level and am a few boards into the second. I have ideas for about seven levels.
[size=75:lh51rn9h][b:lh51rn9h]When the 5 o'clock whistle blows, so do I.[/b:lh51rn9h]
[/size:lh51rn9h]
[/size:lh51rn9h]
Yeah, this has been known for a while. It isn't a solid, and there's nothing special about #blue, #red, etc. Basically, when you #put certain things that don't actually exist (like a #blue), it bugs out and places some weird high-number element instead of giving the regular error. In this case, the element has a blank character, meaning that you just see a solid background color. When you do it over a blue passage, you get a white-on-blue element with a blank character, so you just see the dark blue background.
I haven't been able to find consistency in the keywords that cause these errors. One nonexistent element name (I forgot what the name was) creates what looks like a green text element, and often crashes ZZT.
I haven't been able to find consistency in the keywords that cause these errors. One nonexistent element name (I forgot what the name was) creates what looks like a green text element, and often crashes ZZT.
-
- viovis
- Posts: 48
- Joined: Tue Oct 05, 2004 3:55 am
- Location: jorja
- Contact:
the green text thing was called a slider... not a sliderns or sliderew, but slider... and it only worked if you changed someting to a slider... and if it didn't crash it would ask for every parameter if you pressed enter on it..... and if you tried to remove the stats of it it just became text.. I'm sure there was another thing you could call it to appear.. i just remember slider worked.. but yeah, it ask the duplication rate, the intelligence 5 times, every question in zzt basically, if it didn't crash..