The update yesterday reminded me to look at this issue again.
An update that may prove useful: the game no longer appears to freeze the system but instead crashes. (No reason for this to have changed? Launcher is the same version, game is 1.11.2 as when created.)
It appears to be something realms related however. It appears to have a work around as well.
I usually set my options in game, not from the main menu. However today I saw that this had lead me to missing the setting to disable realm notification.
Turning this off appears to allow the game to load a world with out crashing when there is no network access.
(Note: disabling of network access is done via firewall; I believe the firewall in question prevents the opening of sockets if it receives a "no" to access... it is not simply removing the network cable.)
A further note is that the game works correctly with the setting on if it connects to a minecraft server running on the same computer even if all non-lan IPs are blocked.
As if v1.12.1 with a full clean install meant to play offline this work around no longer works.
Game now crashes regardless of whether or not realm notification is on.
Note - while turning off realm notification worked before it no longer does.
However it is somehow still related to server communication; when only requests to port 53 are blocked (and it doesn't request any other ports) the game does appear to opperate offline.
This does not appear to be the same issue at all; the behaviour describe is being observed by intentionally firewalling the game as it was sold as being able to opperate completely offline. The only time the game is allowed online is to update.
Further every ticket I update I get told to try a different ticket. I would suggest the ticket system currently being used is not effective.
Steven
MCL-5473
crash-2017-09-04_00.31.57-client.txt![[Mod] violine1101](../../../data/avatars/users/92858.png){kind=small}
The update yesterday reminded me to look at this issue again.
An update that may prove useful: the game no longer appears to freeze the system but instead crashes. (No reason for this to have changed? Launcher is the same version, game is 1.11.2 as when created.)
It appears to be something realms related however. It appears to have a work around as well.
I usually set my options in game, not from the main menu. However today I saw that this had lead me to missing the setting to disable realm notification.
Turning this off appears to allow the game to load a world with out crashing when there is no network access.
(Note: disabling of network access is done via firewall; I believe the firewall in question prevents the opening of sockets if it receives a "no" to access... it is not simply removing the network cable.)
A further note is that the game works correctly with the setting on if it connects to a minecraft server running on the same computer even if all non-lan IPs are blocked.
As if v1.12.1 with a full clean install meant to play offline this work around no longer works.
Game now crashes regardless of whether or not realm notification is on.
Unresolved.
Crash report attache however.
Please be aware that anyone working on this issue should be taking the steps themselves are they are repeatable & reliable.
Crash log attached.
Note - while turning off realm notification worked before it no longer does.
However it is somehow still related to server communication; when only requests to port 53 are blocked (and it doesn't request any other ports) the game does appear to opperate offline.
This does not appear to be the same issue at all; the behaviour describe is being observed by intentionally firewalling the game as it was sold as being able to opperate completely offline. The only time the game is allowed online is to update.
Further every ticket I update I get told to try a different ticket. I would suggest the ticket system currently being used is not effective.