I dont think we should allow quicksave/load because no other p2 Game allows it also the cheat used to see in the oob areas should be banned! So just the Rules of Portal 2 with diffrent timing!
I disagree, you take away the OoB glitch and this game becomes mega boring. If a bunch of you feel really strongly about this, maybe a separate category is in order, but as far as I'm concerned, I want to make this game as fast and as cool as possible, I don't understand the arbitrary decision to ban something just because other games do, making this game slower and less interesting.
Also, let me ask you this, can you give me a reason that saving/loading should be banned, without mentioning that the other mods ban it? What was the reason for doing that in the first place? Especially when it enables new skips and faster runs.
FYI, as far as I know there's no ban on saving and loading in Aperture Tag, it's the activator for the cutscene skip in Escape.
Quicksaving/loading is not allowed in P2 because its meant to be single segment thats the offical reason. I don´t agree with this rule either because Super Reportal but thats not my business. So I would not have a problem with quicksave/load being allowed! For the oob thing its different because the command is protected by sv_cheats so a different category would probably be the best solution. The thing is atm there are not really enough people running this game so i would say we wait a bit and see how many people are interested at running this game and if there are enough we could split it in categorys.
For the Aperture Tag Cutscene skip you can avoid quicksave/load by killing yourself or load the autosave.
While it's true that the OoB glitch uses sv_cheats 1, sv_cheats 1 DOES NOT need to be activated during the run, it's something that can be done before the run started, I keep forgetting to do it beforehand so I end up doing it during the run (which wastes time, btw). I agree that sv_cheats 1 should never be activated during a legit run, it's dodgy af, but in this case it doesn't have to be.
Bind this to a key: "save oob; sv_cheats 1; noclip; sv_cheats 0; load oob"
You'll be able to see out of bounds until you restart the game or activate noclip again.
Also, the saving/loading ban was implemented before any skips or glitches were found that use it, I think. It made sense then, it stopped people taking the easy way out with difficult tricks, it doesn't seem relevant anymore since it's use allows entirely new glitches to be used.
I agree with PsYcHo. The reasons for saving & loading being banned do not apply here. The OoB view glitch can be activated before a run, eliminating all risk of cheating. If it becomes necessary, seperate categories could be created, but at this point in time, it doesn't make sense to do so as too few OoB related strats have been found.
What does he have to gain from me advertising his mod? It's not like he's selling it. Do you have anything constructive to add to the conversation? An actual reason for why we should ban this stuff maybe?
Getting the "noclip viewing glitch" with sv_cheats shouldn't be allowed in the first place. You should use "r_drawallrenderables 1" instead.
r_drawallrenderables 1 differs from the noclip view so I don´t thinks its a good alternative...
How is that not useful? Is it still too hard to see in OoB? You can't get a legit run with noclip/sv_cheats.
Noclip is stil activated during the run. You think its turned off but it never was: sv_cheats 1, noclip (on), sv_cheats 0. You can't clip through the map but it still let's you see the map from the outside/OoB.
You are infact wrong. The order is "save a; sv_cheats 1; noclip; sv_cheats 0; load a". sv_cheats is turned off after using noclip and the movement state before the noclip is loaded. With that noclip mode is deactivated for the player who ran the command, which can also be seen by reactivating sv_cheats and toggling noclip, which turns noclip mode back on. The fact that you can now see OoB is a mere artifact in the code of the game.
Noclip does exactly TWO things: -flying/clipping through the map -seeing the map through out of bounds space
Yes, you load a save where noclip is not activated BUT you load from a state where it is activated. This gives you the ability to see in oob, which is one of the features of noclip.
So what? Just because it is one of the features of noclip doesn't mean noclip is activated, which it isn't. You are thinking that noclip has to be active for it's features to be active, but if you would re-toggle noclip after that skip, you would see it going to ON. Just because it is a feature doesn't mean it's active.
Really? "Just because it is a feature doesn't mean it's active." You CHEAT by "half-activating" noclip. Do you understand now?
