Startup Task retry after Startup Error

[Constrat]

Before raising the issue...

• [X] I filled in a short, clear title so that developers could quickly identify the general problem when going through the issue list. Instead of "Some suggestions", "Stuck", etc.
• [X] I'm probably sure this is a new feature/suggestion and not a bug encountered (please attach logs if you're not sure)

The problems you have encountered?

Big log as it's from the start all the way to the end: line 1578 for StartupError log.log

Unfortunately both haven't fully resolved the startup issue, as these two only aimed at fixing the loading of the game.

• #9083
• #8966

If a freeze happens we have absolutely no way to detect it, especially in the startup phase, as it can take quite some time and most screens are black, but obviously after 1 minute and a half MAA detects something's wrong as we reach the 50 retry time. Passing it instatly leads to a startup error.

How is this error handled? Quite simply, it makes it as if the task ended correctly, so technically if the startup leads to either an error or a success, the result is the same, as the next task will be the infrastructure either way.

Iirc this issue has already been discussed almost a year ago and it lead to no solution as out of scope, because the request was to detect a freeze anytime / in any instance screen, which is definitely out of scope, but in case of a Startup Error it's usually (always) the first task in an automated MAA environment.

Any good ideas?

In case of a startup error (after 50 retries) just kill the game and repeat the StartGameTaskPlugin again (this way my starting activity tasks does it's tests) and hopefully this time it won't get stuck in the loading (or in a black screen as it seems to be the case in my log)

Additional

No response