That's all well and good, and I've actually tried this as well, but my carriage returns (line breaks) don't work at all anymore, so instead of "Goal:" being in bold and on the next line the actual goal, I get "Goal: [insert goal here]" with the first word in bold. If I put in a second carriage return, I get a new paragraph instead. There seems to be absolutely no way to make something just be on the line directly after something else other than letting it naturally wrap anymore.

EDIT: Also, trying to use a "#" to make a header will put a blank line before the text afterwards just the same.

Is it just me or is BBCode and other formatting completely broken when editing things (at least rules) for anyone else? The big tag seems to no longer work, and things as simple as single line breaks don't show up at all even when just pressing enter for them.

If you go to the full-game leaderboard, there's a "View Rules" button for each category, and yes, your setup would be allowed.

Good to hear! :)

Are you using a controller or keyboard? I ask because it kinda looks like a bit of down+right was pressed which coaxed Tails to walk forward some. If you're on controller, I'd guess the d-pad is a bit finicky (or you're using analog stick and you're not getting a true down input.) If you're on keyboard, I have no idea. This one's strange.

Emulator soft resets are allowed. The rules have also been brought up to date regarding Retoarch and the GPGX core:

"The following unofficial emulators are allowed: Regen, Kega Fusion, Genesis Plus GX (standalone or through Retroarch.) Links to these emulators can be found in the Resources tab.

"For runs using emulators, the game must be visibly reset before a run. When using Retroarch, this reset must return to Retroarch's menu to display the core being used. (Mid-run resets in Retroarch may use a reset keybind.) Any use of a savestate after boot voids the run."

Any way that visibly shows that it is, in fact, a hard reset will work. For Fusion, showing the "Hard Reset" text is the easiest way.

The rule has changed, @jammcg90 . You now just need to visibly show a hard reset being executed in any of the allowed emulators and no longer need to capture the entire window.

PS3 removed, and PS4 and Xbox One added. :)

I appreciate it. I just noticed it when checking out the runs and wanted to make sure things were accurate. (Also to make sure there wasn't some PS2 Regis Millionaire I didn't know about.) :P

I'm looking into running the various NTSC versions of WWTBAM and my research shows that there is no PS2 NTSC version of the game, yet there's a leaderboard here with one run of what appears to be the PS1 NTSC version. Am I incorrect or is this an oversight?

Thanks in advance. :)

The emulator rule has since changed. You no longer need to capture the full window.

First paragraph of the current rules: "The following unofficial emulators are allowed: Regen, Kega Fusion and Genesis Plus GX. Links to these are in resources. For runs using emulators, the game must be visibly hard resetted before a run. Any use of a savestate after boot voids the run."

You just need to make sure to have a visible hard reset (with the text message from the emulator on the screen) at the beginning of the run and you'll be fine.

Glitchless leaderboards have a very low likelihood of happening in this game.

Firstly, defining things such as "No Zips" and "No Clipping through surfaces" isn't as easy as it sounds. For instance, if you press against a wall, the collision detection is technically zipping you away from the wall, which means that "No Zips" wouldn't allow you to even push against walls. "No Clipping through surfaces" as you put it causes issue in specific situations, as well. If you were to go above the screen and fall into a wall that simply wasn't given a solid top, are you following or breaking that rule? There are people that argue both ways in this instance.

As I said in another thread, we've had the glitchless discussion many times and it's far more confusing than it appears to be. The issues I brought up are just a small sample of issues that have arisen when discussing how to execute a glitchless board. We've already gone over all the possibilities mentioned in this thread and it's simply too difficult to define what is and isn't a glitch in this game.

If you go to the leaderboards, there's a button that says "View Rules." Here's a copy/paste of the "Beat the Game" rules:

For PC/Console runs, records are to be timed by adding up the minutes and seconds shown on the in-game timer after you beat each level. Milliseconds are not included due to a bug that causes the game timer to not reset the milliseconds to 0 at the start of every act.

For iOS runs, records are to be timed by adding up milliseconds in addition to minutes and seconds that are shown on the in-game timer after you beat each level. The bug mentioned above was patched in the iOS version.

Any deaths also count towards your in-game time. Add the amount of time lost (time at death minus time when you respawn).

You are not allowed to start the run from Level Select, but if you already started a file from Palmtree Panic 1 you're allowed to start from there.

For verification purposes, it is required to do a visible hard reset on emulator runs and for the "Hard Reset" text to appear in the corner. A soft reset will not suffice, even with "Soft Reset" text.

The reason we don't have glitchless boards is hard to quickly yet thoroughly explain. There are two main reasons. Firstly, it's harder to define what is and isn't a glitch in this game than is apparent. Multiple discussions on the matter have come up for years, and they all lead to extremely difficult (and sometimes outright confusing) questions to figure an answer for regarding a ruleset for such a category. Secondly, there's the argument that it's very easy to accidentally trigger small zips and other random oddities in this game, which could invalidate a glitchless run and lead to many dumb resets.

If I were in your position, I would go ahead and run Sonic & Tails All Emeralds Glitchless and go ahead and submit the time under the "Sonic All Emeralds" category as it would be a valid run for that category (as long as there are no inputs made on the second controller.) Then if, in the future, the glitchless conundrum does somehow get solved, the interest is there, and the board does end up being made, you could submit runs to that board at that time, as well.

It can be an unfortunate situation, but it is one that is much harder to tackle than it seems. If you have any other questions, please feel free to ask.

For God's sake, guys. It's two weeks. Calm your tits and run in the meantime. The mods have made their decision (which I think is a wise one) to wait until we have all the information before making a ruleset. I'll repeat: It's TWO WEEKS. Show some respect for the mods, back up the wahmbulance, and have fun running the game in the meantime. Nothing's stopping you.

The short version is that defining these glitches is a different situation between the average casual player, the average speedrunner, and the average TAS'er. What may seem cut and dry simply isn't. Any attempt that's been made to come up with a cut and dry easy-to-define category for glitchless ends the exact same way. It's a sad truth. :(