Subject: Event not executed

I always take screenshots before playing games because I don't trust this game. And I have this screenshot:


It's in Portuguese, but I think everyone understands that Fernando Maria Pena (who was a substitute) came on in the 60th minute in position 8, and then, in the 61st minute, he would move to position 9.

However, watching the game, Fernando Maria Pena did not change to the position 9. Therefore, the event that I created did not happen.

The game ended 2-1 with a goal conceded in the 70th minute. And that goal could see Portugal drop into Pot 3, which affects the entire qualifying campaign and potentially the World Cup.

Fernando Maria Pena, who had just come on as a substitute, would have been much more influential in attacking down the right wing.

Dani Fragateiro has better passing and creativity, and would have been better than Fernando Maria Pena in the center.

Your screenshot is waay too small to read it properly.

It's in Portuguese, but I think everyone understands that Fernando Maria Pena (who was a substitute) came on in the 60th minute in position 8, and then, in the 61st minute, he would move to position 9.

Correction. The player came in at minute 62! So the order from minute 61 could never be executed and therefor was cancelled

The event I created was to make the substitution at the 60th minute. Obviously, the substitution was delayed until the game stopped. When the game stopped at the 62nd minute... the event at the 60th minute happened, but the event at the 61st minute did not happen, and it should have happened as well.

https://i.postimg.cc/Ss9mS4Q5/event.png

This way, the screenshot should be larger if you open it via the link.

It shouldn’t. You made a mistake.
You should have made a bigger gap between orders

I created the events correctly. These events should have worked correctly... and if they didn't, then it's because the events are buggy.

I shouldn't have to force events to happen just because they are buggy and have never been implemented properly over the years. The logic of the events I created is correct, but there was one event that didn't execute!

No, you misinterprete the orders.
If the game was stopped, both orders go through, but the 2nd order could not go through because the player was not on the field, so it was cancelled.
Like The Ripper said, you should take at least 5 minutes between both orders to be certain for about 98% that the order would go through.
(edited)

Maybe what you said is the problem... but that shouldn't be a problem. The events should have worked correctly, and as a user, I shouldn't have to worry about the poor implementation of the events. It's something that needs to be fixed, which is why it's written here. This bug hurt me today. I can't guess all the bugs in Sokker. There are too many bugs! There is a substitution in the 60th minute (which happened in the 62nd minute), and a position change in the 61st minute (which should have happened in the 62nd minute, in the next clock cycle, as it is the next event).

I do this type of event, one at minute 60 and another at minute 61, all the time in other managers, and Sokker is the only one that has a bug.

the logic is pretty clear:

position change = minute set
substitution >= minute set

if it was positon change >= minute set you could think of some odd situations in the game.

If I'm not mistaken, there's also a bug if I do things with your logic. If I move a player to position 9... I think the substitution has to be for position 8 (the original one), even though the player has moved to position 9. It is therefore a mistake that I have also made, and that we users are forced to do things unnaturally in order to work around yet another bug.

Setting the order is not really intuitive and the descriptions are sometimes missleading, I agree.
But I wouldn't call it a bug, because there is a clear logic behind and it works how it was intented to do.

I would have described / implemented orders differently at some points, so that it is clearer for myself. But it might be confusing or still missleading to others.

Setting orders is rather complex and therefore difficult to be implemented in an easy, user-friendly way (without taking the tactical depth).

It is pretty much an expert option, nice for extending the tactical depth, but not obligatory to be used comprehensively.

- In my opinion, when a player moves to position 9, he should be considered to be in position 9. If replacing him requires using the old number, then the player's number hasn't been updated, and therefore it's a bug. There are other manager games where the numbers are updated when players change positions.

- Regarding what prompted me to start this thread... the event I created didn't happen. I'll assume that although the events were created for different minutes, in practice, they would have been executed at the same minute... and that's why there was a bug. But just because two events occur at the same minute for the same player, with a correct sequence of which is first and which is second... doesn't mean one shouldn't happen. If there are 2, both should occur, one after the other, within the same minute, according to the sequence in which they appear to be executed. Therefore, for me, this is also a bug.

I understand your point, but I don't follow your conclusions for the reasons explaned above.

i agree you about the fact those order mecanism had to be improved to be clearer.
But about tactic switchs, it's very clear that a player keep his number all the match except he is outing from the grass to the bench.
so we have to understand that, while too that some player switch happen only when play stopped (and not switch tactic)
i don't know if a player switch (both already on the grass) happen suddenly or after a stop.
But i know new player from the bench happen only when match stop.

Question:
i suppose some stop are not concerned, like GK six 6 eter shoot, or after a goal. isn't it?

Unfortunately, your case isn't a bug, just a chain of very sensitive commands.

Switching positions require both players on the field at exact moment when command is set, but for that to happen, game had to stop before swap command occur, but it isn't!

It happened to me many times though I am using 5 min gap between any potential chain commands ...

Possible solution: positions physical swap, regardless the player, was the sub made or anything related bit for that to happen, whole Orders system would have to be changed so - no way to happen! :)