Rules update regarding milliseconds, Update*
Hey guys,
due to recent developments 2 new rules had to be implemented.
1. The first rule is covering the situation when two records with the same times up to two decimal places (00.00.50 for example) get submitted in the very same release. What to do in such a situation?
New set of rules:
The XJ record system is using a real time time-measurment system allowing millisecond times up to 2 decimals!
It's not possible to beat demos with faster times in the third decimal place (.00x), if there are two demos with the same times in the first two decimal places the first submitted demo will be accepted (first come first serve).
-> This is based on the fact that the demand interval of the hl engine is not capable of giving solid and valid times beyond the second decimal place 100% of the time (then again timeshifts would be happening in some cases, which would be way harder to determine than the old timerbugs, since they are happening in the decimal areas): Because of the quantization of time measurement in the hl engine in 0.01s intervals the mean error of one time measurement is 0.005s. So the statistical variance for the measured record time is Sqrt[2*0.005^2] = 0.0071. Every time difference smaller than the statistical variance is not significant and only based on statistical effects so it is likely to have occurred only by chance.
2. Obviously the rule that forbid all AMXX plugins was an April Fool that was related to kz.ee's April Fool (newspost). Too bad only a few people understood the connection, that's probably why most of you though it's a boring joke.
/!\ APRIL FOOLS /!\
You are NOT allowed to use metamod or AMXX plugins in your record demos in any way!
/!\ APRIL FOOLS /!\
3. However, I want to use this chance and newspost to explain a few other things. Due to the recent poll simple switch-binds won't be forbidden and won't fall under the following rule:
You are not allowed to use any script or metamod or amxx plugins that give you an advantage to other jumpers.
Please note that scripts with +use;wait etc., however DO fall under this rule rule.
This rules is also relevant when talking about plugins such as jump_prestraf.amxx, which falls under this rule, too. Two demos including this plugin were accidentally accepted by one of our demo admins in the previous releases, probably because he didn't think about this problem: Obviously, all other jumpers didn't have access to this plugin before it was released, also it gives you information about your strafes that are not available with default cs configuration. This information can be used to estimate and see how you have to strafe to get a perfect bhop pre or lj pre (on small areas or maps with bhop ljs)... next time you try to copy it to get the same pre. This makes it two advantages and explains why the plugin never was and never will be allowed.
Note: The two corresponding demos on clintmo_bhopbarrels kz_bhopwarehouse will be removed and the old records will be restored.
Best regards,
XJ Staff
P.S: To read the full text of the edited rules check the extended newspost!
due to recent developments 2 new rules had to be implemented.
1. The first rule is covering the situation when two records with the same times up to two decimal places (00.00.50 for example) get submitted in the very same release. What to do in such a situation?
New set of rules:
The XJ record system is using a real time time-measurment system allowing millisecond times up to 2 decimals!
It's not possible to beat demos with faster times in the third decimal place (.00x), if there are two demos with the same times in the first two decimal places the first submitted demo will be accepted (first come first serve).
-> This is based on the fact that the demand interval of the hl engine is not capable of giving solid and valid times beyond the second decimal place 100% of the time (then again timeshifts would be happening in some cases, which would be way harder to determine than the old timerbugs, since they are happening in the decimal areas): Because of the quantization of time measurement in the hl engine in 0.01s intervals the mean error of one time measurement is 0.005s. So the statistical variance for the measured record time is Sqrt[2*0.005^2] = 0.0071. Every time difference smaller than the statistical variance is not significant and only based on statistical effects so it is likely to have occurred only by chance.
2. Obviously the rule that forbid all AMXX plugins was an April Fool that was related to kz.ee's April Fool (newspost). Too bad only a few people understood the connection, that's probably why most of you though it's a boring joke.
/!\ APRIL FOOLS /!\
You are NOT allowed to use metamod or AMXX plugins in your record demos in any way!
/!\ APRIL FOOLS /!\
3. However, I want to use this chance and newspost to explain a few other things. Due to the recent poll simple switch-binds won't be forbidden and won't fall under the following rule:
You are not allowed to use any script or metamod or amxx plugins that give you an advantage to other jumpers.
Please note that scripts with +use;wait etc., however DO fall under this rule rule.
This rules is also relevant when talking about plugins such as jump_prestraf.amxx, which falls under this rule, too. Two demos including this plugin were accidentally accepted by one of our demo admins in the previous releases, probably because he didn't think about this problem: Obviously, all other jumpers didn't have access to this plugin before it was released, also it gives you information about your strafes that are not available with default cs configuration. This information can be used to estimate and see how you have to strafe to get a perfect bhop pre or lj pre (on small areas or maps with bhop ljs)... next time you try to copy it to get the same pre. This makes it two advantages and explains why the plugin never was and never will be allowed.
Note: The two corresponding demos on clintmo_bhopbarrels kz_bhopwarehouse will be removed and the old records will be restored.
Best regards,
XJ Staff
P.S: To read the full text of the edited rules check the extended newspost!