Rules

1. Intro

  • Players have to meet the following criterias in order to participate in the Defrag World Cup 2021.
  • In order to participate, players have to register here.
  • Note: It is strictly not allowed to share your account with another player.

2. Client

3. Config

  • DFWC 2021 requires some Cvars to be set in order to allow for consistency of each run/demo.
    Download the DFWC2021 config here
  • Usage: Download the config file and place it into game-folder / defrag /.
    Run the DFWC Client, once the game is running, open console and execute this command: /exec dfwc-rules.cfg After you are prompted with the confirmation message, go ahead and set your name and country for the demos: /df_name NICKNAME /df_country COUNTRY Note: This will not affect your existing config, it will force/add its own cvar values to your existing setup.
    Make a copy of your existing config if you do not wish to do that.

    Additional cvar information: 
            "df_name" must be set to the player name
        "df_country" must be set to the country the player is from
        "timescale" must be set to "1"
        "sv_cheats" must be set to "0"
        "handicap" must be set to "100"

        "sv_fps" must be set to "125"
        "com_maxfps" must be set to "125"
        "g_speed" must be set to "320"
        "g_gravity" must be set to "800"
        "g_knockback" must be set to "1000"

        "df_autorecord" must be set to "1"
        "df_ar_stopdelay" must be set to a value between "1000" and "10000"

        "df_mp_interferenceoff" must be set to "3"
        "g_killWallbug" must be set to "1"

4. Demos

  • Only demos that are submitted before the round's deadline are accepted into the competition.
  • The filenames of the submitted demos have to match the following pattern:

    map[df.physics]time(nick.nationality).dm_68
  • Demos have to start with player's (re)spawn and end after defrag reports map completion in the console (see demo recording cvars below). Demos without start or end are not accepted.
  • It is a good practice to send more than one successful demo. This ensures that you are not eliminated if your fastest demo is rejected for some reason (e.g. corrupt demo, recorded a broken demo, etc.).
  • Only offline demos on localhost servers are allowed. The players net ping has to be 0. Do not play on a dedicated server (no multiplayer demos).
  • It is not allowed to use external means to time player actions (jumping, shooting, view direction change).
    The player has to time actions himself. (no auto jumping, no replaying)
  • Note: Demo validators have the right to reject demos with engine/physics exploits not listed in these rules, if they violate the common sense of fair play. However, this is only a precautional measure and very unlikely to happen. In any case, the player as well as the community would be allowed to appeal to this before the final decision is made. If you are in doubt whether your route will be allowed or not, please reach out to one of the DFWC staff.

5. Cheating

  • It is not allowed to modify the memory used by defrag or its client with external programs during runtime of the game.
  • It is not allowed to use external means to time player actions (jumping, shooting, view direction change). The player has to time actions himself or with help of the allowed internal quake3/defrag features e.g. cg_drawTimer 1.
  • Mousewheel: It is not allowed to bind any actions that alter the movement of a player to your mouse wheel, such as; +forward, +back, +moveleft, +moveright, +movedown, +moveup. Stick to conventional keybinds such as; +button commands, weapon #, chat binds...etc.
  • Bound Rocket-Jumps:It is not allowed to bind both +moveup and +attack on a single button and use it. It is not allowed to invoke by any means any sequence of commands including both +moveup and +attack in it. For example, if you have +moveup bound to one key, and +attack bound to another key, you can press them down at the same game frame, and release them at the same other frame - it IS allowed. If you use a multi-command bind, or a vstr sequence that contains both of these commands (perhaps, along with “wait”-s or other commands) - it is not allowed to use it.
  • It is not allowed to modify the pk3 files of any of the rounds - neither replace bsp files, nor textures, sounds or any other files. The demo must not contain bsp checksum mismatch warning ("Bsp crc: checksum failed").
  • It is not allowed to modify the demo by external software at any time.
  • Yawspeeding: It is not allowed to change your view angles (direction the player is facing) with other means than moving the mouse. This means the usage of commands +left, +right, +lookup, +lookdown, centerview is not allowed.
  • Botting / Replaying / Scripting: It is not allowed to record and reproduce player's input data using special software or hardware to record a valid demo. It is not allowed to execute sequence of commands (triggered by software or hardware) that affect physical player behavior using predefined timing and order. Basically any kind of automation is forbidden, all times have to be set by hand.
  • Timescaling: It is not allowed to manipulate the rate of time defrag works or perceives, using special software or hardware tweaks.

6. Map exploits

  • Map decompilation.
    Decompilation of bsp files is discouraged. We made the bsp files protected this time, so that only the official DFWC client can open them.
    After DFWC is over, regular versions of the maps (playable on any server and client) will be uploaded on ws.q3df.org.
    Besides, the official DFWC2019 anticheat client is unable to open other maps - that is normal.
    If you need to know where some triggers or player clips are located in a map, you can do it without decompilation this time.
    The anticheat client comes with an extra pk3 file and has 4 new CVars for that: 
    	scr_clips_draw "1" - this will render player clips in-game
	scr_clips_shader "tcRenderShader" - the recommended shader (comes in the special pk3 file)
	scr_triggers_draw "1" - this will render triggers in-game
	scr_triggers_shader "tcRenderShader" - the recommended shader (comes in the special pk3 file)
    Usage: download the tcRender.pk3 from the FAQ page and put it in your baseq3 folder. Set a binding like the following: bind <key> "toggle scr_clips_draw; toggle scr_triggers_draw;" Note: the usage of this pk3 and these commands is not necessary. You may use them, if you like, or you may ignore them.
  • Walllingering / Wallbugs: It is not allowed to build up large amounts of speed without moving.
  • Killbugs: Players have to make sure they don't retain any game states of prior attempts to set a time into the current attempt. It is not allowed to exploit behaviour that only occurs when a player restarts the map or kills himself.

7. Streaming

  • In past streaming during rounds was not allowed due to sharing routes and such.
    Cracking down and banning people from competing for doing so is nearly impossible and seems rather unconventional.
    At the end of the day its no different than teams or clans that gather together to share routes among each other.
    Today streaming is a major part of any video game or competition, it plays a huge role in attracting new players, allowing them to learn maps and game mechanics collectively.
    Therefore, if a streamer decides to share routes with their viewers, by all means do so at your own risk.