many apologies!! that was a bug that occurred from me testing new additions in bugbears route, and due to negligence overlooked removing it when i updated D: !!!!!!! now fixed
