Skip to content

Stop newly-spawned pitfall NPCs from communicating with the afterlife about last jumped trap

Player Name requested to merge PlayerName/2009scape:graahk into master

What have you done in this MR?

  • Clear the 'last pitfall jumped' attribute when a pitfall trap NPC dies, so that the next spawn will not have one pitfall blocked that they, in fact, did NOT recently jump across.

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