It's also masochistic, it doesn't fight back once you escape it's aggression zone once.
Originally created by @MitchvanWijngaarden on GitHub (Oct 5, 2019).
Original GitHub issue: https://github.com/2006-Scape/2006Scape/issues/7
It's also masochistic, it doesn't fight back once you escape it's aggression zone once.
This can be solved by changing the NPC spawned at Draynor by ID 179 and modifying this NPC to be un-aggressive.
<!-- gh-comment-id:552144358 -->
@Gptaqbc commented on GitHub (Nov 9, 2019):
This can be solved by changing the NPC spawned at Draynor by ID 179 and modifying this NPC to be un-aggressive.
But someone have to confirm if this is a real issue or if it was like that in 2006.
<!-- gh-comment-id:552144394 -->
@Gptaqbc commented on GitHub (Nov 9, 2019):
But someone have to confirm if this is a real issue or if it was like that in 2006.
Aight it's confirmed it wasn't aggro. To fix, remove 178 from the array of int named: AGGRESSIVE_MONSTERS
<!-- gh-comment-id:554415407 -->
@Gptaqbc commented on GitHub (Nov 15, 2019):
Aight it's confirmed it wasn't aggro. To fix, remove 178 from the array of int named: AGGRESSIVE_MONSTERS
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @MitchvanWijngaarden on GitHub (Oct 5, 2019).
Original GitHub issue: https://github.com/2006-Scape/2006Scape/issues/7
It's also masochistic, it doesn't fight back once you escape it's aggression zone once.
@dginovker commented on GitHub (Oct 5, 2019):
Have you considered writing a bot to camp the black knight instead?
@MitchvanWijngaarden commented on GitHub (Oct 5, 2019):
no
@dginovker commented on GitHub (Oct 5, 2019):
Closing issue until further comment.
@mrextremez commented on GitHub (Oct 24, 2019):
I’m pretty sure his aggressiveness is based on your combat level
@Gptaqbc commented on GitHub (Nov 9, 2019):
This can be solved by changing the NPC spawned at Draynor by ID 179 and modifying this NPC to be un-aggressive.
@Gptaqbc commented on GitHub (Nov 9, 2019):
But someone have to confirm if this is a real issue or if it was like that in 2006.
@Gptaqbc commented on GitHub (Nov 15, 2019):
Aight it's confirmed it wasn't aggro. To fix, remove 178 from the array of int named: AGGRESSIVE_MONSTERS
@Gptaqbc commented on GitHub (Nov 17, 2019):
Fixed