Resave *all* JSON files using Zaros to prevent future pain (!1771) · Merge requests · 2009Scape / Server · GitLab

The 17.0 major release is coming on May 16, 2024! This version brings many exciting improvements to GitLab, but also removes some deprecated features. We are introducing three breaking change windows during which we expect breaking changes to be deployed to GitLab.com. You can read more about it on our blogpost . The second breaking change window begins 2024-04-29 09:00 UTC and ends 2024-05-01 22:00 UTC.

Player Name requested to merge PlayerName/2009scape:gg_everyone into master Mar 18, 2024

What has been done in this MR?

Resave all JSON files using Zaros
Will merge conflict with at least !1723 !1713 (closed) (I think) !1735 which should be addressed by authors of those MRs. Sorry everyone, this is pain now to prevent more pain later 😞

What should testers check?

There should be no Corporeal Beast in front of Lumbridge castle
There should be no Armadyl godsword in front of Lumbridge castle
(Why those things? Because those are the changes I made, and subsequently removed, to trick Zaros into resaving those files)

I have tested these changes thoroughly.
I used the relevant Thanos/Zaros tool for any JSON edits where possible, and have attached screenshots of any changes. YES OH GOD YES