Now that many great runs have been made and the dust has settled, the time has come to revisit, amend, and clarify the rules. The following suggestions are based on existing content and conversations with participating players
If so, here's the rules:
1. You must have PROOF of the time (flag) capture! (See the [sic] 4th RULE!)
2. All captures are to be done with regular (PURE) Nexuiz settings.
3. The quad cannot be used!
4. The Hook cannot be used!
5. The demo or .avi (PROOF) needs to be uploaded so that challengers may view the run.
6. If a demo is uploaded, Please Provide the exact time of the capture. This will eliminate having to watch a demo all the way through.
7. There are two ways of holding a record. 1. Is to capture using any weapon available on the map. This will be displayed as (Weapons) under the record holder section. 2. Is to NOT USE any weapons at all. This is pure running skill. It will be displayed as (No Weapons) under the record holder section.
RE: #2, Changing the timer to display an extra placeholder and sys_ticrate
<mkzelda> div0: how can I display 1/1000 placeholder in speedruns? ie capptured the flag in 30.125 seconds?
<div0> mkzelda: you could, but the timing is not that accurate
<div0> s = ftos_decimals(t, 2);
<div0> s0 = ftos_decimals(flagcaptimerecord, 2);
<div0> you'd change the digit 2 there
<mkzelda> its accurate to hundredths though
<div0> not even that
<div0> it is accurate to multiples of sys_ticrate
<div0> that means usually 0.05s
<div0> it slightly changes physics, especially regarding laser jumps
<mkzelda> you can change mid-run for different sections
<div0> yes, and changing should be absolutely banned
<div0> either the rules should require a fixed ticrate, or it should require you to specify it when posting
<mkzelda> good idea, ill do the latter for now
Conclusion:
1) changing the timer beyond the hundredths is not beneficial
2) sys_ticrate should not by modified during a run at any time
3) sys_ticrate should be specified for the demo be it 0.01, 0.02, 0.03125, 0.05 or whatever else, see my next point on naming conventions.
4) Getting everyone to agree on one sys_ticrate may be a problem. 0.05 is the default for 2.3. 0.0138889 is the default in svn (which is the desired client b/c of impulse 77). Forcing 0.05 means that those who want something more responsive, faster, and more accurate lose out. Forcing 0.01 means some people will have difficulty keeping up on older computers. This is why I've taken the approach of just posting what we use. This info can be found in the demo file too.
RE: Rule 1&5. The demo or .avi (PROOF) needs to be uploaded so that challengers may view the run.
The demo should always be available. Videos are the icing on the cake.
RE: Rule 7 Wep/Nowep
"There are two ways of holding a record. 1. Is to capture using any weapon available on the map. This will be displayed as (Weapons) under the record holder section. 2. Is to NOT USE any weapons at all. This is pure running skill. It will be displayed as (No Weapons) under the record holder section"
This has been elaborated over several pages of this thread, and I'd like to wrap it up.
Nowep:
- You must start at rest, 0qu/s
- You may not use a weapon at any point in the run or during the run unless a weapon is required to complete the map. Examples of this are digdigdig and desert castle. In these cases its still important that there is no speed advantage gained by the weapon. You may not take advantage of the fact that you are firing a button that could also propel you. Use a shotgun if applicable.
- You may not abuse impulse 77 to gain speed.
- You may do whatever else to build speed prior to grabbing the flag.
Wep:
- You must start rest, 0qu/s
- You may use any weapon in any combination, provided the usage, ammo accumulation and health stacking could be accomplished in the game.
- You may not abuse impulse 77 to gain speed.
- You may do whatever else including using weapons to gain speed prior to grabbing the flag.
There has been enough interest in laser only wep runs that we've kept seperate records for nowep, laser, and wep (full weapons)
Laser:
Same as weapons, but laser only.
Naming Conventions
It would be extremely helpful for us to use a consistent filename scheme for our demos/videos. Besides making the files self-explanatory and easy to read, eventually we will have a demo/video repository that will allow you to submit a demo, grep the demo for the captures and time of caps, store details into a db as well as pack it into .pk3 and link the pk3/video, etc.
For now I'd like to propose something like as follows:
mapname(direction)[physics_ticrate]runtime-weapons-datestamp-runner.dem
where
mapname=the mapname nexuiz writes to .dem currently
direction=b2r, r2b, special (blue to red, red to blue, or if weapon is required on nowep, provided only if needed)
physics=nex2.3, nanl
ticrate=0.01, 0.0138889, 0.02, 0.03125, 0.05 (we should narrow this down)
runtime=00.00.00 placeholder, we have maps that require minutes
datestamp=YYYYMMDD
runner=alias
ex.
forkamuse91(
r2b)[nex2.3_0.02]00.12.07-nowep-20080126-mkzelda.dem
spyglass-nex[nex2.3_0.02]00.02.76-laser-20080127-mkzelda.dem
geforce1[nex2.3_0.01]00.03.53-wep-20071225-mkzelda.dem
digdigdig(
special)[nex2.3_0.01]00.02.59-nowep-20071221-mkzelda.dem
df_cpma3x-1[nanl_0.02]00.16.880-nowep-20080230-cantwait.dem
I'm not a big fan of using ()[] in filesnames for the sake of not wanting to escape them, but _ . and - are already used in mapnames, runtime, version number and variables. The order is most important, and what I have given the most consideration. The delimiters could be better but I think the order is good.
Final Thoughts
Keep in mind I'm not trying to change any rules here. I'm trying to clarify existing ones, and suggest ways of improving our system. I'm also trying to set up a standard that will work with future speedrun mods. Please feel free to make corrections or advice so we can nail down a newer cleaner set of rules. [/list]
by Chryyz » Sun Jan 27, 2008 9:52 am 
they are in my list of demo's on nexuiz, but do not appear in the nexuiz/demos folder
