Changed the levels for minotaurs familiars, so it should be more accurate as it can be
What have you done in this MR?
- Changed minotaurs stats. changed levels, str bonus, matching ATK Bonus/DEF bonus
- I have added bonus to match attack bonus of battleaxes, and match platebodies (for example Rune minotaur - ATK Bonus matching Rune Battle axe, DEF Bonus matching Rune platebody)
- i did it the same way as adding levels to match combat level, used runescape.wiki Rune platebody revision back to january 09, then edit source to the the stats. i left the str bonus out of the bonuses because i already determined str bonus for their hits
- https://oldschool.tools/calculators/combat-level - Settings for calculation:
- Adamant & Rune Minotaurs combat level doesn't match, because the hitpoints is higher, so i give them 5 more levels according to the other ones so the levels are higher than the "weaker ones". because of the hitpoints to match the combat level they should have less stats than the "weaker ones"
- https://oldschool.tools/calculators/melee-max-hit
- According to maxhits, i have changed the str bonuses for "melee" and because special attack can hit higher at some cases, i used the str to the magic str bonus, because the magic one i needed to select a spell
-
- sources i have used: runescape.wiki from 2009 january - Click Edit source in the right corner of the page
- https://runescape.wiki/w/bronze_minotaur?action=history&year=2009&month=1&tagfilter=
- https://runescape.wiki/w/iron_minotaur?action=history&year=2009&month=1&tagfilter=
- https://runescape.wiki/w/steel_minotaur?action=history&year=2009&month=1&tagfilter=
- https://runescape.wiki/w/mithril_minotaur?action=history&year=2009&month=1&tagfilter=
- https://runescape.wiki/w/adamant_minotaur?action=history&year=2009&month=1&tagfilter=
- https://runescape.wiki/w/rune_minotaur?action=history&year=2009&month=1&tagfilter=
Are there any tricky things testers should keep an eye out for?
-
No -
Yes, as follows: -
I have tested these changes thoroughly. -
This requires extra testing due to changes to architecture or other similarly risky changes. -
I used the Thanos Tool for any JSON edits where possible, and have attached screenshots of any changes. -
I acknowledge that this contribution will be released under the AGPL license.
*** NOTE: If Gitlab complains about pipelines stating that you need to "Validate your Gitlab account" there is no need to worry. You do not have to do this and it is only occurring because OUR pipeline tried to run on your fork. While it's preferred that you do validate your account, you can safely ignore/dismiss this message from Gitlab. ***