Hello all, I hope you are all well. Now that TU5 is here, the board is long due for an update.
First update is an update to the Qurious Armor Augment System. Before, the ruling for it was very loose as it only asked that you don’t do anything illegal like going over budget. However, as time went by, more was discovered about the augment system on how skills and armor is generated by it. Thanks to our partners over at the Freestyle Leaderboard, we will be adopting this ruling involving the Qurious Armor System.
-Budget must not be exceeded -The 7th augmentation has to be defense compensation -(number of innate skill type before aug) + (number of new skill type after aug) <= 5 --For example, armor piece which has skill type A, B, C, D innately can only have 1 more new skill. Skill type A, B, C, E, F cannot be accepted as a result of augmentation for the above armor piece.
The second update is an update to the Simple Rules category. There was some confusion about the rocks in the Jungle map and what would happen if you procc’d it on accident, especially if you used a weapon such as Insect Glaive or Lance as their movesets would cause the rocks to fall on quite a number of attempts.
-Going forward, accidental rock drops will be allowed and judged on a case by case basis on how much it influenced the outcome of the run.
The third update involves changes in the No Tools% categories and IL runs.
-No Tool% runs will NOT be allowed to use followers unless it is through a mandatory story quest. -No Tool% runs will NOT be allowed to use Starburst Beetles and Marionette Spiders. -All IL runs will NOT be allowed to use followers. Followers are allowed in the any% run because of the moddless environment of them, IL runs will not be granted them because of the mod heavy environment that they operate in. With the lack of damage numbers on them, it is easy to mod their values that is easy to overlook and exceedingly difficult to verify in that environment.
Lastly, the final update will be in regards to the Restricted variable for Freestyle and Simple ruleset. The lack of charms ended up being too restrictive as some weapons suffered heavily from their skill taxes. -Qurious Armor Augmenting and Talismans generated by Vigar and Cyclus melding are prohibited in Restricted.
With this change, it will allow people to still make functional sets while reeling back on the new insane power creep that TU5 has offered.
On that final note, any runs that was submitted during Version 14.0.0 of the game that do not follow the new Qurious Armor Budget rules will be accepted, however, any runs that have been submitted after version 15.0.0 that do not follow the Qurious Armor Budget guidelines will be rejected.
Thank you everyone for your patience and happy hunting!
Hello all. Lumini here. I wanted you all to let you know that I am currently in the process of reorganizing the IL Rise section (Village, Hub 1-7☆) to the current format we have for the Master Rank and Anomaly Research section. This will definitely take some time, but we believe that doing this will be for the betterment of this board as the old structure of the leaderboard causes confusion and frustration as quests get buried in a very long list.
Aside from this, soon, I will also be providing an update to the Simple Ruleset in regards to clarifications and some adjustments, new information on augmenting and charm melding.
Lastly, there will be an update of the rules for the No Tools% category for Sunbreak as it adds in its own new mechanics.
Again, thank you all for your patience and thank you for using this leaderboard.
When it comes to the freestyle category, the run will result in either capturing the monster or killing the monster while doing whatever you can to get it done asap. The question I have for the community is this.
Would you want a Freestyle Cap and Freestyle Kill variable to add to your runs so that you can see whether the person killed or captured the monster?
If the community wants this, the variables will go from Freestyle and TA, to Freestyle(Cap)/Freestyle(Kill)/TA. If you do or don't want the freestyle variable to be split up like this, please feel free to respond to the thread.