RPG Attribute System 5.0.1

Fixes

Attack Power, Protection and Toughness no longer get overridden by other mods

RAS used to apply an attribute by overwriting the stat's base value. Another mod, a KubeJS script or a datapack that also writes the base value of attack damage, armor or armor toughness replaced RAS's value, so the points you spent did nothing. This is common in large modpacks.

RAS now adds its bonus as its own attribute modifier on top of the normal base value, the way other mods add theirs. Nothing can erase it by resetting the base value, and RAS no longer erases other mods' base values either.

• In an unmodded game the numbers are exactly the same as before. For example, 500 points of Attack Power still give 101 attack damage, and 500 points of Protection still give the maximum 30 armor.
• Existing characters are converted on their next login. The old base value is reset to default and replaced by the modifier, so nothing is counted twice.
• This covers every cmd_to_exc command of the form attribute @s <attribute> base set [param(x)], including modded attributes. Other commands run unchanged.
• /attribute @s <attribute> base get now shows the normal default. Use /attribute @s <attribute> get to see the total.

Config edits no longer reset when you relaunch

When RAS could not read a config file, it treated the file as empty and rebuilt it from defaults on the next start, so your changes were lost. Two common causes: an editor that saves as ANSI (the default files contain § color codes), and an edit that leaves a trailing comma.

• Files saved as ANSI, or as UTF-8 with a BOM, are read correctly. A trailing comma before } or ] is accepted.
• A file RAS still cannot read is never overwritten. The log names the file and the line and column of the error, and that file's settings are ignored until you fix it.
• Attribute files attribute_1.json to attribute_8.json now follow strict_config_mode like every other file. A key you delete, for example on_level_event, is no longer put back.
• init_val_starting_level in attributes/settings.json is no longer reset to 1 when strict_config_mode is off.
• An empty totals list in stats_display.json is kept instead of refilled.
• /ras lock and /ras unlock update the file as it is on disk, so they no longer revert edits made while the game was running.
• Config files are saved through a temporary file, so a crash while saving cannot leave a half-written file. A blank file is filled with defaults like a missing one.

Good to know

• Toughness only makes armor work better against strong hits, as in vanilla. Without armor, from Protection points or worn armor, Toughness has no effect.
• Fall, fire, drowning, magic and other armor-piercing damage ignores Protection and Toughness, as in vanilla.

Compatibility

• The fixes run on the server. In single-player, updating the game is enough.
• The network protocol is unchanged, so 5.0.0 and 5.0.1 clients and servers can join each other.
• Configuration files and player data from 5.0.0 load unchanged. The public API is unchanged.