Michael Sant

Thanks for sharing this one, our QA team will investigate further.

We aren't able to provide a time frame yet I'm sorry. We do still have this issue being worked on.

Just to help understand the situation better, are these youth players generated as part of your youth intakes, or young players already in the game? This is just to better understand if its a data issue with existing players, or something happening with new youngsters.

Thanks for coming back with those, the QA team will investigate further.

We do have those issues in the latest post you made under review. Thank you for adding more information.

If you'd like to upload the game save to our cloud storage, you can do that and add the save game name to your ticket. Here is the guide:

Does the person have their save game file available so that we can take a look into this further? You can give them the usual guide for uploading saves: https://community.sigames.com/bugtracker/instructions-and-notes/how-to-upload-files-to-us-r98/ Seems like we'd need to check a few things about why this is happening and see if its something data related or an issue elsewhere.

At a certain point we transition from using the Crashes forum to direct one-to-one support through tickets. If you create a ticket here: https://fmofficial.support/Ticket Then our staff can work through troubleshooting steps based on your game.

There are a lot of issues you've listed here across the thread. They also fall within different areas of the QA team. Issue 1, 3, 4, 5, 6, 7, 8, 12 and 13 would need their own threads with examples of the issue so that the QA team can investigate. Issue 2, 9 and 11 match issues we already have under review so would not need to be logged again. I know you've linked from FM Korea and it looks like the community there has put a lot of work in to logging information, it may be worthwhile asking the posters in there to share their issues with us directly so we can see it in their save games for some of these issues. We'd really like to look into these fully and make sure we get everything logged correctly.

For a crash it would typically be best to create a support ticket. You can do this through the following link: https://support.sega.com/hc/en-gb/requests/new?ticket_form_id=360003117678 You may be able to holiday past the day in some instances which can help you reach a point where you can continue the save.

I can see Haaland is duplicated here. We would need your save game from before this happens to best investigate. If you have such a save available, a guide on how to share it is available here: https://community.sigames.com/bugtracker/instructions-and-notes/how-to-upload-files-to-us-r98/ 이런 일이 발생하기 전에 세이브 게임이 있습니까?

Thank you for sharing this one, we'll need to check where exactly the conflict is in the background, but our QA team can review this and we can take things further from there.

Thanks for sharing this one. The QA team will take a look into this further.

There haven't been any changes to the ME in terms of the way teams are playing. There can be spells of bad form and bad luck. There are a lot of potential reasons as to why this situation may change with your team.

We would need to see some breakdown of stats from your game. Do you happen to have anything to hand from your save just how many exactly have come within the first 10 minutes?

Best to let the QA team to investigate this, I'm also a little unsure off hand myself under the current rules but feel it would count as an offside as a keeper save isn't as deliberate as a pass.

Thank you for providing the pkm. The QA team will investigate this further.

Very Attacking is a high risk approach towards playing and so the goalkeeper going forward does make sense.

Thank you for providing the pkm. The QA team will need to investigate this further and review exactly why it is happening in this way.

Thanks for sharing, it appears the combination columns (so attempted/completed) are the ones which still show as white. This may be by design, but its best to let the QA team double check this so that we can be sure.

Thank you for sharing the pkm. There are some issues which can persist but the QA team will investigate this further and what may be done moving forward.

Thank you for sharing this one, the QA team will investigate further.

The QA team will take a look into this and what the functionality should be in situations such as these. Thank you for providing the files to review.

Thanks for sharing your save and pointing out the issue with translation. Our QA team will take a look into both issues further.

Thanks for sharing this one. The QA team will take a look into this further.