Hello,
A recent thread highlighted an issue we've had here for a little while, so we would like to dive into this.
It's no secret that the addition of the MD5 hash has made verification more tricky. Now when you record a run it will save ALL mods you had loaded at the time onto that replay, and that means on our end we need to have these loaded (and in some cases, in a specific order) to be legal for speedruns. Certain mods do not trigger these parameters such as music mod packs and also (some) lua files, and as such can be used if you were using them already, however if there's any issue we will have to reject it.
It might seem a little asinine, but the reason is simple; it's messing up verification. We wish it were pre 2.2.12 days where this would not have changed anything but sadly we are in a tough spot with verifications, and have to take these hard stances against it.
Also you may have seen we cannot approve 2.2.14 runs, this is for 2 reasons:
- This version of the game is no longer obtainable through legitimate means, and therefore we won't consider as we only offer a site to officially validated versions of the game.
- This version caused an issue with the addition of the Shield button which made it unverifiable on version 2.2.15, and since 2.2.14 is no longer available, we cannot verify these runs.
We're sorry for the issues this may cause for some runners. We understand it can be a little strict, however due to the changes forced upon us by the game we have to do what's best for the players AND moderation staff for the future of verifications. We hope you can understand.
Hello,
A recent thread highlighted an issue we've had here for a little while, so we would like to dive into this.
It's no secret that the addition of the MD5 hash has made verification more tricky. Now when you record a run it will save ALL mods you had loaded at the time onto that replay