Restricted vs Unrestricted has been the cause of a fair bit of drama due to the arbitrary decisions of which bugs are or aren't allowed in restricted. Moving all bugs to unrestricted would cause the category to be inaccurate, as almost all bugged runs do follow the typical restrictions. Changing the categories to Glitchless and Glitched will have almost no impact on how people currently play the game, but will have a great impact on the organization and integrity of the leaderboards.

All runs appearing on the site will follow basic restrictions:

• No racial skills
• No prestacked on-kill sigils
• No precasted rune pets
• No revive enhancements
• No precasting LoyF if you swap off the trait
• No interface bug abuse Interface bug abuse is just as uninteresting as the other items on the list, and it simply is not comparable to other bugs. Abusing Anet's garbage hero panel code is not gameplay. Examples of interface abuse include:
• Soulbeast merge + pet out
• Multiple signet
• Casting skills and swapping them without the slot going on cooldown due to traitline movement

Runs may not include usage of extreme bugs which de-legitimize the run, such as:

• Precasting multiple preparations
• Dealing dps far beyond what should be possible, such as with the shadow flare or renegade trait bugs
• The boss deciding to despawn before the win condition is met

It is clear at this point in our speedrunning scene that a run which does not follow these basic restrictions is exceedingly rare, and it simply makes sense to apply the rules globally. Runs which do not follow these rules will be collected in a google sheet in order to have a complete collection of speedruns. New runs can still be submitted to the site and rejected for the purpose of creating a link to be added to the google sheet.

What constitutes a glitch? There may be arguments over the definition of glitch, or what Anet's intentions are. However, for the purposes of sorting the leaderboards, anything that could be perceived as notably different than a typical run (and therefore not comparable to a glitchless run) should be placed in the glitched category.

Bosses which do not have 1 enrage timer that remains present and ticking for the entire fight must be manually timed. Dhuum submissions can exclude the pre-event as timing can be done based off of Dhuum's health bar appearing, which is at exactly 2:12. It is worth noting that ArcDPS logs are fairly accurate (~100ms off).

However, the timing method most commonly used in raids is Time = [Total enrage] - [Time left]. This means a kill with x:59 remaining will be a x:01 kill time. This timing method is not extremely accurate compared to manually timing the runs, but it comes close and is very simple.

When the enrage timer appears, it ticks down by 1 second within only a few frames. This means for bosses which have their enrage timers appear about 1 second delayed from actual combat, the timer is fairly accurate. This is the case for most bosses, and only stopped being true for every boss starting in wing 4. Instead of having exceptions for these bosses, the timing method will be kept consistent as it still works for comparison purposes.

##Bosses which start with their enrage timer: Cairn Broken King Deimos Qadim the Peerless

##Bosses which have about a 1 second delay before their enrage timer appears: Vale Guardian Gorseval Sabetha Slothasor Matthias Samarog Keep Construct Xera Mursaat Overseer Samarog Soulless Horror Eyes Dhuum Conjured Amalgamate Largos Twins Qadim Adina Sabir