The issue isn't with parties but with relogs. Since I refactored the Player objects to no longer hash by id because it was causing confusing and incorrect behavior in other parts of the code, using Players as keys directly made the violation service think you were a different player after you relogged. Tracking by player id explicitly should fix this.
The issue isn't with parties but with relogs. Since I refactored the
Playerobjects to no longer hash by id because it was causing confusing and incorrect behavior in other parts of the code, usingPlayers as keys directly made the violation service think you were a different player after you relogged. Tracking by player id explicitly should fix this.Closes #931