Vehelits works different than every other enemy in the game. Most enemies are on a specific spot, it's easy to find, you just look for their shadow and line yours up with theirs'. Vehelits doesn't have a shadow. Your position doesn't matter so long as his head doesn't move too high or too low to hit. That's why most will hang around the bottom quarter of screen, because you can jump to hit high and punch when he's low. It's helpful for me to think of Vehelits as a 2D character, who can only move along the front of the screen while your character and every other enemy is in a 2D.5 game. Good luck, I hope this helps :)

You're not overthinking it. I'm the same way. I probably have a dozen different Genesis controllers. I prefer the Genesis 6-button (it has a loose d-pad that lets me input fast).

I grew up playing on a 6-button pad. You'll always play better on the pad you're used to. That doesn't mean you can't learn to play better on a new pad.

Here's the question: Does your current controller have a design flaw that would be fixed on a different controller? Like how sor3 uses 6-buttons, a 3-button controller would limit you.

Here's the next question: Would my current controller work fine if it was in better condition. I've opened a lot of controllers and had to replace a lot of d-pads and buttons. These things break. Sometimes they just need a cleaning, other times you have to throw it away and get a new one but often you need new rubber membranes which are inside the controller.

Retrospy is the software that I use to capture my inputs. You don't need to learn to solder in order to capture a Genesis controller.

Look up Arduino, male DB9 Breakout Board and a DB9 connector. You take your controller, plug it into a DB9 with a Y-splitter. One DB9 split goes into console the other goes into the male DB9 Breakout Board, that goes into the Arduino and the Arduino plugs into your pc via usb.

You'll probably need one or two Genesis controller extension cables. Sorry if this was cryptic, long time since I've done it and I should be sleeping already. Let me know if you get stuck and I'll show you pics of my setup :)

Abadede always breaks early for your first attack, so you can only do a 2 punch and he'll break on the 3rd punch. After that, you can 3 punch him. If you 2 punch him, you have to wait a little between the 2 punch loop since Abadede needs to move/attack in order for his break to reset.

Most every enemy will do a head bob on the ground before they get up. Watch R.Bear's bob. If you do a defensive-special and he hits you, you d-specialed too soon. If you hit him with the d-special, you've done it too late. Watch the bob and find a good time to d-special where he doesn't hit you and you don't hit him then use that timing. Hope that helps :)

Save States do effect the RNG of the game. I've proven this on stream with the start of the Mr. X fight, where he swings away from you on one save state and toward you on another.

The game appears to lock into an RNG% on console start, even with resets the games RNG seems locked. For example, on one console power-up the level 6 ninjas may have a 90% chance of grouping for an Atomic Drop where as the next console power-up they only have a 10% chance. This is why I sometimes power-off my console when I keep getting bad RNG in the same spots. Or, why I switch strats during a certain part since I've had bad RNG with my primary strat.

The RNG of the game appears to be by the frame by the pixel. Your actions effect enemy behavior depending on which frame/pixel you are on. This gets mixed with RNG lock so you may get the same result with the same actions on one power-up but a completely different RNG lock on the next. Just watch any top speedrunner on the first section of the first level and you'll get an idea of how random the game can be.

That's my experience with the game. I think reset is a good idea. I can go into more detail on any of this if people want.

This was already done and it was reversed. Stop separating the runs. Change it back.

If you want to implement something big like this, why don't you run it by the community first to see what they think. Personally, I think this is the worst.

SoR2 - Extreme Mania Hack is a ROM HACK created by Eskayelle: http://www.romhacking.net/hacks/4821/

This Hack is intended for the most extreme Mania players or for anyone looking to have some fun and see how far they can get. The Link gives a good description of what you can expect in this hack and is also where you can download it.

You have to have your own (hopefully legally obtained) copy of SoR2 ROM and then patch it with the hack. Good Luck!

Any questions?

There's original console and everything else is emulator. PS, Xbox, Wii, Switch, PC; it's all emulator.

NeGAtiv4k, you just keep it on Sega Genesis then tick the emulator box. Too many different types of Emulators on PC to list them all.

They just use the time of the video.

Whatever direction you are facing when you hit an enemy causes them to face you. The same thing happens when they hit you and you automatically turn to face them.

If you attack Abadede in the air he will face you, then you have to hold the opposite direction so when you land you grab him from behind. If you play the video in slow motion you can see the inputs I'm using. Jump, hold down, attack, hold opposite direction. Then when I land I turn and grab his back then I suplex him.

Made you a video, hope it helps:

made a video, hope it helps

Good find, I didn't know about this one. Here's my Abadede run:

With Axel you need to face away from Jet when you jump kick, otherwise you'll hit him too far away from yourself. Then you get under him and wait for him to try and grab you, jump-down-attack and you have him.

Zamza starts in blocking mode, so you have to grab him as he fades in and then forward-special. After that he shouldn't be in block mode. You don't have to backwards jump, just jump away as he gets to his feet, jump back towards him, grab him and forward-special.

this video has a section where it explains the backwards jump and the glitch "slow jump" which makes backwards-jumping a lot more difficult if you have a slow jump.

The last run that was submitted, that wasn't you, was months ago. We're not struggling to keep up. This site allows 3 weeks to verify. Obviously I don't want to take 3 weeks to verify a run but if it does take longer then it's probably because the moderators are inactive and a change is needed.

Sorry, we don't need an extra moderator right now. Still, it's nice knowing that if we do need one in the future, you're willing to help out. Thanks.

I don't think we need another moderator. I could be wrong, if so you're welcome to change my mind, Diogo.Asgard. Also, Congratz on the really good runs!

@IwerSonsch I agree with you, my GameShark example doesn't really work. My mistake.

If we're talking about one button press being remapped to another button press; that's fine. In the case of remapping the analog stick to a single button press, that is a different story. The analog stick is not a button. It does not function like a button. Let's say Mario can move at 3 different speeds when you hold up, if you convert this to a button then Mario can now move at 1 speed. If we convert the 3 speeds to 3 buttons then you would be making 3 buttons 1 button.

My example once again, doesn't really work because an analog stick is not a button. The problem is usually from the direction of turning one button press and mapping it to 2 buttons to give an advantage. This is more the opposite, this is more like a macro, taking multiple buttons and converting it into one.

I think one button for one button is fine. Multiple buttons to one button is not okay. One button to multiple buttons is not okay. Converting analog to digital is not okay (since, to make it easier to understand, it's basically multiple buttons to one button.)

In my mind there are only two questions:

1. Should an outside source be allowed to change the way the game plays (in this context)
2. Should analog to digital be allowed (converting a range of movement to a single button, basically a macro)

Let's pinpoint the issue:

Should the Mario 64 speedrun community allow an external source, which is altering the way the game plays, in their N64-console speedruns?

What if this exact same thing was done with a GameShark? Would that be allowed? If not, why not?

I talked to Lotus, he's very friendly. I got the impression that if he was asked, he would remove a run even if there wasn't any reason to remove it; he seems to be very accommodating.

For that reason I don't have any plans to ask him to remove his run or to remove it myself.

"The question was "do we allow 2 same character", i say yes as long as people want to do it and will provide runs. For now we do not need to create one for this run only." <---agree