mojira.dev

Kevin Hamilton

Assigned

No issues.

Reported

No issues.

Comments

I'm in the same boat. I play split screen on the same xbox as my wife. I never seem to have any issues myself as the first player.

Case1) Wife logs in and realises she has lost some progress. Her xp level was 30 but now is back at 28. A diamond enchanted hat has returned to being a half damaged iron one. Buildings however remain from moments before she last save and quit.

Case2) Wife logs in two days later to find her diamond enchanted hat has returned. Her xp level is at 30 again. Missing several items from her inventory however.

Case3) Wife again logs in a day later, diamond hat missing yet again. Level back at 28 again but showing her inventory exactly as it was at start of previous session.

We simply cannot trust minecraft in this unstable state and havent bothered playing it since. Not to mention that as soon as split screen becomes active the FPS becomes unplayable, barely 10-20 frames per second. (since the latest 'patch')

LAN play worked fine in 0.11.1. Issue appeared in 0.12.1.

I have a big house, so I have a large wifi network. The network is constructed using a few Apple routers. The root router is an AirPort Extreme. The others are AirPort Expresses. The AirPort expresses are physically wired to a switch connected to a wired port on the root router. All routers have updated firmware. Here's the basic network config:

Master APExtreme (DHCP/NAT)

switch

switch

switch

Sub1 (Bridge mode)

Sub2 (Bridge mode)

Sub3 (Bridge mode)

The routers use the same network name/password, but are assigned non-interfering RF channels. We never had the issue with 0.11.1. It only appeared after the 0.12.1 update. Nothing in the network has changed since 0.11.1.

Three of us play PE together. Although we're in the same room, the room is equadistant between two routers, so one person's device will be connected to the Master, while the others will be connected through a Sub (or vice versa). In this case, the workaround alone is insufficient to remedy the issue. But if I restart the sub (causing all iOS devices to connect to the same/root router), then executing the workaround procedure works most of the time.

Thanks, Aleksandra, for your efforts to fix this.