@Gptaqbc commented on GitHub (Oct 28, 2019):
No more info about this or anything reported. I think we can close it.
@ben-maher commented on GitHub (Oct 6, 2019):
Looking good so far, no issues since second fix yet.
@Gptaqbc commented on GitHub (Nov 9, 2019):
@dginovker You can close this.
@dginovker commented on GitHub (Oct 6, 2019):
Thanks for the double fix. Closing :)
@Gptaqbc commented on GitHub (Nov 6, 2019):
We need to have a list in here that we can add all the objects that aren't working properly so the information is not…
@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
@ben-maher commented on GitHub (Oct 6, 2019):
I think this was caused by an anomoly when I attempted a trade, haven't been able to replicate since.
@dginovker commented on GitHub (Oct 6, 2019):
Closed with https://github.com/dginovker/2006rebotted/pull/16
@Gptaqbc commented on GitHub (Oct 24, 2019):
@benmaher95 What happened exactly?
@ben-maher commented on GitHub (Oct 6, 2019):
Re-open please <3
@RedSparr0w commented on GitHub (Oct 24, 2019):
Sorry, it's actually on these 4:
new Tile(2947, 3904, 0), //object id 1597
new Tile(2948, 3904,…