Top Eleven Changes?

[BridgeGoth]

Ok guys I am going to request some help from you all on this one.

I noticed today that the free kicks on the stats show up as inverse of the number of fouls. While a useless stat, it shows they did something to the game.

THEN I noticed that on all 3 double corners today I got unusual commentary, and none scored.

So I request to the forum, if you see a double corner, please post here what the commentary was. I am going to analyze it and will be able to tell if they fixed the double corner glitch. I am very confident that I know why it was causing such a high % of goals, and will be able to tell from the comments if they fixed it.
So everyone, please help me out here, and I'll post my findings when I get enough data.

Thanks!


I'll explain the double corner glitch to you all, my theory to it anyway.

This is how i would program something like Top Eleven, in fact I've written programs that do very similar things to T11, so I have reason to believe this is accurate.

I'll try to make it understandable to non programmers.

Top Eleven uses an event tree, example:

Level zero:
Your Striker gets the ball: Go to level 1

Level 1:
Event selected (He plays a short pass for example)
He does something -- If successful, go to level 2, If fails, return to level 0

Level 2:
Event Selected (MC gets the ball in a likely situation)
Event happens -- if successful, go to level 3, if fail, go to level 0

and so on.

So a message like "But the DC anticipates it and wins the ball" would trigger the return to level 0.
The event variable, which i'll just call EVENT, is changed each time.

EVENT = 0
ST decides to dribble -- Fails: EVENT = 0
EVENT = 0
MC plays a short pass -- Success: EVENT + 1
Event = 1
ST gets the ball in a likely situation -- Success: EVENT + 1
Event = 2
He's now 1 on 1 with the goal keeper! -- Fail: EVENT = 0
But the goalie tips it over the bar! Great save by GK!

This is how a basic even tree works. Now let's look at corners and why Double Corner glitch exists.

To score a corner : (I will use CEVENT as the trigger)
CEVENT + 1 (Now 1: This triggers a corner)
MC kicks a weak center pass -- Success: CEVENT + 1 (now 2)
It's a chance! but DC's aerial defense dominates. -- Fail: CEVENT = 0

CEVENT + 1 (Now 1: Corner triggered)
MC kicks a weak center pass -- Success: CEVENT + 1 (Now 2)
ST with the header! -- Success: CEVENT + 1 (Now 3)
But it goes over! -- Fail: CEVENT = 0 OR GOAL: CEVENT = 0
The tree is complete and we restart at 0

Notice when CEVENT = 2, the ball reaches the striker's head, then level 3 decides the final result

Now here is my theory to what a double corner is actually doing. I suspect this because I have made this same error in event tree programming.

CEVENT + 1 (Corner triggered CEVENT = 1)
MC kicks a weak center pass
DC reacted clumsily and gives up another corner (restart the cycle)
CEVENT + 1 (Corner trigger CEVENT = 2) UHOH!! CEVENT wasn't reset!
Onto the head of ST! (CEVENT + 1, now 3 skipping the previous level)
GOAL!!!!

So what happened here exactly?
When a corner is triggered, CEVENT needs to be 1 + something, my theory is this does not reset on the 2nd corner, so instead of 1 + something, it's 1 + something + something, which shoots it down the event tree.

So instead of selecting a level 1 event (a result of the pass) it selects a level 2 event (a result of the header).

Got it? No? Good!



So what is the solution? Add a line of code to reset CEVENT back to 0 (or 1, whatever the trigger number is) after the 2nd corner initiates. Now it will look like this:

CEVENT = 1
MC kicks a weak center pass CEVENT + 1
DR takes no risk and kicks it into the corner !!!CEVENT = 1!!! (This is the new code)
MC kicks a weak center pass: CEVENT + 1 (Now 1 + 1 instead of 2 + 1)

Yes, to those of you who have posted multiple rants about double corners, the fix really could have been this simple....

[Gert Funck]

I had two double corners against me. My keeper saved both.

[talisman]

I had a double corner against me today - my keeper made a super save from the first and the opposition striker knocked his header over the bar for the second.

[BridgeGoth]

If you can please provide the actual commentary, not just the result.

It was from analyzing the commentary that i figured out the glitch, so I will need to do the same in order to see if it's really gone.

It does certainly look like they fixed it.

[Gert Funck]

If you can please provide the actual commentary, not just the result.

It was from analyzing the commentary that i figured out the glitch, so I will need to do the same in order to see if it's really gone.

It does certainly look like they fixed it.

It has been fixed for a while now

[BridgeGoth]

It has been fixed for a while now

I can absolutely assure you it had not. My ops still scored on about 90% of them, and the commentary was still consistent with the glitch, assuming my theory was correct.

[Gert Funck]

I can absolutely assure you it had not. My ops still scored on about 90% of them, and the commentary was still consistent with the glitch, assuming my theory was correct.

mine has this season been nearer 70% or so, so on my server it is fixed

[BridgeGoth]

mine has this season been nearer 70% or so, so on my server it is fixed

They are slightly less, but that is most likely the result of other factors, such as improved goal keeping, or adjusting the success ratio of certain events.

I explained in the OP what is likely going on with them just now.

[talisman]

I'm with Gert on that - my double-corner success is nearer 50% this season, according to the commented ones. There are more different commentary phrases being used, too.

I'm not sure that anything in this game can be analysed to the nth degree - the matches are played and a result comes out the other end - there's not much more we can do, except not rely on certain situations having a specific result.

[talisman]

If you can please provide the actual commentary, not just the result.

Pretty difficult to do seeing as the matches were played before we saw your thread...