Skip to content

Save the allow_aggro command so it persists.

Pine Stone requested to merge natis1/2009scape:master into master

What have you done in this MR?

  • Save the allow_aggro command so it persists. This makes it extremely slightly more convenient in single player so you don't have to type it every time while still letting you play an admin. For the like, two people in this thread that care about that.

Note that it defaults to FALSE so the default behavior is the same as current. its just if you turn it on as an admin it persists.

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. ***

Merge request reports