@Dave Compton: In regards to UWP/ ExtendedExecutionSession it really is as easy as setting that bit at least from a code standpoint (perhaps Minecraft has additional code built in that would make it not trivial, but at it's core you put the line of code in that makes the request and then Windows either grants it or it doesn't based on resources, but it mostly does). The only issue (which would not be an issue for Mojang) is I believe they have to request permission to set the bit from Microsoft as part of the app certification process. The Windows Store is mostly a wasteland and Minecraft is one of the golden gooses it has, it would most certainly be approved without question I would think.
I had written a UWP app that I ended up abandoning because of various UWP restrictions, one of the annoyances for me was I had a TCP/IP connection open that Windows would terminate when the app suspended (which was a deal breaker for my app). Basically the app suspending is meant to be a CPU/Memory/Battery saver, all UWP apps can be suspended by Windows and the app maker has to put an event in place that basically saves all of the state so it can restore where you're at when the app becomes unsuspended. Traditional Windows app don't have this issue.
The problem is, although it's meant to save battery and resources the annoyance to users outweighs the benefit in many cases and this is one of them. Many of us are playing Minecraft on a desktop or a laptop with power and not from a low end mobile device. If anything we should have the choice on whether to allow it.
@Dave Compton: In regards to UWP/ ExtendedExecutionSession it really is as easy as setting that bit at least from a code standpoint (perhaps Minecraft has additional code built in that would make it not trivial, but at it's core you put the line of code in that makes the request and then Windows either grants it or it doesn't based on resources, but it mostly does). The only issue (which would not be an issue for Mojang) is I believe they have to request permission to set the bit from Microsoft as part of the app certification process. The Windows Store is mostly a wasteland and Minecraft is one of the golden gooses it has, it would most certainly be approved without question I would think.
I had written a UWP app that I ended up abandoning because of various UWP restrictions, one of the annoyances for me was I had a TCP/IP connection open that Windows would terminate when the app suspended (which was a deal breaker for my app). Basically the app suspending is meant to be a CPU/Memory/Battery saver, all UWP apps can be suspended by Windows and the app maker has to put an event in place that basically saves all of the state so it can restore where you're at when the app becomes unsuspended. Traditional Windows app don't have this issue.
The problem is, although it's meant to save battery and resources the annoyance to users outweighs the benefit in many cases and this is one of them. Many of us are playing Minecraft on a desktop or a laptop with power and not from a low end mobile device. If anything we should have the choice on whether to allow it.