Thanks.

From the evidence I have collected I can conclude the double corner glitch is FIXED. Not partially, or toned down, it's actually gone.

As for explaining the game, I am not saying it's flawless only that events can be explained.

For example I created a program years ago which almost certainly uses the same structure as Top Eleven.
Instead of playing soccer, it had players run an obstacle course. I used variables at different points to control the action. This is how games of this type work. You use control variables to send you to different parts of the program, or reset it back to zero.

Example in my program, as long as my control variable was equal to 1, the program continued to run, and would continue the course. If a player fell or ran out of time, pass would be set to 0 and it would kick it out and reset the program to the selection screen.
During the run, different events could happen, such as commentary.
It was all % based, and I had a success cap of 99.75%. In other words. .25% of the time even the strongest player would fail the easiest part of the course, or 1 out of 400 attempts. A success cap is mandatory for these kinds of programs in order to avoid predictability and to make it more interesting. This is why your 8 star striker with 1 on 1 ability misses his counter when 1 on 1 vs the 1 star goalie sometimes.

For Top Eleven, it calculates who does something, possibly based on possession, with a cap at 80%, and starts the Event Tree cycle which I mentioned in the OP.
While I couldn't tell you specifically what numbers go into which equations without seeing the code, this is almost certainly the way it worked. My program also had things like weather and form programmed in, it's really easy to do. In fact form took me like 6 lines of code to write and I could even do it for each specific rating on each player. Maybe his arm was a little sore so his strength was down, but he could still run just as fast.

So yeah... T11 isn't that complex in the grand scheme of things.