Naming the categories "Full game _%" is a bit redundant since they're in the full-game section of the site. Just "Any%" and "100%" works perfectly.
Any% runs with SSDs can be kept in the same category as either variable or subcategory.
You can post it here instead: https://www.speedrun.com/botw/forum
Here's a list of games added over 6 months ago that have no verified/new runs, no guides, no resources, no forum posts in over 6 months, and follower counts no more than the moderator count:
http://pastebin.com/iz9n3sS2 -- Has names http://pastebin.com/g9HaqSFd -- Version with links
Either go through them manually (not all at once) or check the database with the IDs to make sure there's no runs since 2017-02-28.
Leaderboard conflict between Robotron X and Robotron 64. I requested the former originally on behalf of Jorf.
The games are, at least at glance, the same thing. Robotron X came out first for PC and PSX, and two years later, ported for the N64. I'm not certain if they should or shouldn't be using the same leaderboard.
If you feel like being fanciful, add an easy formatting option to be able to quickly link games/users or so. Typing something like Super Mario 64
or @SgtKabukiman would change it to Super Mario 64 and SgtKabukiman. If it fails the look-up it wouldn't link anything.
Automatically linking without a formatting option would probably be too intensive on the server and would have a lot of false positives, especially for users.
First post has been updated for everything before this month. Users have shifted quite a in positions and I've added emphasis on the 'weighted record' list. The User sheet is available and the Game and Leaderboard sheets will be added tomorrow.
Even then, autosplitters aren't magic. They check the game for whatever triggers it 60 times a second, which can also be de-synced with the monitor refresh rate/OBS capture rate. The margin of error at most would be ~33ms.
Edit: Actually, because LiveSplit refreshes at 40Hz, the margin of error could be as bad as ~100ms.
Are you using the correct emulator? The Pokemon leaderboard are really picky about the emulator used so you may be using the wrong one.
Evo's Space Adventures belongs in the Space Station Silicon Valley series. You wouldn't think they're the same game from the title, but they are.
"A PlayStation port, developed by Runecraft, was released in 2000, under the name Evo's Space Adventures."
A couple runs return "0" for splits when using the api when it always returns null when they're missing. Example: /api/v1/runs/wzp1o18z
That players bug for api still exists too. Example: /api/v1/runs/kz54d8nm
I didn't want these to be completely ignored, so I'll mention them here.
Without the pause, Learonys's time for Mission 12 would be 6:06. tails22x's segmented time of the same mission is 5:24.
Based on this image of site usages by country posted a few months ago, the only two languages not available yet are Ukrainian and Romanian. Every country above 0.65% are being covered though, which is great.
Ask the series moderators for an anthology game like you mentioned. If they don't respond, try asking in this thread: /The_Site/thread/63nr7
The borders on game covers slightly shrink the image, for some reason. Example:
It can be fixed with: img.border{ border:0 !important; outline:rgba(204, 204, 204, 0.75) 1px solid; }
I think the look of the IL pages could be improved with a slight border between each board, and the min height be the same as a cell with a run.
This is what I use for that: tr.levelrow { height: 51px !important; border-top:rgba(204, 204, 204, 0.25) 1px solid !important; }
tr.levelrow > td.linked {
border-left:rgba(204, 204, 204, 0.25) 1px solid !important;
}
tr.levelrow > td.linked.center {
vertical-align: text-top;
}
Edit: Unofficial games (rom hacks/mods/etc) should be allowed to appear on the front page if there's enough players running said game, like 5 or more.
An obnoxious message should popup if a run is edited and both the date and time (and video if applicable) telling the user to submit a new run instead of editing older ones. From what I can tell, when the verification date is before the run date, it's the result of an older run edited for a newer run...