Hello Everyone! If you didn't know, we've been busy testing out a plethora of new rules for fullgame speedruns! We're excited to share these new changes today and begin implementing them in new runs and on the leaderboards! Feel free to ask questions or for assistance with the new rules and tools and how they'll affect your runs! Please note: the new rules presented here only affect PC categories.

Static Track RNG Rule

Based on community feedback and interest, we have decided to allow runners to “choose” which track patterns will occur for the required track gathering segments in both Xeno% and Shara% categories for PC platform. This removes an approximately 2 minute and 10 second variance between the “best possible combination” and “worst possible combination.” The Static Track RNG creates few changes in routing. Any routing achieved with Static Track RNG is technically possible with unmodded Variable Track RNG, but is less likely and creates a reset-heavy mentality for perfection.

Runners are now able to set which track patterns they would like to have during a run using the MHW Speedrun Tool available here. Once installed and setup, runners can choose which patterns appear during the track gathering segments for Pink Rathian, Nergigante (after first Elder’s Recess visit if needed), Kushala Daora, Teostra, Vaal Hazak, Namielle (MR), and Blackveil Vaal Hazak (MR). Simply pick which number pattern you would like during your run, then implement the mod using the “Load to nativepc” button. The number identifiers for each pattern use the game’s internal numbering. This is not the same as the current number system used in JalBagel’s Track Gathering Guide. Track patterns must be selected and implemented BEFORE the run begins and cannot be edited DURING an attempt.

For reference, the fastest gathering combination presently is:

• Pink Rathian in Wildspire Waste: 1
• Kushala Daora: 1
• Teostra: 1
• Vaal Hazak: 3

Reminder: you do not need to use these patterns in your attempts. You can use any combination of possible track patterns available in the tool. This is only a recommendation based on the current world record and other top time runs.

To implement Static Track RNG into the leaderboards, a new variable will be added: Track RNG. There will be two options:

• Random - This indicates the track patterns in the submitted attempt are randomized and not modded.
• Static - This indicates the track patterns in the submitted attempt have been modded by the MHW Speedrun Tool and are not random.

Since no major routing changes are anticipated, the new variables (Random and Static) will be tracked on the same PC leaderboard. You will be able to filter by the variable similarly to the weapon variable filter currently.

(1 of ...)

FPS Restrictions

For PC categories, FPS has been identified to have the following effects during gameplay relevant to fullgame speedrunning:

• Framerates above 60 FPS result in faster text mashing and menuing resulting in significant timesaves during long dialogue segments.
• Framerates below 60 FPS result in faster animations during the Barroth Escort Section causing the Handler and Researchers to progress to the Barroth cutscene faster.

Due to these findings, the following restrictions on FPS have been implemented:

• Framerate Maximum: 144 FPS
• Framerate Minimum: 30 FPS

Changing framerate DURING an attempt is PERMITTED but must comply with the restrictions noted above.

The rule is designed to avoid a “pay-to-win” environment where better PCs achieve faster speedrun times than worse-performing PCs. Additionally, a framerate below 30 FPS is only achievable using external tools.

To assist in verification, runners are requested (not required) to show their framerate settings during the run. The preferred time to show framerate settings would be during the Stealth Tutorial in the Ancient Forest following the Zorah Magdaros introduction. Generally, there has been enough time for runners to make settings changes while waiting on the Handler to progress the tutorial segment. This makes for a convenient moment to check/verify framerate at the start of the run. Once again: this is not required, but requested. However, the MHW moderation team reserves the right to reject any potential “Top 3” run if framerate is not verified during the submission.

CSM & Load Removal for Shara%

It was our intent to remove load times and cutscene times from the current Top 3 Shara% leaderboard runs. Load times present a significant amount of real time in the current timing. It seemed removing only cutscene time presented an unfair disadvantage to existing runs. However, JalBagel’s July 13, 2024, Shara% speedrun was completed in a time of 6:53:10.37 IGT (with loads and cutscenes removed). This is approximately 1 hour and 40 minutes faster than the current first place Shara% speedrun with cutscene time removed only (mosstkm’s Shara% in 10:43:20 / 8:33:29 with cutscene time removed).

It is unlikely that load times accounted for the 1 hour and 40 minute difference, but rather a fundamental improvement to the speedrun is the cause. Therefore, we believe it is appropriate to implement the IGT timing method to Shara% without removing load times from the current Top 3 speedruns. Instead, cutscene time will be removed from the current Shara% speedruns to display both a RTA and IGT timing method. A total of 2:09:50.400 will be REMOVED from runs completed as RTA (without the autosplitter) presently on the leaderboard and submitted in the future.

(2 of 2)