6 minutes speedrun of Half-Life Created 6 years ago2018-07-15 22:13:37 UTC by Shepard62FR

I can't stand speedruns. It's bullshit.

But damn, I have no idea what is going on (hah) in that video, it doesn't make any sense to me how that glitch is supposed to work.

yeah... i don't get it but... cool?

I actually found this really cool from a technical perspective. It's not as interesting to watch as a normal speedrun and I can understand why a lot of the runners didn't want to do this one since it's probably not all that fun to run.

Yeah, it's technically pretty cool but I prefer to watch the more interesting speed runs where you can at least sort-of-tell what's going on.

I enjoy watching speedruns, It's entertaining to watch people go through the game as fast as possible in unpredictable ways, but this one really hurts my head lol.

While I'm not a really big fan of speedruns, I do enjoy GDQ, SGDQ (and derivatives) mostly for the commentary that goes along with the run.

Segmented runs like this though, not so much.

So how does save-warping work? I didn't want to watch a 12 minute video to find out.

@tschumann They utilize the wait command in the command queue to delay a level change when you enter a changelevel trigger, then they save the game with different relative position to the land_mark (being able to move around the level before it changes) once the other level is loaded they load the game and poof you are somewhere else on the new level or something like that, that's how I understood it.

They utilize the wait command in the command queue to delay a level change when you enter a changelevel trigger, then they save the game with different relative position to the land_mark (being able to move around the level before it changes) once the other level is loaded they load the game and poof you are somewhere else on the new level or something like that, that's how I understood it.

That's right, they abuse the fact that "trigger_changelevel" is basically calling "changelevel2 <map name> <landmark name>" with "wait" commands combined with the save/restore stuff in the landmark's PVS by quick saving/loading.

That glitch was fixed in modern Source engine versions where console commands stores their intended execution value.

Ah thanks - makes sense.