The Metroid Dread Speedrunning Community is pleased to be able to partner again with [SpeedGaming Live](https://sglive.speedgaming.org/) and our good friend [kekumanshoyu](https://www.speedrun.com/users/kekumanshoyu) to hold another tournament showcasing Metroid Dread, this time in the **[Any% Glitchless](https://www.speedrun.com/mdread?h=Any-glitchless-Rookie&x=9kv83mjd-wle962k8.klr8wp21-ylp6w5rn.jq66533q)** category!

Here are a few things you should know:

**This is an online tournament**. Signups are open to all with no entry fee, but please make sure you are able to follow the scheduling requirements detailed in the tournament rulebook. **You must be flexible enough to potentially schedule matches with international players within 5 days of the matches being made available by the tournament organizers.**

The qualifiers will begin on **July 20th**, and the actual tournament will run from August 5th to the end of September.

Signups will close on **July 27th @ 11:59 EDT**. The earlier you sign up, the more qualifiers you can join!

## Qualifier Heats

Before the tournament begins, there will be eight qualifier matches that determine the bracket positioning.

Qualifier heat schedule (*all times are in US Eastern*)

- Two heats on **Saturday July 20th, 2024: 10:00AM and 6:00PM**
- Two heats on **Sunday, July 21st, 2024: 2:00PM and 10:00PM**
- Two heats on **Saturday July 27th, 2024: 12:00PM and 8:00PM**
- Two heats on **Sunday, July 28th, 2024: 4:00PM and 12:00AM** (technically Monday morning)

**YOU MUST PARTICIPATE IN AT LEAST TWO HEATS**. You can participate in more than two if you would like. In fact, we encourage it because your best time from the qualifiers will determine your bracket positioning.

## Rules

Please read the rulebook below in order to familiarize yourself with the rules:

## [Any% Glitchless Tournament Rulebook](https://docs.google.com/document/d/1TxVr6bh-vheTs_C4L4u0_QKYBFlWnveruryzM0xvQLc/edit?usp=sharing)

## Other Notes

- You are required to join the SpeedGaming Live Discord server to participate: https://discord.gg/eH4qa3Fnew
- We encourage all runners to show up 10 minutes early for the qualifiers and for the rest of the tournament. This helps the staff and admins out *greatly*.
- During the qualifiers, four people will be chosen at random to be showcased on one of the SpeedGaming channels on Twitch.
- There's a prize pool for this tournament! As of this news post, the prize pool amount is $85.00 USD. If you want to contribute further to the pool, visit this link and follow the instructions: [https://matcherino.com/t/sglive24?contribute=true](https://matcherino.com/t/sglive24?contribute=true)

Take care, and See You Next Mission.

The Metroid Dread Speedrunning Community is pleased to be able to hold another tournament showcasing Metroid Dread, this time in the Any% Glitchless category!

SpeedGaming Live 2024 Metroid Dread Any% Glitchless Tournament

> Turbo is a huge win for accessibility, however they cannot compete for a top time.

It's legal now, so yes, yes we can.

Awwww yeeeee I'm ready to go back to one of my categories of origin!

Metroid Dread

Hey everyone, we have a big announcement today.

As a result of continued feedback, the CMs have decided to revisit our ruling on turbo restrictions. **Effective immediately and on all leaderboards, turbo will be allowed up to 21hz. The restriction on missile weaivng with turbo is also being lifted.**

Unlike previous rulings, we did not have an officially sanctioned public discussion before coming to our decision. This issue has already been discussed at length in various feedback threads made by community members, and it was clear that doing so again would only further strain the community. Everybody has already made their thoughts known, so we instead discussed the state of the issue internally and came to a consensus.

We understand many people will be upset with this decision. When it comes to turbo, there's never been a perfect answer. Every ruling has always come at the cost of some part of the community, and as with every decision in the past, we've attempted to balance this to minimize the damage caused. After the many lengthy discussions and an internal revisit, we feel that the positives of loosening the restrictions far outweigh the negatives. We're certainly not happy about upsetting people with this, but it was also clear that not making this decision would upset even more.

Because of how nuanced this issue is and how many factors there are, we've compiled a document with a full explanation for the reasoning behind this decision. If you take issue with this decision or are otherwise concerned/curious, we ask that you please read this document. You can find it [here](https://docs.google.com/document/d/1DoPjSQEcVUqqLqs5gNjN_EFYbb6dDvuHie8_tcwKc_g/edit?usp=sharing).

That said, we will at least summarize the reasoning and have a short FAQ here:

- Why was this decision made?

After considering many factors including (but not limited to) community activity, competitive integrity, controller availability, and runner health, we felt that the pros outweigh the cons. We feel that we stand to gain a net positive or at least not a net negative on any of these factors. The strongest factor was competitive balance, which turbo has been lagging behind in significantly.

- Why not 17hz?

The main reason is controller availability. The doc goes into depth about this, but many 13hz controllers would see no speed increase under 17hz. Along with still lagging behind the best human mash, this would somewhat defeat the purpose. We felt that if we made the cap 17hz, we would have to eventually raise it to 21hz anyways.

- Why not split the board?

Our goal with the boards is to provide an option for every way to view it. It's already possible to view a split board by using filters. While this isn't a perfect solution, it would be worse for those who want to see a combined board to be unable to do so than it would be for those who want to see a split board to need a few extra clicks each time they use the boards. Our reasoning is that it's clunky, but at least usable, unlike the alternative.

- Will this decision be revisited?

We don't plan to revisit this decision. While this has also been the case with past rulings, our principles never changed. We just didn't predict the circumstances changing so dramatically as the gap between turbo and mashing got further. That gap will probably not get that wide again, and even if it does, we're limited by the controller market as controllers over this speed aren't widely available. This shows no sign of changing as controllers closer to 30hz are difficult to make. As of now, we see it as very unlikely this decision is revisited any time in the near future.

Thanks for reading.