Update:

The issue is identified and a fix is implemented. Local tests look fine and Christer is running the deployment at the time I write this.

So hopefully 2016 should be fine again after this.

For those interested: The bug was similar to the one before just happened at a different place, when you deselected a player again without actually performing an action. I should have spotted this yesterday when doing the first fix but it was on oversight due to sloppyness on my behalf.

I appreciate people not being too upset about these issues but I am still very sorry for wasting people's time.


======================================================================
As seen on Discord there is at least one more issue with 2016 games. 2 matches ran into an error (that are those we are aware of currently).

I don't know how many games have been played since the update, but considering that the error(s) happened sometime during the game implies that you do not necessarily have to encounter it/them. So it might be possible to play an entire match without issues but there is no guarantee.

I will try to investigate this further and hopefully find and fix the cause soon.

As an explanation why this is happening and was not caught earlier: Testing for 2016 rules is very limited with the current site setup. Basically it is only the amount of testing that I can do locally which is not too much due to the focus on implementing new stuff. Usually I try to make sure changes for 2020 do not affect 2016 but as is evident with this release I sometimes miss things.

I am aware that this is very unpleasant for you as it might result in quite some wasted free time and I sincerely want to apologize for this inconvenience. Please be assured that this is not a result of ignorance or neglectance for the 2016 rules. We fully intend to support them as long as there is demand and do not consider you as a second class party.

As for the current issue, I will try to post updates here.