Derbyshire, EnglandIs it fair? Yes. Is it 100% "right"? Probably not. Either way, it's way too late to change such a rule given the 151 players that have submitted and the 4 years that have passed since this leaderboard was created.
What Captain-No-Beard is saying about there being no way to be faster is not 100% true btw; check out this video by quadrazid:
It'll depend on which package you're using, for example my GoldSrc Package 1.34 is running on latest Steam (SteamPipe), therefore you'll need 99.5 there, however GoldSrc Package 2 is based on a much older client so you'll need to use 100. NGHL also runs on a pre-SteamPipe client so once again you should use 100 there.
I can't really speak much for the CS:CZ runners, but I'm 95% sure their rules are just a copy-paste of one of the old rulesets for the Half-Life leaderboards, so they're most likely inaccurate. In fact, the "No saveglitches" rule stems from a pretty ancient controversy exclusively related to single segment runs in Half-Life. I can't think of any reason why it'd actually be appropriate to ban "saveglitches" from that game. Once again, the recommended fps_max value depends on what client the game is being run on. To my knowledge, the best client to run CS:CZ on is latest Steam (SteamPipe), so it'd be appropriate to use 99.5 there.
The reason we use 99.5 in more recent clients is due to a lazy fix that Valve implemented to solve an issue where the fps counter activated with cl_showfps 1 displayed the incorrect amount by -.5fps. Their "fix" was to just make the game add an extra .5fps to whatever value you specified in fps_max. Therefore, if you use a fps_max value of 99.5, you're actually getting a max of 100fps. If you use a value of 100, you're getting 100.5.
You can use 'startdemos <demo1> <demo2>' etc after launching the game, however it probably won't work if you launch a server or play a demo beforehand.
+bxt_tas_ducktap is a function that automatically performs frame perfect ducktaps when you hold down the key that it's bound to.
Ducktapping is a technique similar to bunnyhopping except with +duck instead of +jump, as in when you tap +duck you will get airtime which can be used to accelerate just like with bunnyhopping.
How does having multiple PBs justify making only the top 3 runners submit their demos? It's your own responsibility for not recording demos when the rules clearly state that's what's required; I don't see why you should be excluded from those rules because you lack knowledge of the engine or "the things to go fast" (as if we're just supposed to take your word for it anyway). I also don't see why fluctuation in time of submissions should exclude you either.
Setting up the game and then actually speedrunning it takes considerably more time than creating a few keybinds to record demos, so given you had the time to do all that I find it pretty hard to believe that you couldn't take a few extra minutes to read the guide and write a few lines in the console.
"Runs done in this category must not use the 'wait' command or any scripts, aliases, macros, turbo buttons, hyper-scrolling and so on.. "
Hi,
Yes, if you use your CD key in Steam, you'll get a collection of the GoldSrc games developed by Valve that are all in their latest Steam forms.
You don't need to use the original WON client; check out the 'Guides' section for info on how to get set up with the correct version.
If someone understands the circumstances completely, then how exactly is their opinion any less valid than someone who runs the game/category? In a community vote they shouldn't get to take part, I agree, but in normal discussion pointing out pros cons etc I don't see why their opinion is any less valuable.
Just thought I'd mention: In HL1 there once was a quicksave/quickload strat that saved a couple of seconds and the majority of people wanted to not use it (in favour of keeping the SS route) so what we said was "you can use quicksaves/loads so that we're not elitist and everybody can submit their run, but you can't use quicksaves/loads to perform RTA-exclusive tricks because we want to keep the SS route".
This situation sounds pretty similar so I thought it'd be worth mentioning it.
This has been due for some time now since YaLTeR developed an in-game/without loads timer for Bunnymod XT.
The rules section has been adjusted to include the following:
¤ Standard competitive timing used is in-game time (without loads). This form is timing is acquired from Bunnymod XT which you can download in the 'Resources' section.
By all means this is a fairer method of timing and makes total sense for competitive purposes.
If you want your PB to stay relevant (i.e not get overtaken by a run that might not be as fast but includes in-game time), you'll need to provide the without loads time. The recommended method of doing this is by cutting out the loading screens in a video editor (download the VoD or make a video if you haven't already). Of course if you already have the time without loads you can just edit it into your submission straight away (I've already done this for some runs that provided it).
Note that you should not use BXT's timer to time demos, as this is significantly inaccurate due to the way that demos work.
Get Bunnymod XT here: http://www.speedrun.com/tools/BXT_01-04-15_vTYoz.zip
Since there is not currently a 'Request category' feature on the site, you may request them here for the time being.
Currently categories are defined by several factors, which are:
¤ Segments - SS vs RTA, in GMC's case SS currently means no saveglitches are allowed, RTA means they are.
¤ Version - WON vs Steam, similar to HL2's 'Old Engine' vs 'New Engine' concept, both versions contain many differences and therefore are categorically separated, note that this is more to do with the client and server DLL files (client.dll and hl.dll), not the client that the game runs on itself since those are often adjustable to match the versions' capabilities.
¤ Difficulty - Easy vs Hard, unfortunately there is not much difference between difficulties in Half-life, only through the amount of damage dealt by NPCs, how much health they have and how much medkits/batteries/chargers provide. This means that difficulty is often down to personal preference or tradition, but is categorically separated due to the minor time difference (on Hard you'll spend more time killing enemies and collecting health/armor, on Easy you'll perform more damage boosts/other riskier strats).
The current necessary requirements for requesting categories are:
- There must be an interesting difference compared to the already established category/s' routes.
- There must be more than one player running it.
There of course will be other factors that will be taken into account when deciding whether the category should be created, but these will vary depending on each one and will often be discussed between moderators/established community members.
There is a 'misc' section for arbitrary or 'joke' categories which will generally be added if there are a good number of players running them.
Most people avoid it by holding the satchels during downtime, it usually takes about 15 seconds for them to 'unstuck' themselves. An example of downtime would be waiting to be teleported to Gonarch's Lair.
Hope that helps.
Well for example, someone submitted some Intended Route runs to the board I moderate (Half-Life) so I had to make a new category for it, however some levels would be completed via the intended route anyway (Anomalous Materials for example in the beginning of the game).
Perhaps a better scenario I could come up with would be if you had an Out of Bounds category and going Out of Bounds was only possible in some levels. This could possibly confuse/mislead players into thinking that going Out of Bounds is possible in every level.
As for the rules, as 'Intended Route' is kind of an arbitrary category in this case, I wanted to be able to set some rules as to what you must achieve in the level for it to be accepted, so that it doesn't gain advantage over a previous run by not following the same objectives. These rules wouldn't apply to a usual Single Segment run of the level.
