@Xeapnea That can happen sometimes when there is a lot of traffic on the site. When it happens pages won't load sometimes (and you will be directed to a "site is full" message page), and sometimes they will load but the scripts or CSS won't load correctly.
(That happened to me right now on the main page: https://imgur.com/a/6gwP57t)
Just reload the page and it should be fine eventually.
If you are asking about how to add your game to the site, you will have to request it (Read all the rules first): https://www.speedrun.com/requestgame
@Elims Daravae explained it here: https://www.speedrun.com/post/25q0j
To be more precise: When you get better runs, your previous runs are marked as obsolete, but are not deleted from the leaderboard. You can see obsolete runs in a leaderboard with the relevant filter, or in a user profile page with the "show obsolete runs" switch.
@ReverseDmitry There is a link which does exactly that, although not clickable on the site: www.speedrun.com/randomgame
Assuming you ask about the "Best Possible Time" info that is often shown at the bottom, after the splits and the timer; Go to Layout --> Information --> "Run Prediction", and add that.
You will see a new layout section called "Current Pace". To change it into "Best Possible Time" information, go to the layout settings for this new section, and change the comparison to "Best Segments".
Some more information on @Oxknifer issue:
By looking at the API on the runs of the game (Super Cat Bros.), we can see that after unchecking "separate load times", the new displayed time is the previous "time without loads" column. For almost all the full-game runs there was only a real time with loads, and the time without loads was empty. Only the runs which had time without loads (NG+ world 1) have a time column now, but it is probably the wrong one.
By the way, Oxknifer, the times are still there but they are just hidden. If you will check the "separate load times" option back, you will see the times again.
Site suggestions go to the feedback thread. Point 3 was suggested several times.
@Kingslow why did you necro a 2 years old post just to ask an irrelevant question? You should go to this forum: https://www.speedrun.com/streaming_recording_equipment/forum There are plenty of posts on how to record stuff.
You should go to this thread: https://www.speedrun.com/the_site/thread/5twus I didn't find any "Smash TV" series (the Smash TV game itself doesn't belong to any series), so I think the best you can do is request the game to be removed from the Marvel series.
This kinda reminds me of the EZscape video about "glitchless speedruns", where he talks about the general definitions of what is an exploit and a glitch, the ambiguity in those definitions, and how different people or communities may interpret them.
In a similar manner, I don't think you can find a "true" definition for what is an OOB, because you can interpret the term "out of bounds" in several ways. It can strongly depend on the game and the community (especially for your question, "what rules does OOB have?").
I'll try to answer your questions based on my own personal interpretation, and I will give some examples:
-
How to define OOB? I would call OOB as "being out of the playable map". Basically, if the game will have an in-game map (which marks where you can and can't be), I would imagine out-of-bounds to be anywhere where you are outside of the outer bounds of that map. Out-of-bounds might also include being inside a physical barrier where you are not supposed to be, like a wall or a rock. If the playable zone is in a close space, then being above the ceiling will also be an OOB.
-
OOB or Skip? A skip can happen in-bounds or out of bounds, there is no contradiction between the two. Sometimes going out of bounds can save time, but in other times it might be slower than normal gameplay, or serve no purpose for the objective of the game; so in those cases it will not be a skip.
-
Should a glitch always be used? Probably yes. Since most game developers don't want their players to be out of bounds (from a technical/stability point of view, not speedrunning point of view), they create barriers or mechanics that prevents the players from doing so (that is, if the developers put more than minimal effort in their game). So, it will usually require you to use some glitch or a game mechanic in a certain way, unintended by the developers, to go out of bounds. Even when going through a certain wall where the developers just forgot to put a barrier - this might be considered a glitch as well.
Back to (my) definition of OOB - I said earlier that this is going "outside the map". But that means that any skip, no matter how much minor or major, that happens "inside the map" is not OOB. Clipping through a wall or a barrier that separates between 2 playable zones can cause a sequence-break, but it still happens in the bounds of the map.
In Jak 3, they defined OOB as: "Going out-of-bounds is considered to occur if you go outside the natural zone of an area (into void space that is not meant to be encountered during the ordinary progression of an area) or outside the boundary displayed by the in-game map". The game has a hover glitch, that allows you to go upwards indefinitely with the jetboard. It can help you get to unreachable platforms or skip entire platforming sections, but as long as you stay "in the boundary of the in-game map" they don't count it as OOB. (You can check the Jak 3 AGDQ-2019 video here and here, where they talk about that and laugh about being in-bounds, just really really high).
Based on those definitions, I probably would not call your skip in Destiny an OOB skip, because it looks like you are always in a playable zone, but crossing the sea barrier in an unintended way. Just note that I don't know the Destiny game, or what is the intended way to get to that chest, so you or other destiny runners can disagree with me.
To conclude, when you say "out-of-bounds", usually images like those come to mind :) :
Jak 2:
Amnesia - The Dark Descent:
Super Mario Odyssey:
https://www.speedrun.com/Sim1mon/allposts suspicious post that doesn't relate to the thread.