Hey shattered throne runners, we'd like to notify you of a timing change for duo/fireteam runs.

We're changing the duo and fireteam timer start points to match with the solo timer start point. Previously, timer would start: "when you MOVE PAST the door at the start. For resets that teleport in front of the door all runners have to put their back to the door and timer will start on first movement."

It's now been changed to read: "Timer begins when fresh runners reach the respawn point or when a respawn runner makes their first input."

This was done to allow for faster resets, especially in regards to bad entrance rng, and to match solo timing with duo/fireteam timing for less confusion.

• Swifty

Mod Update: The one about the PC/Console Split

Hey fellas - it’s been a long time coming, but we’re finally splitting PC and Console on speedrun.com. While it was always possible to filter runs by platform, we recognize that the advantages of playing Destiny 2 on PC are enough to warrant giving Console its own category. You’ll now see Sub-Categories for both “PC” and “Console” on both Destiny 2 and Destiny 2 Story pages. An example of what it will look like is shown below.

As you can tell, it currently shows “No runs”. We can’t just flip a switch and make everything proper, so we’ll be transitioning the site over the next couple days. In the meantime, we welcome any feedback that the community may have on this change.

Another point of contention we need to discuss is that Console records will never show up on the Individual Level Main Page. We wish it didn't have to be this way, but the site isn't the most customizable for our needs. It's an unfortunate situation, but there is little we could do about this bar changing the way we do to the split, and we feel our approach was the best option. While the runs are re-added, you can still find console records under the console subcategory as normal, but should a console run beat it's pc counterpart, the pc run will be the one to show up on the IL Main Page.

In the coming weeks we'll be looking to make more changes to the site and better clarify a lot of our rules. Be on the lookout for changes to come.

Cheers

-Destiny 2 Mod Team

Mod Update: The one about the PC/Console Split

Hey fellas - it’s been a long time coming, but we’re finally splitting PC and Console on speedrun.com. While it was always possible to filter runs by platform, we recognize that the advantages of playing Destiny 2 on PC are enough to warrant giving Console its own category. You’ll now see Sub-Categories for both “PC” and “Console” on both Destiny 2 and Destiny 2 Story pages. An example of what it will look like is shown below.

As you can tell, it currently shows “No runs”. We can’t just flip a switch and make everything proper, so we’ll be transitioning the site over the next couple days. In the meantime, we welcome any feedback that the community may have on this change.

Another point of contention we need to discuss is that Console records will never show up on the Individual Level Main Page. We wish it didn't have to be this way, but the site isn't the most customizable for our needs. It's an unfortunate situation, but there is little we could do about this bar changing the way we do to the split, and we feel our approach was the best option. While the runs are re-added, you can still find console records under the console subcategory as normal, but should a console run beat it's pc counterpart, the pc run will be the one to show up on the IL Main Page.

In the coming weeks we'll be looking to make more changes to the site and better clarify a lot of our rules. Be on the lookout for changes to come.

Cheers

-Destiny 2 Mod Team

Hey Runners!

Mod update time. So, the Revelry is here, a limited time Destiny 2 event, and it kind of breaks the game. Supers and abilities can be gained at rates far above what they normally could be, which means if we allowed people to run around with Tonics and super spamming, the boards would be in a pretty bad state after the event's end. We could just stop submissions for the next 3 weeks, but we'd like to try and come up with a better solution to this issue then "Just don't run lul.", and we think we have that.

You can still submit to any activity you wish during the Revelry, PROVIDED YOU FOLLOW THE RULES BELOW:

• No player is allowed to have a Tonic active for any reason during the run.
• If your run takes advantage of orbs generated by Revelric Light (The always active perk that gifts orbs on precision kills), it may be rejected.

This way, runs done during this event should not differ from runs done outside of this event, and any records set during the next 3 weeks still have the same potential to be contested and broken as any runs set outside of this event.

Thank you for your understanding, - Swifty, Destiny 2 Super Mod

Hey Runners!

Mod update time. So, the Revelry is here, a limited time Destiny 2 event, and it kind of breaks the game. Supers and abilities can be gained at rates far above what they normally could be, which means if we allowed people to run around with Tonics and super spamming, the boards would be in a pretty bad state after the event's end. We could just stop submissions for the next 3 weeks, but we'd like to try and come up with a better solution to this issue then "Just don't run lul.", and we think we have that.

You can still submit to any activity you wish during the Revelry, PROVIDED YOU FOLLOW THE RULES BELOW:

• No player is allowed to have a Tonic active for any reason during the run.
• If your run takes advantage of orbs generated by Revelric Light (The always active perk that gifts orbs on precision kills), it may be rejected.

