Sub 15 will never happen. It's literally impossible. A lie, a myth, a farce propogated by the government to mislead the ignorant. Anyone who thinks it's possible is stupid and should feel ashamed, and can wallow in their own lack of intelligence. This is an irreversible fact of speedrunning and simply cannot be challenged. Go cry about it, nerds.
Hi, Can "Multiple Valve Games" be added as a "multi-game" game type and as part of both the "Half-Life series" and "Portal series" https://www.speedrun.com/multiple_valve_games
Thanks!
debug mode is allowed to be used as long as you do not use any debug mode features during your run. essentailly, you can have the debug mode on, but you cant actually use the commands or teleport to screens during your run.
to turn on debug mode in the normal, non-everest client, navigate to where you installed celeste, and enter the folder titled "Saves," in this folder, you should find "settings.celeste" Open this file with the text editor of your choice (ex: notepad). Near the bottom of the file, you should see <LaunchInDebugMode>false</LaunchInDebugMode>. Simply change that false to a "true" and the game will launch in debug mode.
good luck with your ILs!
locked because im a terrible moderator who wants to abuse their power by stopping a very relevant conversation about speedrunning portal.
yup! its an older version of portal that is often more stable than the current steam version and allows easier edge glitching/save glitching among other small changes.
it is recommended you use the source unpack version of the game if you want to run portal
Hi, I was going to link you to the ultimate portal guide, but i realized the 18 legacy route was missing, so I made a video for it.
I hope it's helpful.
For any other questions for routes, I would recommend consulting the Ultimate Portal Speedrun Guide (linked in guides or at http://bit.ly/PortalSpeedrunGuide ) or ask in the portal speedrunning discord, as many runners do not actively check these forums.
as someone who's part of the minority that plays with keyboard, i completely disagree with this decision.
my major concern with this is that someone who looks at the leaderboards would assume that a certain method of input gives an distinct, notable advantage, when this is entirely not true.
i also agree with the fact that this would make submission process just a tad bit more inconvenient than it needs to be. i also foresee people meming the submissions, and people meming over meme input methods that should be included.
however, i do think it is interesting to see what input method players play on. i'm sure many players would be supportive if you'd like to find this information out other ways, i.e. creating a survey among top players.
hi, this is a glitch and NOT allowed by the rules. thank your for bringing this to our attention! there are lots of portal runs to verify so its pretty easy to skim through submissions and calling it a day, which is why runs like these end up getting verified.
i have removed the run in question, if anyone has anymore runs that they believe conflict with the ruleset please let me know,
could you maybe delete your account
spidda cute af btw haha
at the end of the day, play with whatever input method you enjoy more.
however, if you want anything close to a competitive time, it is essential to play on kb+mouse.
you're right in the idea that the aim is slower on controller, however you need to realize that aim is the biggest part of the portal speedrun. i know you mentioned you wanted to run glitchless, so this point is irrelevant to you, but for ABHs (a movement glitch used in every other category) you need to jump right when you hit the ground. on kb+mouse, we bind our mouse wheels to jump so we can spam jump inputs. there is no equivalent on controllers.
so to answer your question, keyboard is a lot better, however play with whatever you find most comfortable or have the most fun with
Portal Stories: Mel ( https://www.speedrun.com/mel ) is marked as a modification of Portal when it is really a modification of Portal 2
speedrun_save "vault"