Hey, about the run, good point, I updated it!

For the second paragraph, I totally agree about the consistency. For the other statements of your message I'll try reach out to you via Discord, maybe we can discuss quickly.

Edit: As reaching out via Discord did not work as expected, I'll add here to your comment. I didn't "give you crap" about the rules, it's not my fault if you didn't read the rules (and after I pointed you to them, that you somehow got mad and blamed me that you were not following them). We can always discuss about rules if we keep it civil and respectful.

Do you have an example run?

Congrats!

According to the site rules (https://www.speedrun.com/support/learn/site-rules):

Game moderators are generally provided 21 days to handle a run submission.

If your run hasn't been verified after that, you can contact site staff.

Sorry I didn't see your run until just now, will look at it as soon as possible.

Added.

The rules have been updated accordingly. Also, see the latest news post.

@TheStrahl The rules say "completing the game", which I read as defeating the final boss - maybe the rules could be clarified in that regard?

Hi, I noticed some runs on the board use emulator save states, for example the run of HopeTrash (start of run), Cheesehead302 (visible at 0:28) and Flamesabre (visible at 0:02).

These are Emulator-only features, and disallowed by the global speedrun.com site rules:

Tool-assisted emulator features such as save-states, re-recording, or frame advance are not allowed.

Save states give an unfair advantage to emulator runners as they are able to do a much quicker run restarts, and runners on real hardware are disadvantaged. (Not sure if RNG manip is possible for Shaq Fu but that would also be an issue with save states.)

To make sure that save states are not used, I think it makes sense to require the recording to include the game start/reset (as it is already the case on many other boards).

I tested the most common Android emulators (Pizza Boy, John GBC, OldBoy, Lemuroid etc.) against the standard test suite I use for all emulators and none of the mobile emulators were accurate, except for Pizza Boy, which failed blargg's tests.

SuperGBC was 0.85% faster on the Mario test and 2.4% slower on the Kirby test (so not even consistent), which makes it unsuitable for speedrunning.

Data: https://www.kleemans.ch/static/gb-emulator-timing/

I ran into a similar problem a while ago. For my latest API project, a Queue client (to see pending runs), I use the plain "/runs" endpoint for a certain category, and iterate through the result pages (of 200 runs each, the maximum amount per page).

The URL would like this: "/runs?game=${gameId}&status=verified&orderby=submitted&direction=asc&max=200&offset=${offset}" with an offset of 0, 200, 400 etc. where you can loop until you reach the last page.

After that you'd have to sort that big list of runs by run time - I don't see any way in the API docs to use the "orderby" for the actual run length.

Seems a bit tedious but I can't think of another way on how to do it. (There is a "/records" shortcut on the /games-endpoint but it can only provide the N top runs, not the N bottom ones, so wouldn't be useful for your use case.)

The two runs in question were removed. As mentioned, emulator-only features (which are not possible on real hardware) should not be allowed.

If it's not possible on real hardware it should not be allowed. Any emulator features like fast forward or skip features, save states etc. are not allowed.

@RetroMaestroHalil did you use the described RetroArch/fixGB setup?

Good point, thanks for bringing it up, will look into it.

Is this a new category suggestion (for SNES)? Can you provide a run?

Is this a suggestion to track the character as additional variable on the board? Why do you think this is worth tracking, are there any differences?

Thanks for your quick response! I requested the game entry for GameBoy and it got approved. So if anyone wants to try their luck on GB, feel free to submit a run :-)

Board: https://www.speedrun.com/loopz_gb

For the moment I created the same categories as for NES, I hope you don't mind! I think they make sense.

Hi, I was playing the GameBoy version of Loopz the other day and wanted to ask if that would also fit in here if I were to submit a run? Or should I try to request a separate game entry on SRC? From a first glance it seems like the versions are pretty comparable.

No, this has to be played on a GameBoy. If you don't have one you can use an Emulator like BGB (https://bgb.bircd.org/#downloads) or Gambatte (https://github.com/pokemon-speedrunning/gambatte-speedrun/releases) to load the ROM provided.

I also added a part about emulators in the Game rules for anyone interested.

I played through the GB version some times and from a high-level perspective they seem pretty much the same. Thanks @itsme_baruch for adding the other platforms (and the new category)!

There are some differences regarding the password system though:

Only one password: DJLRR (Dalton, Jolly Jumper, Lucky Luke, Rantanplan, Rantanplan) for the Buffalo level.

For the GameBoy Color, there are passwords for all levels:

• Stagecoach: RDJLJ
• Painful Gulch: RRDDL
• Saloon: JDJDR
• Train: LJJDL
• Prairie: DLLRJ
• Buffalo: RJLDD
• Ranch: LJRDR
• Rapids: JJLRD
• Cheyenne Mountains: DRLJR
• Jail: RJLDR

If anybody notices some more differences please let me know!