The restriction amount of states allowed for the toggle command, and for aliases, have been lifted. You use an unrestricted amount of states which may be helpful for reducing the amount of binds required for viewsnaps.
Due to concerns over possible advantages, the changing of any game models, including the player model, is now banned. Textures can still be modified so long as they follow the restrictions outlined in the rules.
Following community discussion, all Glitchless runs are now beholden to a sensitivity limit of 10.0. In-game sensitivity must not exceed this value during both full game and individual level runs. All individual level runs that utilized sensitivities above 10 will be retroactively rejected, while any full game runs will be grandfathered in.
Hello everyone, Inbounds No SLA Unrestricted and Inbounds No SLA Legacy have been renamed following a poll in the Portal Speedrunning discord server.
Inbounds No SLA Unrestricted -> Inbounds No SLA
Inbounds No SLA Legacy -> Inbounds Legacy
This change is to better distinguish the two and shorten their names. No changes to their rules have been made.
Inbounds No SLA Legacy and Unrestricted have now been separated into their own categories. This is a purely aesthetic change.
The rules for Inbounds No SLA Legacy have been updated to better clarify what it is and is not allowed.
Seamshots are now banned everywhere except for chamber 17. This currently only has an effect in chamber 05. Sensitivity is capped to 10.0 for the category and only two decimals of precision may be used. (1.23 is acceptable, 1.234 is not). Leniency may be afforded to accidental violations of these limits, at the discretion of the verification team.
The existing "Inbounds" individual level category has been separated into "Inbounds" and "Legacy", which follow Inbounds and Inbounds No Sla Legacy full game category rules respectively. Existing runs are currently in the process of being sorted into the new categories. Some runs may qualify under both categories. In these cases, you may wish to re-submit your Legacy PB to Inbounds to maintain PBs in every category.
sv_max_queries_window -1 has been added to the command whitelist. If you suffer from long freezes during saveload segments, this command should fix it.
Hi everyone!
Following the recent vote, viewsnaps (using precise sensitivity values to move your camera an exact amount) is now banned in Inbounds No SLA Legacy.
Additionally, the standard protocol in Legacy going forward is that new tech is banned by default. New tech will only be allowed if a vote finds a 2/3 majority in favor. Seam shots remain allowed unconditionally in Legacy. All other categories are unaffected.
You can read more about the outcome of the vote in this document.
Hi everyone! A few recent discoveries have sparked debate about the Inbounds No SLA Legacy category and what should/shouldn't be allowed in it. We'll be holding a vote this week to determine the path forwards for Legacy. There are three decisions to be made:
- Whether Legacy should receive a "tech freeze", where new discoveries are banned by default
- Whether seamshots should be banned in Legacy
- Whether viewsnaps should be banned in Legacy
Each vote will have multiple options for you to rank from most favorable to least favorable. These options are explained in detail on the poll. If you have any questions, feel free to ask in the rule discussion thread.
The poll will run until Monday, 25 August 2025 4:00 AM UTC.
Only votes from players who have a Legacy run on the leaderboard (or in queue) as of the 17th of August will be considered. You can submit your response using the link below: https://docs.google.com/forms/d/e/1FAIpQLSemCaW3u1inWnPNWQpyJoYB-5AI38Y80zJtjn0ahUbR3GJUuA/viewform?usp=dialog
Inbounds runs that use Item Save Glitch to perform 02 skip will now be accepted to the leaderboards. Please provide demo proof for any such runs.
An update has been released for SST that adds the command sst_portal_resetisg. This command removes Item Save Glitch and is to be used in place of restarting the game. This is a temporary solution while a more robust and legitimate one is developed.
The reasoning for allowing this is to make the new 00/01 Out of Bounds routes available for use runs. You can see an example of one such route in this video.
The preferred use of the new command is with the bind "save quick; load quick; sst_portal_resetisg; load quick". This will appear similar to a saveload, but will remove ISG.
It's important to note that this does not mean Inbounds 02 skip is allowed as the issue with out of bounds props is yet to be resolved.
It was recently discovered that it is possible to set your mouse sensitivity to a value so high that the game considers it infinite, leading to several new glitchy techniques being discovered.
The rules have now been amended to ban these new techniques in both Inbounds No SLA Legacy and Glitchless.
This ban does not apply to Inbounds No SLA Unrestricted, or individual level speedruns submitted to the Inbounds category.
As of today, 17/03/25, ghost door is officially banned in all runs, due to it not being possible without pre run setup (if a setup is found from game launch the rules will be updated accordingly). All previous full runs utilizing it will be grandfathered in, and all previous ILs utilizing it will be rejected.
Starting now and currently being grandfathered, all console runs will be manually retimed with load times removed. This process will be redone by the verification team anyway, so don't worry about doing it yourself when submitting. Massive shoutouts to Tactix1 for doing this basically single handedly.
Starting today, runs that require video proof (top 25) and runs beyond that where video is the only form of proof, now require audio, as recording audio for only the game is now a native OBS feature.
Starting today all top 100 runs must submit using demo proof, with video proof also being highly encouraged, and still required at top 25. If you dont know how to set up demos yet, please follow the setup tutorial found here. All runs submitted before this not using demo proof will be grandfathered in.
Starting today, we will be using a more accurate timing method which includes “Tick 0” from demo timing.
LiveSplit should automatically be updated to include the “Tick 0” timing method. For those of you using the bootleg SourceSplit, you may need to manually install the new SourceSplit found here: https://github.com/thisis2838/SourceSplit/releases
To confirm you are on the correct SourceSplit version, do the following:
- Open LiveSplit
- Right click and hit Edit Splits...
- On Game Time and Auto Splitting, click Settings
- Click the About tab
- This should read as SourceSplit version 3.3.0.0 or higher
Note: ILs will be retimed at a later date. Currently all ILs are only off by 1 tick only since they complete the level without save/loading. Since this is internally consistent, submissions to ILs will use the old timing system until we automate a way to update them all at once.
Update: as of November 1st 2023 all ILs have been retimed to include tick 0. Please submit accordingly
What does this mean for you?
- All future runs using in-game time must be using the newest version of LiveSplit. Runs not timing tick 0 will be rejected.
- All Top 10 runs in main categories will be retimed and updated to include all 0 ticks missed.
- All other runs will be grandfathered in i.e. not be retimed.
- Category extensions which require demos will be retimed.
- Your own gold splits and com gold sheet will now be off by 1 tick per save/reload during that segment.
- ILs should be submitted WITHOUT 0th tick for the time being.
Example of what the new SourceSplit does and looks like: https://imgur.com/a/uXmZKNZ
The restriction amount of states allowed for the toggle command, and for aliases, have been lifted. You use an unrestricted amount of states which may be helpful for reducing the amount of binds required for viewsnaps.
