Michigan, USAI've never run 100% actually, so I don't really have any advice for you, especially since you're trying to go glitchless. I would say to limit how much time you take collecting seeds until you can buy them, but I don't know if the 100% routing factors in money for seeds or anything like that. Hopefully one of the 100% runners can chime in on their experiences, or you could try a Japanese run like R suggested!
You'll have to collect every non-consumable item in the game (key items, weapons, equipment), so while that does not require every battlefield to be cleared, you will have to clear all of the ones that give you items.
I was messing with older builds and realize the current patch doesn't have the anti-cheat installed anymore. Beat this time properly anyways so nbd
There are some carts that do have the cloud guy cut in half when he floats away. To my knowledge it doesn't really indicate anything one way or another. I never used to have it happen, but lately I've been noticing it in about half of my runs.
And Zero is right about the transition screen thing. There is 1 frame where if you switch weapons it'll softlock you.
I don't think there's an easy way without actually using the cart. I don't know how to do it but I've seen Fumo bring up a debug screen that I guess can show you the version.
I suggest asking Fumo about it in the Discord because they know way more than I do about it.
Speedrun.com treats uploaded files stupidly. They're not a zip folder, which is why eLmaGus was saying you'll need to re-name the extensions. The instructions are listed on the resource page for the saves.
It just comes down to knowing when to auto, and knowing all the situations where auto will make your partner do something like using heal potions.
So, when you got Meteor I noticed that your inventory didn't have heal potions in the 4th slot. This is what screwed things up. Should be Seed, Sky Coin, Refreshers, Heals in your inventory before buying the 31 potions.
Most likely Kaeli used some accidentally on auto throughout the tree if I had to guess without scrubbing through the VOD.
Tybalt,
The proof change only applies to Any % so if you're intending to still run 100% I don't believe the proof rules apply.
Here is a tutorial I created that goes over not only the Venus Shield set-up routed by Claude, but also general movement/gameplay stuff
If you're looking for a shorter guide for just reminders, here's a Google doc for you
Sorry if there is anything wrong, but I think this is a really good start for anybody looking for the "safer" route through the speedrun.
So they changed the rules before you did the run...
I get that it's annoying because the same thing happened with me with the streaming rule, but rules are rules man. I didn't read them for like a week, they changed, and when I submitted runs they weren't valid. It happens.
"They don't give a shit". There have been two mods already on this post explaining the rules and why those rules are in place. If they didn't give a shit you'd have your runs rejected and nothing would be said.
Just run the game again, do what I said with Voicemeeter or just use game audio, then you'll be good. It's simple.
Dzoni, chill my dude. You can follow the rules or not.
If you NEED music, look up how to use voicemeeter to play music but not have the music output to your recording or something, no need to be a cock.
I'll send a link to the one I've seen here to you Hampster on discord.
EDIT - Turns out I'm an idiot. The run I noticed just had player damage turned on, not set to versus mode. My bad! My point to Dzoni still stands though.
Not trying to be a dick to anybody, but I noticed in the rules that it states
"You have to play the survival mode and not the versus or creative mode.",
and there are runs that do not follow this rule that are currently up.
I don't see a problem personally with using V.S. mode (I guess I don't understand the difference), but if the rule is there then I feel like some runs shouldn't have been allowed.
Yeah, this is a good 'ole crash. According to Calmlamity, it occurs on a specific frame as a screen transition is loading in, and if you press the L button on that frame you will crash. Happens on EMU and cart.
You can avoid this by holding a directional button while you click buttons, or obviously just not touching the shoulder buttons.
I know this is 2 years late, but thanks for bringing this up! I haven't been able to find any way that this would be useful in a run, but I appreciate you coming here.
I went through a slow run today, making sure to create states at any point I thought people might want to practice at. How can I get those on the resources page?
