I feel this is a futile attempt in trying to explain the issue, but I feel I must try, even though you've already decided that there's a bug no matter what I say, and this will turn into an endless debate. Here goes:
@Radiobasket:
1. Obviously I need to start answering every bug report with "please, have patience". Seeing that you had already said that ("Ok, Radiobasket, we got it. Please wait, please be patient"), I smiled and thought this time I didn't have to. Also, I would have posted my analysis before if I thought I needed to. Only when we determined for certain that there was no training bug and you both dismissed my conclusion (!), I had to write such an elaborate analysis.
2. I couldn't have done it before because it wasn't checked before (these things take time). Try not to use sarcasm when reporting a bug, it definitely doesn't help.
3. So, my mistake was editing my post? I had to edit it because I, like you, jumped to a conclusion that there was definitely something wrong with the training without checking your minutes beforehand (as I trusted you wouldn't file a report if you weren't sure) or checking the code. Until I was sure that there is no bug in the training calculation code, I couldn't have had an unbacked statement out there. If you asked about this, I would have explained before.
4. A misunderstanding: I believe your players had +100 minutes displayed. That was the presentation error which was fixed. Also, another one was that the players didn't have "private" beside the minutes for the game in question. That too was fixed. Just to clarify, the code for displaying the minutes has absolutely nothing to do with the training calculation code, so a printscreen would have never been accepted as valid proof.
5. A) and b) already explained.
c)'Collapse in our game shape (oh, yes, "could be better", "could be better", "could be better", "could be better")' - have you even read what I wrote about what influences GS? Selectively taking things out of context isn't really making an arguement. Also, I said that two of the twelve players could have had better GS than they do, not four (as you presented it).
d)"No answers to our requests FOR DAYS" ? - let's look at our timetable:
30.4. : The report is filed and we reply to it the same day
1.5. : You're asking about the status of the issue
2.5. : I reply asking for more patience (with your own words)
3.5. : You reply with "Me and Yuzzu are waiting...". I don't think I have to reply to that.
4.5. : The sarcasm starts ("I'm proud of you all."). Where's the patience I asked for there? This was rude, you must admit. Therefore, no reply.
5.5. : I ignore the sarcasm and post the conclusion that there was no training bug ("We checked the code thoroughy and the conclusion is that it was only a display error, so no minutes were ever included in training").
6.5. : You dismiss my conclusion with "Your answer is quite unlikely, the way you managed the issue too." SpicyMcHaggis adds "So how is the collapse in game shape justified?", which still implies there was a bug. Yuzzu was more direct with "unbelievable! this is a Bug! OBVIOUS.. display error? tzè..". Again, you all have already decided that there must be a bug, regardless of what I said. And then, as a reply to that, I posted my analysis, which you have accepted (I may be wrong) and SpicyMcHaggis still does not (to be replied to in the next post).
I did not reply on the 3.5. and the 4.5., but I had good reasons not to (read above), and all that after I had asked for patience on the 2.5.. Therefore your statement that there were no answers for days simply doesn't stand.
6. I undestand that you wanted a quick answer, but there was none to be given. Checking the code had to be done properly and I'm afraid we can't do it in a rush, nor can we say when exactly it will be done. My plead for patience was not heard in this case, so if you state that we are slow, I'd accept that and state t