TittenIgnition wrote:In a tournament as small as this, there's no point in trying to exploit "vague" terms in the rules.
dqopb wrote:Thanks TittenIgniton. I wish all the players were as conscious as you.
gnj wrote:I appreciate your input but can you be a little more specific?
gnj wrote:You of all people should know how complex and explotable this game is and how challenging it is to create a perfect ruleset. This is merely a safety net in case someone comes up with something BLATANTLY unfair which wasnt covered in the rules (hence the phrasing "common sense of fair play").
khetti wrote:Specific how? There are obs which are consistent that the rules disallow. How many or how severe should not concern you.
khetti wrote:Begin by learning what Random means...
If you can describe how to consistently reproduce an OB it probably isn't random.
We are not interested in theory lessons
But maybe you dont really wanna contribute, but just tell us how stupid we all are?
khetti wrote:I gave you a negative definition:If you can describe how to consistently reproduce an OB it probably isn't random.
It covers every case, I think.
You're free to point out exceptions.
We are not interested in theory lessons
You can't act responsibly without a theory, but ok, I'm not your tutor.
i. It is not allowed to utilize OBs, that were created by using a weapon in places where the OB detector doesn't show a possible weapon OB. When an overbounce is created by weapon usage, the player has to reach the maximum height possible with one contact shot from the used weapon. This rule does not apply to sticky OBs.
ii. It is not allowed to utilize OBs on slopes, or OBs created by jumping from a slope onto a level surface (the slope being the origin of the jump).
iii. It is not allowed to utilize OBs that occur hitting ceilings of any shape (straight, slanted, curve).
iv. It is not allowed to utilize OBs that may randomly appear after triggering jumppads and jumppad-like triggers
Keep in mind: Demo validators have the right to reject demos with engine/physics/map exploits not listed in these rules, if they violate the common sense of fair play. It is the responsibility of the validators to judge that. If you find a trick / bug / map exploit that you are unsure about, it is highly recommended to contact one of our validators or admins to confirm its usage.
oranje wrote:This basically says that if you don't play the map the way the mapper intended it to be played, your rec doesn't count. Isn't the whole point of defrag to find new routes and tricks? Might as well have strafe pads or a 2x rocket room as a dfwc map.
Since when did the df community become so afraid of its own tricks?
oranje wrote:
oranje wrote:
oranje wrote:
Arcaon wrote:Give an example of a consistently reproducable OB that breaks the current ruleset, and I promise you the current ruleset will be changed. Aloha!
gnj wrote:Why do you quote me like that? I said we dont need theory lessons AT THIS POINT IN TIME (since the schedule is tight and theres other stuff to do).
gnj wrote:And that it would be better if you stepped in directly (while a specific example/phrasing that we can just put inside the damn ruleset - since you seemed to have the solution already), instead of going back and forth and wasting time.
Overbounces which cannot be reproduced consistently are forbidden. OBs resulting from unpredictable or inaccurate processes, or requiring manually unachievable preconditions, must not be used.
oranje wrote:Since when did the df community become so afraid of its own tricks?
TittenIgnition wrote:You people who combat these rules so heavily do so only because you read and interpret literally everything that is said, but don't see the reason they're there: we want every run to be reproducible, and purely about skill.
Tittenignition wrote:A good example of a random OB that's unfair is w3sp's run on chronos_cpmrun3.
Tittenignition wrote:These things should be up to the demo validators: if there's an OB that goes against these rules, but it can be easily reproduced, it should be allowed.
Tittenignition wrote:stop nitpicking
Tittenignition wrote:the demo validators will hopefully not be so picky as to disqualify legitimate runs, but also should not allow completely random occurrences such as random OBs.
© 2011 q3df.org. Designed by Zeences. All Right Reserved.
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group
Prostylize Darkgrey style by Ishimaru Design