really makes you wonder if you could use boost ball to your advantage in the first one.. I imagine parax would have thought of that and done that if it were easier/possible though. just looking at the slope, you'd think you could boost right up there.
Also I'm not collecting nova beam that way. Where would I re-enter...?
The next room you go to in any%, i.e. the one above the spider track since the entire point is to skip spider ball.
Also if you're doing the 2nd SW, there's no reason (at least in terms of difficulty) to not get nova beam like that since the wallcrawl is incredibly easy. You can just morph above the nova beam if you want to play it safe.
I don't really want to get into the discussion of "is the nova beam wallcrawl single segment or not?" (which I think it should with a definition change since the entire point of "single segment" is to not repeat segments, and we're not repeating a segment but whatever)
Anyways if you really don't want to die, just do exactly the same thing except in hypermode so you don't die; IIRC you can trigger the pirate fight?
Well MG has a pastebin putting together a pretty convincing argument to allow it but it's his pastebin and I'll wait for him to share it. The TL;DR version, though, is that the intent behind single segment is to disallow retrying segments, and that's not the case here; and the "IGT" that isn't counted for this specific wallcrawl is the time between getting nova beam and dying, which quite frankly nobody cares about.
Single-segment: Beats the game in one sitting. Resetting or using save&quits midrun are allowed, but may be a separate category if they speed things up significantly.
Single-segment: Beats the game in one sitting. Resetting or using save&quits midrun are allowed, but may be a separate category if they speed things up significantly.
It doesn't even mention dying. But I would really like to see that pastebin. Hopefully MG reads the corruption threads.
SDA rules are ancient and are just kinda blah nowadays; not even sure if that's up to date. Most communities have moved on from SDA definitions and stopped caring so idk.
It's whatever. As long as everybody says it's ok I will get to practicing.
Well regardless, the SW is the hard part anyways. Whether it's ultimately allowed or not shouldn't change much on how to do the wallcrawl, and it saves time either way; just less if you disallow checkpoint abuse for this case.
This debate always reminds me of Ocarina of Time and the warp to ganons castle as a child.
I say allow it since it isn't for optimization, but required for a sequence break. Late reply, I know.
I do have a reason for posting here: What triggers the first pirate homework landing site? For that matter, what's the trigger that makes Dane say he's in orbit and will let you know when he's ready to attack? Aaaaand what's the trigger for the Valhalla landing site?
I'm doing a cheat assisted run for the hell of it. Since I started with all items I was hoping I could avoid bryyo altogether like i did with Norion. Also, the reason I wanted to know about the dialog was because it would happen on the way to fight ghor. Side note: sucks that boost and spider don't work until you collect them, even though they're in my inventory. And plasma not able to weld but still able to melt stuff.
I forgot about screw attack, which is extremely stupid of me considering I had just posted that leaving bryyo ice with SA was what triggered Valhalla. (so it would be required to go there even with moon jump)
EDIT: I'm guessing I know the answer to this but I'll be wondering if I don't try. Is there any way, ANY way at all, to change what button needs to be pressed for Moonjump, like maybe a change to the cheat itself? Or the one used for boost? Not being able to use boost sucks. So does sacrificing Moonjump seeing as that was the entire point of the run in the first place. Hell, even a way to enable/disable moonjump at will would be nice.
You could probably modify the code but don't ask me exactly how you'd do that. I'd try looking up how the codes are structured and try to find documentation on how button presses in codes works.