Bavaria, GermanyI see what is causing this now: the latest runs section of series works the same way the front page works. As such, it also uses your front page settings for followed games which with your particular settings means they don't show up.
Tenebrae: The latest run showing up for me is from today, so I don't see a problem. Keep in mind that the latest runs section tends to be cached for an hour or so at most.
I don't think so, except for the fact that nicovideo was added to the list of sites that gets embedded automatically.
The main distinction is that it's possible for the site to check whether a video was submitted, which it does. I'm the first to admit the checks aren't infallible and with some malicious intent users can circumvent the checks, but a lot of bad submissions are blocked that way, before wasting a moderator's time.
How would a 'Runs require timer' option be enforced? There is no way for the site to determine whether a timer is shown. If it's going to be up to the moderator who reviews the run to enforce it, there is no benefit to it being a site option over simply being added to the rules by the moderator.
In certain high-profile cases a game request might be accepted before release, if that release is imminent.
For a game that may or may not be made with a potential release in the indeterminate but certainly not anywhere near future? No.
^
The Emulation field was required but had no possible options which is a mistake on the side of the game mods, you did nothing wrong. I've updated the backend code to prevent such a state being possible. I've also made the error message a bit more informative.
Contacting the game mods is still the correct action, though for the time being the Emulation field is no longer required.
Apparently there were invisible spaces in the end tags as well, fixed the post.
Regarding the topic, being able/having to specify which emulator is used is something that has been on my to-do list for a long time, though it hasn't gotten to the actual planning stage as of yet due to focus elsewhere/lack of time etc etc.
Now assuming that's been added, it would be great to be able to blacklist emulators on a game-by-game basis. (Or whitelist, though I don't think that fits that well?)
In the cases where an emulator is just bad period such as here, a site-wide block should be used for simplicity and consistency, but only for those cases. Say an emulator is bad for 75%, fine for 25% of the games, that should not be blocked site-wide but game-by-game. Ideally they would be blacklisted by default but can be allowed game-by-game, but that might become too convoluted implementation-wise (especially since that shouldn't be possible for a 100% bad emulator).
As I said this assumes the emulator is already specified. Implementing requires considering some design questions.
Given that we're interested in site-wide blocks, there's very little choice but to maintain a site-wide list of emulators. This will probably get a bit messy when having to split certain emulators up by version and potentially in keeping the list up-to-date. Does anyone have any estimates on how long that list would be and how often in would need to be updated (=how often are there significant new releases for emulators that are actually used)?
Since having to think about spelling, acronyms and typos when using a text field to specify the emulator would be a nightmare, a drop down list seems like the best way to present it. You run into the requirement of needing a comprehensive list again but blacklisting based on a text field would either be a mess or miss most of the time. As you mentioned, we'd want this to be mandatory. However, it shouldn't be impossible to submit runs of which the emulator (and/or its version if relevant) is not known (e.g. when submitting an run that's a few years old, or mod submitting runs by other players (when setting a leaderboard)). Additionally, none of the existing runs will have the emulator set so we certainly need to support an 'Unknown' option. That said, while supported it should not be encouraged. Most new submissions should know it so they should specify it. As such it should not be the default option but a conscious choice (not saying no-one will pick it when they shouldn't, but I expect most people will just specify the right thing).
In the OP you mention adding a notes - obviously there would be an indication of banned emulators but I don't like the idea of otherwise having hardcoded messages - they'd inevitably end up being either too limited or too generalized in scope as well as be messy in the code. Being able to add recommended emulators sounds like an interesting idea on paper but I'd imagine that in practice it would end up over-complicating things both backend and frontend.
I realize I went kinda heavy on the implementation side of it since that's most relevant for me but I feel it should still be relevant for the discussion as a whole.
Oh_DeeR: There's an invisible space between 'quote' and '='
[quote]Requested games/series that have not been set up 2 weeks after being accepted, will be deleted. For more information check this thread.[/quote]
Your game request was accepted, but since it had not been set up 2 weeks later it was removed again in accordance with the above rule from the request game page.
That's actually something completely different: You added PC/Console subcategories, but the existing runs didn't have either subcategory set, so didn't appear in either. I've used the 'Apply default to all runs without a value' button in the edit game menu, so now all existing runs are in the PC subcategory (and consequently show up again). If there are any that should be in Console instead, you should still change them.
That being said, there should really be some indication if there are runs without subcategories set, and a way to view them from the leaderboard. I'll see when I have time to look into that.
The list of followed games in the nav bar is no longer limited to 15 games.
Jesse_Porter: All of the runs verified in the last few days that I checked were emulator runs. In the game settings for Golden Axe, the relevant option is set so that emulator runs are 'Hidden by default', so they don't show up on the leaderboard unless you change the Emulators filter to a different setting.
Actually ffz emotes don't trigger without an ffz- prefix, so it happens because Twitch accepted 'Badge' as an emote name. I've added it to the blacklist.
It should show up in the platforms list if you click the 'Show obscure' button.
Rubberduckyassassin3: New3DS already exists on the site; Are there any significant differences between the 2DS and the 3DS for speedruns?
WeaponLord: Are you planning on requesting games that were released on the Vectrex? Which ones?
PogChamp PogChamp PogChamp PogChamp PogChamp PogChamp PogChamp