This way, runs done during this event should not differ from runs done outside of this event, and any records set during the next 3 weeks still have the same potential to be contested and broken as any runs set outside of this event.

Thank you for your understanding, - Swifty, Destiny 2 Super Mod

Our last announcement regarding changes to the solo dungeon was the result of a misinformed situation. The mod team has since gotten together to attempt to amend this mistake. We've updated our rules for Shattered Throne as follows:

Timing: TIMER START SOLO: • Timer begins when fresh runners reach the respawn point or when a respawn runner makes their first input.

TIMER START DUO/FIRETEAM: • Timer starts when you MOVE PAST the door at the start. For resets that teleport in front of the door all runners have to put their back to the door and timer will start on first movement. *Note: We are looking at potentially changing Duo/Fireteam start time to match Solo's. More updates on that will come later down the road packaged in with other changes.

SUPER USAGE/PERCENTAGE: FOR SOLO: • If the run begins with more than 30% Super (edge of class ability on the side bordering the weapons panel) then super cannot be used until the timer reaches 2:00. Mod discretion may be used to validate as long as no foul play or super abuse is suspected.

FOR DUO/FIRETEAM:

• If the run is started with the super bar having reached the end of the melee ability icon (ie. 20% or more) and the super is used before at least the 2 minute 30 second mark after the first input, the run is invalid. Additionally, if it is reviewed by moderator(s) that the player would have had their super by the time they used it if the player had started with 20% (or less) super energy, then the run will be valid.

Please continue to provide your feedback and to criticize any changes we make in the future. We're open to have community discussions whenever we find the time.

Thanks, - Swifty

Hey gamers, quick heads up regarding the solo dungeon. We've been in a bit of a sticky situation recently in trying to find a good place to start the timer. The extremely short version of our issue was that when you're doing a fresh run, the adds will be consistently better knit together for the first symbol than they will anytime you respawn, which gives fresh runners the advantage. As a solo player, you have no way to reset the encounter to get the advantageous fresh add pattern. The solution we've come to is to change the timer start for the dungeon to when the first symbol appears (which is after you clear the first wave of enemies, including the knight). We feel this is the best way given the nature of the adds in this encounter to keep respawn runs competitive with fresh runs.

In addition, due to you now killing enemies before the start of the timer, we needed to adjust the super rule. After some testing and number testing, we've updated it to read as follows:

If the run is begun with more than 50% super it cannot be used until the timer has reached 1:30 seconds. Additionally, if it is reviewed by moderator(s) that the player would have had their super by the time they used it if the player had started with 50% (or less) super energy, then the run will be valid.

Feel free to enquire if you have any questions or have a better idea for how we could do this. PS: The blade barrage exploit non-acceptance footnote was taken out of the bottom of all runs, as, well, you can't do it anymore. No need for it to be there anymore xD

Thanks, - Swifty

Hello, this is Swifty, Destiny 2's current Super Mod. This is a quick "Mod Blog" update for our discord and website. If you aren't already in the discord, click on the Discord tab between Guides and Streams. Now then, update time.

Resources

• Updated our Guides with some helpful techniques:

INTRO TO RUNNING DESTINY 2 NEW GAME GUIDE MOVEMENT GUIDE FOR ALL CLASSES WORLDLINE SKATING TITAN FLYING SPARROW LAUNCH GHOST SKIP SWORD SKATING RETIME RUNS WITHOUT LOADS

Website Updates

Small name changes:

Scourge Of The Past

• Category 1 swapped positions with Category 2 and changed to "Any%"

  • Rules: This category allows for any glitches and exploits not banned in the rules above. Note that runs submitted to this category may be removed from the leaderboards if a certain glitch or exploit used in the run is patched.

• Category 2 swapped positions with Category 1 and changed to "No Major Glitches"

  • Rules: The Ball Duplication Glitch/Exploit is banned in this Category, all other glitches are fair game.

Last Wish

• Category 1 changed from "All Bosses" to "All Encounters" to better reflect the nature of the raid.

  • Rules remain the same.

• Category 2 changed from "Any%" to "Wish%" as the only difference between the two categories is that one allows Wishing.

  • Rules remain the same.

NO RUNS SWAPPED CATAGORIES OR WERE DELETED DUE TO THIS CHANGE

Get Role (DISCORD)

A while ago I created #get-role to allow server members to get their own roles. I introduced this as a "type for role" variant, but we all wanted for it to be "reaction based" from the start. 2 days ago I found a good reaction role bot, so I was finally able to update the getrole. Simply clicking the reaction should update your roles now. You can get platform and color roles. #get-role. Enjoy!