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

A weird (none) Combo to Water Combo Bug

9 replies · 2,091 views · Started 11 September 2007

This is a weird bug. By the way, I had the flippers doing this, haven't tried without it.

Say you go to the next screen and you were on a combo (none), and when you go to the next screen and you are now on a water combo. If you push against a solid combo, you will proceed to raft over the solid combo, all of the way until you reach a screen with a unsolid combo.

So again, you are on a regular combo, go to the next screen to walk on a on a water combo and push against a solid combo right away. You will then start to raft to the next screen.

There's a "potion or life" room in proposed1st.qst up and to the far right of the start point, which you reach by the raft; when you leave you also go from a walkable combo on one screen directly to rafting on the next. How are those screens set up?

My main computer is literally in pieces on my floor right now as I try to figure out why the motherboard is rejecting my RAM; I'll take a look at this bug but it may take me a few days.

DarkDragon wrote:There's a "potion or life" room in proposed1st.qst up and to the far right of the start point, which you reach by the raft; when you leave you also go from a walkable combo on one screen directly to rafting on the next. How are those screens set up?

My main computer is literally in pieces on my floor right now as I try to figure out why the motherboard is rejecting my RAM; I'll take a look at this bug but it may take me a few days.

Is this new RAM, or did it just stop working right?
Do you have a model # and make on your MOB and the RAM, I can do some checking for you if you'd like.

I'm not seeing this in 584. I made 3 screens... Two have walkable combos of type (None), and one between them with Combo type Water. I turn on Flippers in Init. Data, and... Link automatically goes to swimming in the water when I change screens. You most likely have Flag 8 down somewhere on the screen. That's the only logical explanation, as that is what the official quests do to tell where to Raft. Especially on the Potion or Life room DarkDragon mentioned and the Level-4 entrance in the 1st quest. Go south from their screens, you hit a Raft flag. Thus, you start rafting. It's as simple as that. I'd say this isn't a bug... Unless you had the Raft when you did it. You didn't mention the Raft, so...

Map:
x|o
s|s

Lets say, that "x" is a water combo and "o" is a non solid combo (also it can be shallow water as that is how it is now, and I am having the problem). The "|" is the different screens. And "s" is the solid combo.

Start on the "o" and go left to the next screen so you will now be in the "x" combo, and if you are holding the down button against the solid combo, Link will automatic do the raft animation over the whole screen until he reaches a screen with a walkable combo. What is weird is it doesn't show the raft under me, but that may be the fact that I don't have the raft in my quest.

And yeah, I forgot to mention, this is with 584. And no, there is not one flag 8 or any raft flag on my screen. I am 100% sure of it. As it happens to every screen that I have this.

I.....I'm still not seeing it. I just tried it. I have the Flippers on, and I walk into the Water screen. I'm holding down against a solid combo, but nothing's happening except the usual blocking of movement. I seriously can't reproduce this... And yes, I DO have the Flippers. I also just tried using Shallow Water to Water... That doesn't give me the bug, either. :/

I forgot to mention that I have the 8-direction on. Basically I am facing down when I enter the screen and then I will basically raft over the combo. I am going to take a look at it again and see if I am messing something like a quest rule.

Okay, NOW I'm getting it! The way to work this bug is to have Z3 movement on, it seems... It happened for me. Link DOES try to raft over solid combos like this. No Raft appears, and no secret sound is heard. I can verify that this bug exists. >_>