I'd like to take a moment to clarify some aspects of our verification process and address a few misconceptions that users might have about the verifiers team.

The verifiers team is made up of volunteers. We don't work for speedrun.com, nor do we receive monetary compensation for spending our own time watching your runs and ensuring they comply with the rules. We are also not robots — we have real lives to manage as well. This means that runs submitted may not get immediately verified, and we might make mistakes during the verification process, such as overlooking a glitch in a glitchless run or mistiming the run's length. To minimize these issues, we have a private channel on our Discord server where we can consult each other on matters like whether a trick constitutes a glitch, how to retime runs, and whether specific actions during a run break the rules. This allows us to reach a consensus on each run's verification.

Another important point to clarify is that you don’t need to be an active or highly skilled speedrunner to become a verifier. As long as you’re knowledgeable about the game and are willing to watch runs, you can be a verifier. The admins of the Discord server also serve as super mods, meaning they can add or remove verifiers as necessary. We also create tools like the autosplitter, which we do for free.

This week, an incident occurred involving a member of the verifiers team, MayC. After being absent for a few months, MayC submitted a few runs that violated one of the submission rules. One of our verifiers, ktc, noticed this and brought it to the group's attention. We reached a consensus that the best course of action was to reject the runs, even the ones that had already been verified.

Initially, MayC agreed with this and resubmitted the runs with footage that complied with the rules. However, these resubmissions were invalid because they were automatically generated by our Tank-Only bot assistant. Therefore, we rejected them again and asked MayC to make new submissions, this time using the "All" control scheme and avoiding bot-generated submissions.

This appears to have been the breaking point for MayC, who then began insulting two of the verifiers, ktc and Radgryd, in an emotional outburst. I took action and removed MayC from the verifiers team for violating our server rules. In response, MayC demanded through DMs that I reinstate him, threatening consequences if I didn’t. I refused to add him back, and he subsequently began streaming on his Twitch channel with the title "Controversy Time: Let’s talk about Radgryd, KTC, and the verifiers :)". During this stream, MayC physically threatened and defamed members of the verifiers team with extreme slander. Such behavior is unacceptable, and as a result, MayC has been banned from participating in our leaderboards and Discord server.

TL;DR: This week, an incident occurred involving a member of the verifiers team, MayC. He physically threatened and defamed team members with extreme slander during a live stream on his Twitch channel. This behavior is unacceptable, and as a result, we have removed him from the team and banned him from our leaderboards and Discord server.

You can see the message log from the verifiers channel below. You can listen to MayC's rant on stream by downloading the audio here.

The following announcement applies to glitchless runs which play the TR1 level Caves. The announcement is in response to the Caves bridge pull-up glitch, demonstrated with visuals by TrexOfTerror in this video.

1. The moderation team will move forward with the ruling that the maneuver is a glitch, as described in the linked video.

   • In summary, if Lara goes through the rope mesh, a glitch was performed.

2. Already-approved runs using this glitch will remain approved but will have a time penalty of 2 seconds applied.

3. There will be a temporary "1 Strike" policy for future glitchless run submissions with this glitch.

   • If a runner submits a run with the glitch, the run will have a penalty of 2 seconds applied but will still be approved. If the same runner submits another run with the glitch, the run will be rejected.

   • This grace period will expire at the end of this year; starting in 2025, all glitchless run submissions containing this glitch will be rejected.

It's been nearly a month and the first patch has arrived to fix most of the issues we mentioned in the previous post. The UB All Pickups achievement is still broken, but everything else seems to be working.

With this, we're ready to open the boards.

Make sure to read the rules before submitting runs!

^^^ PLEASE ^^^

If you have any questions, ask in the Discord.

• TR1-3 Remastered Moderating Team

Hello, fellow tomp speedrunners. Hope you have been enjoying the remasters so far.

Since there are a few bugs that affect the existence of some of the categories, we have decided to wait until they are addressed by the developers. The main issues are:

• Achievements that never trigger
• TR3 NG+ softlock
• TR3 bonus level doesn't trigger

This means that the leaderboard embargo will be extended until the first patch drops. We will need a few days after this update to make sure that these issues have been fixed.

We hope this patch comes soon so everyone can start having fun filling these leaderboards. Enjoy strat hunting/casual play/speedrun routing meanwhile. :)

• TR1-3 Remastered Moderating Team