ch_createairboat
Can’t you bind quicksave (console “save quick”) and quickload (console “load quick”) via the in-game keybinds pane? If so, then that’s equivalent (basically) to typing reload/kill in console.
My suggestion would be to just add a fixed number of seconds to the run for each save deletion instance.
Yes you can, but it doesn’t work for save deletion. When you try to load the deleted saved with the quick load bind it just gives you an error and nothing happens.
This seems like an obvious bad idea simply because not everyone takes equally long to navigate menus, in a similar way to how the old half-second segment penalty was illogical and arbitrary because no computer takes exactly half a second to load every map or save (among other reasons like how segmented runs are segmented to save time and imposing restrictions is blah blah blah).
I’d suggest this is even worse than the segment penalty though, because this actually assumes no variation in human skill, which takes away the competitive element which is the main point of doing SS / RTA runs. Also, having a fixed arbitrary time penalty is practically the same as just not timing it at all. It serves no comparative purpose and hence is not helpful when timing. I guess it’s different with something like a segment penalty which discourages adding a lot of segments, but once a theoretical optimal route with save deletion is eventually achieved (assuming every save deletion saves a large amount of time) there is no point in doing it this way at all.
Also, if some glitch or trick is discovered which allows faster menu navigation (not that that would ever happen) we have to be able to make the timing distinction.
I’d agree with those who say menus should be timed, although if people decide not to bother for simplicity, please don’t add an arbitrary number of seconds. That is just silly.
Reminder that kill is allowed in literally every multiplayer source game
Reminder that i have the most hours in source games so my opinion holds the most weight
[spoiler]:^)[/spoiler]
Not in CS:GO
used to be allowed in mm, not sure if it’s allowed in pugs but it’s allowed in community servers
Babbaj, please don’t double-post unless it’s necessary. In most cases modifying your post and adding “EDIT:” is more appropriate.
‘kill’ is cheat protected in Portal 2.
Which doesn’t matter at all, because it is still something only accessible via the console.
If you’re going to add a fixed amount of seconds for every save deletion, you may as well not add it at all…
So what is the agreed upon ruling on ‘kill’ and ‘reload’ then?
I think they should be disallowed since you need console
Reload’s been allowed since the beginning of RTA. I say it stays.
Kill is iffy. Since you technically take the shortcut of opening menu and loading your previous save with “reload”, you’d technically be taking the shortcut of killing yourself with “kill.” But the problem for both of them arises when you can’t do it in game.
Save deletion requires you to delete the save, so you shouldn’t be able to reload it. But killing yourself quickly with, say, just the crowbar is nigh impossible.
Since I’m for reload, I guess I’m for kill being allowed as well. Reload is quicker anyways.
The only question I have is whether or not the final decisions will be in favor of a ‘better’ speedrun. Because at the end of the day, isn’t that what actually matters? Not the fact that we allow some things yet disallow others, but because it is generally in favor of making a better speedrun (whatever that entails).
“Better speedrun” is kinda vague because some people may think that noclip makes for a better speedrun, which doesn’t mean that you should allow noclip.
But people do run noclip% (however seriously). And it is a separate category, in part, because most people would rather run without it, as well as many other reasons. But this is getting a little off topic…
So most people seam to be fore save deletion (judging by the poll) but what about timing the run. Is every one against the way gocnak did it and if so how should we time runs in the future. I mean if we cant find any one thats willing or capabel of changing source split how could we even time the runs without putting in some arbitrary time penalty for each save deletion (other than going by real time which in my opinion is a terrible idea).
Also i hate to be the guy to bring this up but i think the top time posted here should be changed back to the 1:30:36 or whatever the last none save deletion run was at least for the time being http://www.speedrun.com/hl2
Why can’t the run just be re-timed? Add the time between when menu is opened and the sourcesplit timer is resumed. This is accurate enough for the time being in my opinion.
Also I just want it to be verified that it is agreed upon that Save Deletion is allowed and the menu time should be timed. If so, the use of Save Deletion should continue. It is slowing down the evolvement of the run to not allow Save Deletion until an in-game timing method is at place (this could probably take a long time?). Half-Life 2 is certainly not at a point where ~1 second faulty timing matters. If this discussion is purely about timing method (once again please verify that it’s agreed upon that SD should be timed) then I can’t see why this is such a big deal.
I completely agree
Maxam has a point, you could just continue to use SourceSplit and then just add the extra time taken from menuing manually when submitting runs in future. The only other option is to time RTA and then manually cut out the loads which is a huge hassle to do when you’re PBing so regularly.