25 coaches online • Server time: 10:47
* * * Did you know? Up until now, 1512555 players have died on the pitch.
Log in
Recent Forum Topics goto Post Problema with the in...goto Post Did throw got even h...goto Post No seasons! - Tourn...
Candlejack
Last seen 50 minutes ago
Candlejack (5844)
Overall
Mega-Star
Overall
Record
477/177/185
Win Percentage
67%
Archive

2025

2024

2024-10-17 09:49:03
rating 6
2024-08-30 11:54:13
rating 5.7
2024-01-26 18:34:34
rating 6

2023

2023-11-28 07:59:39
rating 6
2023-09-29 23:03:37
rating 6
2023-05-03 19:01:26
rating 6
2023-04-30 19:34:13
rating 6
2023-02-13 00:01:56
rating 6
2023-02-05 13:08:00
rating 6

2022

2022-11-14 23:32:41
rating 6
2022-08-12 22:07:38
rating 5.9
2022-04-16 11:53:28
rating 6
2022-04-15 20:16:31
rating 6
2022-03-08 07:16:28
rating 6

2021

2021-07-29 00:55:10
rating 6
2021-07-27 23:11:35
rating 6

2020

2020-11-08 15:15:59
rating 4.8
2020-07-01 22:02:23
rating 5

2019

2019-05-01 21:44:03
rating 6

2017

2017-10-03 19:41:33
rating 6
2017-04-16 22:08:12
rating 6

2016

2016-06-09 00:16:52
rating 5.8
2022-04-16 11:53:28
8 votes, rating 6
More 2016 issues
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.
Rate this entry
Comments
Posted by koadah on 2022-04-16 13:15:28
In my day we would have got treble time plus a day off in lieu for working on Good Friday. I'd have to check the handbook to see if there was any extra for it being the evening. Saturday would be a measly double time though. :(

It's worth leaving a monthly timebomb in there to remind people to donate. ;)
Posted by Nelphine on 2022-04-16 15:07:18
Candlejack, you are a scholar and a gentleman.
Or a loony git if you prefer.