Hitless Rules
Please be aware that this list is a generic overview.
Each game in the Team Hitless roster has its own individual rules.
We kindly advise checking each game’s comprehensive ruleset before attempting your hitless runs.
A ‘hit‘ is broadly defined as a loss of health and/or a stagger caused by an enemy.
The following examples are also classified as a hit.
- Damage from player-triggered traps.
- Using a shield to block an attack, with the exception of a perfectly executed parry or deflect.
- Falling to your death.
The following examples do not classify as a hit.
- Environmental damage from static features such as lava, water, swamps, spikes, campfires etc.
Damageless Rules
Items, consumables, rings, armor, spells, etc. which boosts players hp temporarily (or while wearing) and then goes back to initial hp (eg. Ring of Favor and Protection in DS1, Prisoner’s Chain in DS3 or Radagon’s Soreseal in ER, etc.) are not considered as damage and are allowed.
New Game Plus - Rules
For Non-Fresh Start NG+ Runs:
NG+ runs without fresh start for the website are allowed for runners who already have a hitless run in that game. Per each game there are specific rules, e.g. starting levels, items, etc. which you can find on the game pages. There won‘t be Worlds First for this category.
Modded Runs - Rules
Modded Runs is a category allowing weapons to be spawned in using tools such as Cheat Engine or a Practice tool for Weapon only runs and for any kind of Randomizers (Item/Enemy/Fog, etc.).
For Weapon only runs the weapon has to be spawned in at the very start of the game, or at the soonest point available (depending on the game). All runs are categorized as Modded and displayed separately from regular runs on the website.
Submitting a Modded run is only eligible for team members with the game-relevant hitless role. Modded runs cannot be submitted for team entry, ‘world’s firsts’, or to acquire Discord roles.
Visual Mods - Rules
Visual mods are permitted for specific games, provided they do not offer any unfair advantage to the player or alter core gameplay mechanics. Please refer to the specific game pages or inquire within the team discord to confirm whether your mod is allowed or the run may result in a rejected submission.
For all games, any visual mods containing NSFW (Not Safe For Work) content are strictly prohibited.
Rules for Submissions
For First Time Submissions:
For First Time Console Submissions: Due to console recording limitations, we can accept separate recordings if there is overlapping footage and no missing gameplay. A minimum of 1 minute of overlapping gameplay is REQUIRED for these types of submissions.
For Runs After Team Entry:
A single continuous offline or online recording is the standard for submission. However, single game runs and marathon runs are allowed to be submitted in multiple consecutive streams. Offline recordings can be used for the first part of a multi-part or marathon run. However, consecutive parts must be streamed online with vods highlighted (if on twitch) in case verifiers request proof of online presence. For all parts of a multi-part run, quitting out with IGT after the first segment AND loading the save file with IGT for the start of the 2nd online segment MUST be shown. This applies for all consecutive parts. You may do a private stream on Youtube or Twitch to not have an audience. Runners are allowed to edit their multi-part runs into one continuous YouTube video for submission, but should include twitch highlight links in the description to show proof of consecutive streams and IGT showing/loading. For Console Submissions: Due to console recording limitations, we can accept separate recordings if there is overlapping footage and no missing gameplay. A minimum of 1 minute of overlapping gameplay is REQUIRED for these types of submissions.
For All Runs:
- The videos or streams should all be a single link. On Youtube you can create a playlist of all the videos, on Twitch you can add the streams to a collection. Please make sure you provide a non-expirable link (eg. non-higlighted VODs from Twitch will expire after a certain amount of time) or the run may not be verified.
- Gameplay must always be shown.
- Ingame sound effects must be audible all the time. Muting boss music and voices is fine. Short interruptions while tabbing out are fine as well.
- Crashes do not invalidate runs.
- The video needs to be of watchable quality.
- The video should only be of the relevant run, you should not be sending the entire VOD of irrelevant sections if only a small portion of it is the actual run.
- When starting a new game, do not cover the game version/patch number. Certain games ban specific patches as listed on the their individual page, for all other games it is fine.
- Runs with evidence of toolassists, such as macros/Cheat Engine/other external software, that are not explicitly permitted for the game in question are not allowed and will be rejected.
- The use of a turbo button, scroll wheel on a mouse, or similar tools for quality of life (ex. scrolling through dialogs) purposes is allowed. However, the use of these tools to achieve a gameplay objective (ex. rebind the attack button to a turbo button or mouse wheel) is not allowed.
Quitouts
- Being at the game’s hub (Nexus, Hunter’s Dream, Firelink Shrine, Majula, etc.) or after resting at a bonfire or its equivalent for Team Hitless games.
- Ending a segment for a multi-part/marathon run. Please note that no enemies or traps can be aggroed before the quitout or your run will be rejected.
- Game specific exceptions which can be found on individual game rule pages.
Failure to meet any of these requirements lead to your submission being rejected. Certain runs and circumstances may have exceptions to these rules, feel free to ask a verifier about any conflicts between your run and the rules.
Every game has also specific rules which the community vote on Discord