Add resolution methods to common Adventure Bot stuck areas and ::botinfo command
What have you done in this MR?
- Made each Adventure bot stuck-area implement its own resolution method
- Added moderator+ command that lets you see what a bot is up to
Are there any tricky things testers should keep an eye out for?
-
No -
Yes, as follows: Adventure bots should not be stuck at Falador wall, Draynor bank, or East of Catherby Fishing. Note the bots stuck at GE tunnel are Green Dragon bots and unrelated to this change (those spam click the tunnel and get stuck in a permanent Movement Pulse that someone who understands the core better will have to look at) -
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, I did not edit any JSON files by hand (MR will be rejected if there are manual JSON edits). -
I acknowledge that this contribution will be released under the AGPL license.