REALMS-2936Snapshot creates FailState Rolback loop; Unplayable
i am sure we know it’s a dupe
but you guys keep privatizing these reports
hi day 1 realm veteran; alpha player converted to player for life
(super autism and 10 years in tech later i’ve been toying with this for a time)
[ why can’t we just all rollback when you push failed code public ?
Even my employer Apple let’s official downgrades happen especially when they drop the ball on a public build...]
Symptom- Upon load as soon as player has written X data value packets to DB it kicks into a fail state and stops replying/pinging back; and seems to enter a rollback.
To a everyday player this looks like you lost your spot; to the autistic this looks like some terrible NBT and chunk rewriting going on. There are more details so please read on.
So I do think it is the size of the world or age, our realm is super old and super big.
Whatever it could be, I was able to get this same issue on a new map once I made it bigger than 3.5GB.
doesn't that sound like a 32bit issue, and arent we in C+++ x64 codebase?
Cause it seems to me like with bees every time you add new blocks to the registry and back-end of the engine it all fails miserably for months while you play bug catch-up.
Outside of making this a soapbox (and I don’t want that i’m trying to give effective actionable feedback is all) let me suggest some fixes.
let OP realms dictate when to rollout; i get you are but give them the option to roll back. In the last year we the public and semi private realms have watched you bend over backwards to give and allow the featured servers roll back to versions two builds before the official client.(So it’s obvious if you did it for Mineplex you can do it for realms too.)
let OP; or even users send crash errors/reports to themselves since having a pile of them isn’t helping your workload; having a ability as users to filter out and give more effective feedback might help both sides in the battle for stable code.
Give OP of realm a optimize this realm button; clearly we didn’t outgrow the need to optimize the world like we need/have in the Java builds. Something is going on and hiding it is silly.
let me expand on how and why i’m arriving at this.
So up until you rolled out .30 unexpectedly the downside is you broke the whole economy trying to fix one console; not cool.
(as in in a PC user base nothing was really game breaking or needed fixing; btw thanks for trying to fix Nintendo)
I had just completed a 4000x16x16 nether highway in a 72 hour build off leading to new chunks on our gigantic world from the first days of realms.
This bad boy has been thru it all and trust me has had is terrible bug days in the past. ( Bees/Aquatic were the worse heartaches)
The thing is this time around was easy compared to 3 months ago it was building a highway to get to new bee chunks.
(In the past we lost our highway builds in progress to random super far back rollback, now at least its minimal rollback)
Everything was working perfectly, the .20 build was amazing; we had our 6 members on around the clock again building like crazy.
AGAIN to your credit .20 was amazing in our eyes; again any crash was only minutes or no data loss.
We started trusting you and the code base. No joke hundreds of hours have been stolen away in build time or rebuilding over the last year.
Players left realms for good over it, and we are seeing that again now.
The new .30 is so broken that, everyone is stuck on our realms even the OP and alt accounts we have.
At most you get minutes of game play, I found a method to bring it forward 5 min max and it’s really ghetto what I need to do to accomplish.
We use to stress it was too many dropped blocks not picked up; but once .30 came out it’s clear the mob and engine rules have changed!!!
Our fire spread and mob griefing switches got reverted back; and in the looping fail-state they can’t be toggled back off.
So that meant for me a ghast spawned onto the leaves i was laying on the highway; so my highway is on fire and even if I try and run away the crashing loop happens. (gonna get a clip of this its epic)
now that your sucked into my story I hope you feel for and try and ease my pain.
ive tried easing yours by documenting and trying lots of solutions before pointing at the problem; here’s some clues
1) it’s in the engine
2) it’s not timer based ( every x ticks )
3) can be tricked (using old client let’s you bring it forward a save state)
4) is probably related to entity metadata and spawning algorithm
5) it’s inevitable you can’t avoid the crash and looping cycle
I feel like i’m living in groundhog day.. I have no joke tried getting out of this 19 times and counting,
*The biggest thing is waiting for it to crash, rollback and recover. I cant imagine this is nice to your DataCenter.
Its not block state or data related 110% mob related.
- I could TP somewhere and crash it all the fastest.
- Couldn’t dig out or build out into a new save state.
- I could put the fire out with illegal flowing water and make the lava lake obsidian and not crash the game (block state) but the second I saw mobs and they started animating it would crash.
oh also when building out a block at a time trying to get to new region files thinking it’s the files; i found that a certain number of sounds played like placing leaves; it would also eventually buffer overflow and crash the realm too.
the easiest check is when your chat stops or you can not open chests fly or interact with mobs or you know they stop animating
I toyed with it being chat too, so if I dug into the wall and hid out I could chat echo nonstop.
Also also the second another player gets on anywhere in the realm it dies, unsure of the other players mob vicinity but i think its just after X packets are read off or written too the whole thing crashes.
anyways no I don’t want to private this or get anything back;
i just wanted to sit down and pour out what I think is going on this time;
if we’re at our limit can we rip out all the education stuff we can’t even use on realms?
same with the pocket edition textures and code base.i know you know we don’t need underwater TNT
!
Environment
Realms , Win10 Pro, all Consoles
NOT specific to any map or seed or troubleshooting steps system wide failure.
Created Issue:
Snapshot creates FailState Rolback loop; Unplayable
i am sure we know it’s a dupe
but you guys keep privatizing these reports
hi day 1 realm veteran; alpha player converted to player for life
(super autism and 10 years in tech later i’ve been toying with this for a time)
[ why can’t we just all rollback when you push failed code public ?
Even my employer Apple let’s official downgrades happen especially when they drop the ball on a public build...]Symptom- Upon load as soon as player has written X data value packets to DB it kicks into a fail state and stops replying/pinging back; and seems to enter a rollback.
To a everyday player this looks like you lost your spot; to the autistic this looks like some terrible NBT and chunk rewriting going on. There are more details so please read on.
If I artificially create a new world on or off realms fly around legit or TP script; I have found the failure point hilariously is around a 32bit addressable memory limit. It’s hilarious cause didn’t you guys create a cool fool proof NTB standard written entirely in beautiful C++ !?!
Cause it seems to me like with bees every time you add new blocks to the registry and backend of the engine it all fails miserably for months.
Outside of making this a soapbox (and I don’t want that i’m trying to give effective actionable feedback is all) let me suggest some fixes.
1) let OP realms dictate when to rollout; i get you are but give them the option to roll back. In the last year we the public and semi private realms have watched you bend over backwards to give and allow the featured servers roll back to versions two builds before the official client.
So it’s obvious if you did it for Mineplex you can do it for realms too.
2) let OP; or hell even users send crash errors/reports to themselves since having a pile of them isn’t helping your workload; having a ability as users to filter out and give more effective feedback might help both sides in the battle for stable code.
And finally..
3) Give OP of realm a optimize this realm button; clearly we didn’t outgrow the need to optimize the world like we need/have in the Java builds. Something is going on and hiding it is silly.
let me expand on how and why i’m arriving at this.
also on mobile right now i’ll get screens maybe even video too if need be.
So up until you rolled out .30 unexpectedly (as in in a PC user base nothing was really game breaking or needed fixing; btw thanks for trying to fix Nintendo) the downside is you broke the whole economy trying to fix one console; not cool.
I had just completed a 4000 x16x16 nether highway in a 72 hour build off leading to new chunks on our gigantic world from the first days of realms. This bad boy has been thru it all and trust me has had is terrible bug days in the past.
The thing is this time around (3 months ago it was building a highway to get to new bee chunks) everything was working perfectly, the .20 build was amazing; we had our 6 members on around the clock again building like crazy.
AGAIN to your credit .20 was amazing in our eyes; any crash was only minutes or no data loss. We started trusting you and the code base. No joke thousands of hours have been stolen away in build time or rebuilding over the last year.
But this new .30 is so broken that, everyone is stuck on our realms even the OP and cam accounts we have.
At most you get minutes of game play, i found a method to bring it forward 5 min max and it’s really ghetto what I need to do to accomplish.
We use to stress it was too many dropped blocks not picked up; but once .30 came out it’s clear the mob and engine rules have changed!!!
Our fire spread and mob griefing switches got reverted back; and in the looping failstate they can’t be toggled back off.
So that meant for me a ghast spawned onto the leaves i was laying on the highway; so my highway is on fire and even if I try and run away the crashing loop happens.
now that your sucked into my story I hope you feel for and try and ease my pain.
ive tried easing yours by documenting and trying lots of solutions before pointing at the problem; here’s some clues
1) it’s in the engine
2) it’s not timer based ( every x ticks )
3) can be tricked (using old client let’s you bring it forward a save state)
4) is probably related to entity metadata and spawning algorithm
5) it’s inevitable you can’t avoid the crash and looping cycle
I feel like i’m living in groundhog day.
Its not block state or data related 110% mob related.
I could TP somewhere and crash it all the fastest.
Couldn’t dig out or build out into a new save state.
I could put the fire out with illegal flowing water and make the lava lake obsidian and not crash the game (block state) but the second I saw mobs and they started animating it would crash.
oh also when building out a block at a time trying to get to new region files thinking it’s the files; i found that a certain number of sounds played like placing leaves; it would also eventually buffer overflow and crash the realm too.
the easiest check is when your chat stops or you can open chests fly or interact with mobs or you know they stop animating
anwyays no I don’t want to private this or get anything back; i just wanted to sit down and pour out what I think is going on this time; if we’re at our limit can we rip out all the education stuff we can’t even use on realms same with the pocket edition textures and code base. i know you know we don’t need underwater TNT
Environment
Realms, Win10 Pro
i am sure we know it’s a dupe
but you guys keep privatizing these reports
hi day 1 realm veteran; alpha player converted to player for life
(super autism and 10 years in tech later i’ve been toying with this for a time)
[ why can’t we just all rollback when you push failed code public ?
Even my employer Apple let’s official downgrades happen especially when they drop the ball on a public build...]Symptom- Upon load as soon as player has written X data value packets to DB it kicks into a fail state and stops replying/pinging back; and seems to enter a rollback.
To a everyday player this looks like you lost your spot; to the autistic this looks like some terrible NBT and chunk rewriting going on. There are more details so please read on.
If I artificially create a new world on or off realms fly around legit or TP script; I have found the failure point hilariously is around a 32bit addressable memory limit. It’s hilarious cause didn’t you guys create a cool fool proof NTB standard written entirely in beautiful C++ !?!
Cause it seems to me like with bees every time you add new blocks to the registry and backend of the engine it all fails miserably for months.
Outside of making this a soapbox (and I don’t want that i’m trying to give effective actionable feedback is all) let me suggest some fixes.
1) let OP realms dictate when to rollout; i get you are but give them the option to roll back. In the last year we the public and semi private realms have watched you bend over backwards to give and allow the featured servers roll back to versions two builds before the official client.
So it’s obvious if you did it for Mineplex you can do it for realms too.
2) let OP; or hell even users send crash errors/reports to themselves since having a pile of them isn’t helping your workload; having a ability as users to filter out and give more effective feedback might help both sides in the battle for stable code.
And finally..
3) Give OP of realm a optimize this realm button; clearly we didn’t outgrow the need to optimize the world like we need/have in the Java builds. Something is going on and hiding it is silly.
let me expand on how and why i’m arriving at this.
also on mobile right now i’ll get screens maybe even video too if need be.
So up until you rolled out .30 unexpectedly (as in in a PC user base nothing was really game breaking or needed fixing; btw thanks for trying to fix Nintendo) the downside is you broke the whole economy trying to fix one console; not cool.
I had just completed a 4000 x16x16 nether highway in a 72 hour build off leading to new chunks on our gigantic world from the first days of realms. This bad boy has been thru it all and trust me has had is terrible bug days in the past.
The thing is this time around (3 months ago it was building a highway to get to new bee chunks) everything was working perfectly, the .20 build was amazing; we had our 6 members on around the clock again building like crazy.
AGAIN to your credit .20 was amazing in our eyes; any crash was only minutes or no data loss. We started trusting you and the code base. No joke thousands of hours have been stolen away in build time or rebuilding over the last year.
But this new .30 is so broken that, everyone is stuck on our realms even the OP and cam accounts we have.
At most you get minutes of game play, i found a method to bring it forward 5 min max and it’s reallyghettowhat I need to do to accomplish.We use to stress it was too many dropped blocks not picked up; but once .30 came out it’s clear the mob and engine rules have changed!!!
Our fire spread and mob griefing switches got reverted back; and in the looping failstate they can’t be toggled back off.
So that meant for me a ghast spawned onto the leaves i was laying on the highway; so my highway is on fire and even if I try and run away the crashing loop happens.
now that your sucked into my story I hope you feel for and try and ease my pain.
ive tried easing yours by documenting and trying lots of solutions before pointing at the problem; here’s some clues
1) it’s in the engine
2) it’s not timer based ( every x ticks )
3) can be tricked (using old client let’s you bring it forward a save state)
4) is probably related toentity metadata and spawning algorithm5) it’s inevitable you can’t avoid the crash and looping cycle
I feel like i’m living in groundhog day.
Its not block state or data related 110% mob related.
I could TP somewhere and crash it all the fastest.
Couldn’t dig out or build out into a new save state.
I could put the fire out with illegal flowing water and make the lava lake obsidian and not crash the game (block state) but the second I saw mobs and they started animating it would crash.
oh also when building out a block at a time trying to get to new region files thinking it’s the files; i found that a certain number of sounds played like placing leaves; it would also eventually buffer overflow and crash the realm too.
the easiest check is when your chat stops or you can open chests fly or interact with mobs or you know they stop animating
anwyays no I don’t want to private this or get anything back; i just wanted to sit down and pour out what I think is going on this time; if we’re at our limit can we rip out all the education stuff we can’t even use on realms same with the pocket edition textures and code base. i know you know we don’t need underwater TNT
i am sure we know it’s a dupe
but you guys keep privatizing these reports
hi day 1 realm veteran; alpha player converted to player for life
(super autism and 10 years in tech later i’ve been toying with this for a time)
[ why can’t we just all rollback when you push failed code public ?
Even my employer Apple let’s official downgrades happen especially when they drop the ball on a public build...]Symptom- Upon load as soon as player has written X data value packets to DB it kicks into a fail state and stops replying/pinging back; and seems to enter a rollback.
To a everyday player this looks like you lost your spot; to the autistic this looks like some terrible NBT and chunk rewriting going on. There are more details so please read on.
So I do think it is the size of the world or age, our realm is super old and super big.
Whatever it could be, I was able to get this same issue on a new map once I made it bigger than 3.5GB.doesnt that sound like a 32bit issue, and arent we in C+ x64 codebase?+
Cause it seems to me like with bees every time you add new blocks to the registry and back-end of the engine it all fails miserably for months while you play bug catch-up.
Outside of making this a soapbox (and I don’t want that i’m trying to give effective actionable feedback is all) let me suggest some fixes.
let OP realms dictate when to rollout; i get you are but give them the option to roll back. In the last year we the public and semi private realms have watched you bend over backwards to give and allow the featured servers roll back to versions two builds before the official client.(So it’s obvious if you did it for Mineplex you can do it for realms too.)
let OP; or even users send crash errors/reports to themselves since having a pile of them isn’t helping your workload; having a ability as users to filter out and give more effective feedback might help both sides in the battle for stable code.
Give OP of realm a optimize this realm button; clearly we didn’t outgrow the need to optimize the world like we need/have in the Java builds. Something is going on and hiding it is silly.
let me expand on how and why i’m arriving at this.
So up until you rolled out .30 unexpectedly the downside is you broke the whole economy trying to fix one console; not cool.
(as in in a PC user base nothing was really game breaking or needed fixing; btw thanks for trying to fix Nintendo)I had just completed a 4000x16x16 nether highway in a 72 hour build off leading to new chunks on our gigantic world from the first days of realms.
This bad boy has been thru it all and trust me has had is terrible bug days in the past. ( Bees/Aquatic were the worse heartaches)The thing is this time around as compared to 3 months ago it was building a highway to get to new bee chunks.
Everything was working perfectly, the .20 build was amazing; we had our 6 members on around the clock again building like crazy.
AGAIN to your credit .20 was amazing in our eyes; any crash was only minutes or no data loss.
We started trusting you and the code base. No joke hundreds of hours have been stolen away in build time or rebuilding over the last year.
Players left realms for good over it, and we are seeing that again now.
The new .30 is so broken that, everyone is stuck on our realms even the OP and cam accounts we have.
At most you get minutes of game play, I found a method to bring it forward 5 min max and it’s really ghetto what I need to do to accomplish.
We use to stress it was too many dropped blocks not picked up; but once .30 came out it’s clear the mob and engine rules have changed!!!
Our fire spread and mob griefing switches got reverted back; and in the looping fail-state they can’t be toggled back off.So that meant for me a ghast spawned onto the leaves i was laying on the highway; so my highway is on fire and even if I try and run away the crashing loop happens. (gonna get a clip of this its epic)
now that your sucked into my story I hope you feel for and try and ease my pain.
ive tried easing yours by documenting and trying lots of solutions before pointing at the problem; here’s some clues
1) it’s in the engine
2) it’s not timer based ( every x ticks )
3) can be tricked (using old client let’s you bring it forward a save state)
4) is probably related to entity metadata and spawning algorithm
5) it’s inevitable you can’t avoid the crash and looping cycle
I feel like i’m living in groundhog day.. I have no joke tried getting out of this 19 times and counting,
*The biggest thing is waiting for it to crash, rollback and recover. I cant imagine this is nice to your DataCente*r.Its not block state or data related 110% mob related.
- I could TP somewhere and crash it all the fastest.
- Couldn’t dig out or build out into a new save state.
- I could put the fire out with illegal flowing water and make the lava lake obsidian and not crash the game (block state) but the second I saw mobs and they started animating it would crash.
oh also when building out a block at a time trying to get to new region files thinking it’s the files; i found that a certain number of sounds played like placing leaves; it would also eventually buffer overflow and crash the realm too.
the easiest check is when your chat stops or you can not open chests fly or interact with mobs or you know they stop animating
I toyed with it being chat too, so if I dug into the wall and hid out I could chat echo nonstop.
Also also the second another player gets on anywhere in the realm it dies, unsure of the other players mob vicinity but i think its just after X packets are read off or written too the whole thing crashes.
anwyays no I don’t want to private this or get anything back;
i just wanted to sit down and pour out what I think is going on this time;
if we’re at our limit can we rip out all the education stuff we can’t even use on realms?
same with the pocket edition textures and code base.i know you know we don’t need underwater TNT
Realms, Win10 Pro
Realms , Win10 Pro, all Consoles
NOT specific to any map or seed or troubleshooting steps system wide failure.
i am sure we know it’s a dupe
but you guys keep privatizing these reports
hi day 1 realm veteran; alpha player converted to player for life
(super autism and 10 years in tech later i’ve been toying with this for a time)
[ why can’t we just all rollback when you push failed code public ?
Even my employer Apple let’s official downgrades happen especially when they drop the ball on a public build...]Symptom- Upon load as soon as player has written X data value packets to DB it kicks into a fail state and stops replying/pinging back; and seems to enter a rollback.
To a everyday player this looks like you lost your spot; to the autistic this looks like some terrible NBT and chunk rewriting going on. There are more details so please read on.
So I do think it is the size of the world or age, our realm is super old and super big.
Whatever it could be, I was able to get this same issue on a new map once I made it bigger than 3.5GB.
doesntthat sound like a 32bit issue, and arent we inC+x64 codebase?+
Cause it seems to me like with bees every time you add new blocks to the registry and back-end of the engine it all fails miserably for months while you play bug catch-up.
Outside of making this a soapbox (and I don’t want that i’m trying to give effective actionable feedback is all) let me suggest some fixes.
let OP realms dictate when to rollout; i get you are but give them the option to roll back. In the last year we the public and semi private realms have watched you bend over backwards to give and allow the featured servers roll back to versions two builds before the official client.(So it’s obvious if you did it for Mineplex you can do it for realms too.)
let OP; or even users send crash errors/reports to themselves since having a pile of them isn’t helping your workload; having a ability as users to filter out and give more effective feedback might help both sides in the battle for stable code.
Give OP of realm a optimize this realm button; clearly we didn’t outgrow the need to optimize the world like we need/have in the Java builds. Something is going on and hiding it is silly.
let me expand on how and why i’m arriving at this.
So up until you rolled out .30 unexpectedly the downside is you broke the whole economy trying to fix one console; not cool.
(as in in a PC user base nothing was really game breaking or needed fixing; btw thanks for trying to fix Nintendo)I had just completed a 4000x16x16 nether highway in a 72 hour build off leading to new chunks on our gigantic world from the first days of realms.
This bad boy has been thru it all and trust me has had is terrible bug days in the past. ( Bees/Aquatic were the worse heartaches)The thing is this time around as compared to 3 months ago it was building a highway to get to new bee chunks.
Everything was working perfectly, the .20 build was amazing; we had our 6 members on around the clock again building like crazy.
AGAIN to your credit .20 was amazing in our eyes; any crash was only minutes or no data loss.
We started trusting you and the code base. No joke hundreds of hours have been stolen away in build time or rebuilding over the last year.
Players left realms for good over it, and we are seeing that again now.
The new .30 is so broken that, everyone is stuck on our realms even the OP and cam accounts we have.
At most you get minutes of game play, I found a method to bring it forward 5 min max and it’s really ghetto what I need to do to accomplish.
We use to stress it was too many dropped blocks not picked up; but once .30 came out it’s clear the mob and engine rules have changed!!!
Our fire spread and mob griefing switches got reverted back; and in the looping fail-state they can’t be toggled back off.So that meant for me a ghast spawned onto the leaves i was laying on the highway; so my highway is on fire and even if I try and run away the crashing loop happens. (gonna get a clip of this its epic)
now that your sucked into my story I hope you feel for and try and ease my pain.
ive tried easing yours by documenting and trying lots of solutions before pointing at the problem; here’s some clues
1) it’s in the engine
2) it’s not timer based ( every x ticks )
3) can be tricked (using old client let’s you bring it forward a save state)
4) is probably related to entity metadata and spawning algorithm
5) it’s inevitable you can’t avoid the crash and looping cycle
I feel like i’m living in groundhog day.. I have no joke tried getting out of this 19 times and counting,
*The biggest thing is waiting for it to crash, rollback and recover. I cant imagine this is nice to your DataCente*r.Its not block state or data related 110% mob related.
- I could TP somewhere and crash it all the fastest.
- Couldn’t dig out or build out into a new save state.
- I could put the fire out with illegal flowing water and make the lava lake obsidian and not crash the game (block state) but the second I saw mobs and they started animating it would crash.
oh also when building out a block at a time trying to get to new region files thinking it’s the files; i found that a certain number of sounds played like placing leaves; it would also eventually buffer overflow and crash the realm too.
the easiest check is when your chat stops or you can not open chests fly or interact with mobs or you know they stop animating
I toyed with it being chat too, so if I dug into the wall and hid out I could chat echo nonstop.
Also also the second another player gets on anywhere in the realm it dies, unsure of the other players mob vicinity but i think its just after X packets are read off or written too the whole thing crashes.
anwyays no I don’t want to private this or get anything back;
i just wanted to sit down and pour out what I think is going on this time;
if we’re at our limit can we rip out all the education stuff we can’t even use on realms?
same with the pocket edition textures and code base.i know you know we don’t need underwater TNT
i am sure we know it’s a dupe
but you guys keep privatizing these reports
hi day 1 realm veteran; alpha player converted to player for life
(super autism and 10 years in tech later i’ve been toying with this for a time)
[ why can’t we just all rollback when you push failed code public ?
Even my employer Apple let’s official downgrades happen especially when they drop the ball on a public build...]Symptom- Upon load as soon as player has written X data value packets to DB it kicks into a fail state and stops replying/pinging back; and seems to enter a rollback.
To a everyday player this looks like you lost your spot; to the autistic this looks like some terrible NBT and chunk rewriting going on. There are more details so please read on.
So I do think it is the size of the world or age, our realm is super old and super big.
Whatever it could be, I was able to get this same issue on a new map once I made it bigger than 3.5GB.doesn't that sound like a 32bit issue, and arent we in C x64 codebase?+
Cause it seems to me like with bees every time you add new blocks to the registry and back-end of the engine it all fails miserably for months while you play bug catch-up.
Outside of making this a soapbox (and I don’t want that i’m trying to give effective actionable feedback is all) let me suggest some fixes.
let OP realms dictate when to rollout; i get you are but give them the option to roll back. In the last year we the public and semi private realms have watched you bend over backwards to give and allow the featured servers roll back to versions two builds before the official client.(So it’s obvious if you did it for Mineplex you can do it for realms too.)
let OP; or even users send crash errors/reports to themselves since having a pile of them isn’t helping your workload; having a ability as users to filter out and give more effective feedback might help both sides in the battle for stable code.
Give OP of realm a optimize this realm button; clearly we didn’t outgrow the need to optimize the world like we need/have in the Java builds. Something is going on and hiding it is silly.
let me expand on how and why i’m arriving at this.
So up until you rolled out .30 unexpectedly the downside is you broke the whole economy trying to fix one console; not cool.
(as in in a PC user base nothing was really game breaking or needed fixing; btw thanks for trying to fix Nintendo)I had just completed a 4000x16x16 nether highway in a 72 hour build off leading to new chunks on our gigantic world from the first days of realms.
This bad boy has been thru it all and trust me has had is terrible bug days in the past. ( Bees/Aquatic were the worse heartaches)The thing is this time around as compared to 3 months ago it was building a highway to get to new bee chunks.
Everything was working perfectly, the .20 build was amazing; we had our 6 members on around the clock again building like crazy.
AGAIN to your credit .20 was amazing in our eyes; any crash was only minutes or no data loss.
We started trusting you and the code base. No joke hundreds of hours have been stolen away in build time or rebuilding over the last year.
Players left realms for good over it, and we are seeing that again now.
The new .30 is so broken that, everyone is stuck on our realms even the OP and cam accounts we have.
At most you get minutes of game play, I found a method to bring it forward 5 min max and it’s really ghetto what I need to do to accomplish.
We use to stress it was too many dropped blocks not picked up; but once .30 came out it’s clear the mob and engine rules have changed!!!
Our fire spread and mob griefing switches got reverted back; and in the looping fail-state they can’t be toggled back off.So that meant for me a ghast spawned onto the leaves i was laying on the highway; so my highway is on fire and even if I try and run away the crashing loop happens. (gonna get a clip of this its epic)
now that your sucked into my story I hope you feel for and try and ease my pain.
ive tried easing yours by documenting and trying lots of solutions before pointing at the problem; here’s some clues
1) it’s in the engine
2) it’s not timer based ( every x ticks )
3) can be tricked (using old client let’s you bring it forward a save state)
4) is probably related to entity metadata and spawning algorithm
5) it’s inevitable you can’t avoid the crash and looping cycle
I feel like i’m living in groundhog day.. I have no joke tried getting out of this 19 times and counting,
*The biggest thing is waiting for it to crash, rollback and recover. I cant imagine this is nice to your DataCente*r.Its not block state or data related 110% mob related.
- I could TP somewhere and crash it all the fastest.
- Couldn’t dig out or build out into a new save state.
- I could put the fire out with illegal flowing water and make the lava lake obsidian and not crash the game (block state) but the second I saw mobs and they started animating it would crash.
oh also when building out a block at a time trying to get to new region files thinking it’s the files; i found that a certain number of sounds played like placing leaves; it would also eventually buffer overflow and crash the realm too.
the easiest check is when your chat stops or you can not open chests fly or interact with mobs or you know they stop animating
I toyed with it being chat too, so if I dug into the wall and hid out I could chat echo nonstop.
Also also the second another player gets on anywhere in the realm it dies, unsure of the other players mob vicinity but i think its just after X packets are read off or written too the whole thing crashes.
anwyays no I don’t want to private this or get anything back;
i just wanted to sit down and pour out what I think is going on this time;
if we’re at our limit can we rip out all the education stuff we can’t even use on realms?
same with the pocket edition textures and code base.i know you know we don’t need underwater TNT
i am sure we know it’s a dupe
but you guys keep privatizing these reports
hi day 1 realm veteran; alpha player converted to player for life
(super autism and 10 years in tech later i’ve been toying with this for a time)
[ why can’t we just all rollback when you push failed code public ?
Even my employer Apple let’s official downgrades happen especially when they drop the ball on a public build...]Symptom- Upon load as soon as player has written X data value packets to DB it kicks into a fail state and stops replying/pinging back; and seems to enter a rollback.
To a everyday player this looks like you lost your spot; to the autistic this looks like some terrible NBT and chunk rewriting going on. There are more details so please read on.
So I do think it is the size of the world or age, our realm is super old and super big.
Whatever it could be, I was able to get this same issue on a new map once I made it bigger than 3.5GB.doesn't that sound like a 32bit issue, and arent we in C x64 codebase?+
Cause it seems to me like with bees every time you add new blocks to the registry and back-end of the engine it all fails miserably for months while you play bug catch-up.
Outside of making this a soapbox (and I don’t want that i’m trying to give effective actionable feedback is all) let me suggest some fixes.
let OP realms dictate when to rollout; i get you are but give them the option to roll back. In the last year we the public and semi private realms have watched you bend over backwards to give and allow the featured servers roll back to versions two builds before the official client.(So it’s obvious if you did it for Mineplex you can do it for realms too.)
let OP; or even users send crash errors/reports to themselves since having a pile of them isn’t helping your workload; having a ability as users to filter out and give more effective feedback might help both sides in the battle for stable code.
Give OP of realm a optimize this realm button; clearly we didn’t outgrow the need to optimize the world like we need/have in the Java builds. Something is going on and hiding it is silly.
let me expand on how and why i’m arriving at this.
So up until you rolled out .30 unexpectedly the downside is you broke the whole economy trying to fix one console; not cool.
(as in in a PC user base nothing was really game breaking or needed fixing; btw thanks for trying to fix Nintendo)I had just completed a 4000x16x16 nether highway in a 72 hour build off leading to new chunks on our gigantic world from the first days of realms.
This bad boy has been thru it all and trust me has had is terrible bug days in the past. ( Bees/Aquatic were the worse heartaches)The thing is this time around as compared to 3 months ago it was building a highway to get to new bee chunks.
Everything was working perfectly, the .20 build was amazing; we had our 6 members on around the clock again building like crazy.
AGAIN to your credit .20 was amazing in our eyes; any crash was only minutes or no data loss.
We started trusting you and the code base. No joke hundreds of hours have been stolen away in build time or rebuilding over the last year.
Players left realms for good over it, and we are seeing that again now.
The new .30 is so broken that, everyone is stuck on our realms even the OP and cam accounts we have.
At most you get minutes of game play, I found a method to bring it forward 5 min max and it’s really ghetto what I need to do to accomplish.
We use to stress it was too many dropped blocks not picked up; but once .30 came out it’s clear the mob and engine rules have changed!!!
Our fire spread and mob griefing switches got reverted back; and in the looping fail-state they can’t be toggled back off.So that meant for me a ghast spawned onto the leaves i was laying on the highway; so my highway is on fire and even if I try and run away the crashing loop happens. (gonna get a clip of this its epic)
now that your sucked into my story I hope you feel for and try and ease my pain.
ive tried easing yours by documenting and trying lots of solutions before pointing at the problem; here’s some clues
1) it’s in the engine
2) it’s not timer based ( every x ticks )
3) can be tricked (using old client let’s you bring it forward a save state)
4) is probably related to entity metadata and spawning algorithm
5) it’s inevitable you can’t avoid the crash and looping cycle
I feel like i’m living in groundhog day.. I have no joke tried getting out of this 19 times and counting,
*The biggest thing is waiting for it to crash, rollback and recover. I cant imagine this is nice to your DataCente*r.Its not block state or data related 110% mob related.
- I could TP somewhere and crash it all the fastest.
- Couldn’t dig out or build out into a new save state.
- I could put the fire out with illegal flowing water and make the lava lake obsidian and not crash the game (block state) but the second I saw mobs and they started animating it would crash.
oh also when building out a block at a time trying to get to new region files thinking it’s the files; i found that a certain number of sounds played like placing leaves; it would also eventually buffer overflow and crash the realm too.
the easiest check is when your chat stops or you can not open chests fly or interact with mobs or you know they stop animating
I toyed with it being chat too, so if I dug into the wall and hid out I could chat echo nonstop.
Also also the second another player gets on anywhere in the realm it dies, unsure of the other players mob vicinity but i think its just after X packets are read off or written too the whole thing crashes.
anwyays no I don’t want to private this or get anything back;
i just wanted to sit down and pour out what I think is going on this time;
if we’re at our limit can we rip out all the education stuff we can’t even use on realms?
same with the pocket edition textures and code base.i know you know we don’t need underwater TNT
i am sure we know it’s a dupe
but you guys keep privatizing these reports
hi day 1 realm veteran; alpha player converted to player for life
(super autism and 10 years in tech later i’ve been toying with this for a time)
[ why can’t we just all rollback when you push failed code public ?
Even my employer Apple let’s official downgrades happen especially when they drop the ball on a public build...]Symptom- Upon load as soon as player has written X data value packets to DB it kicks into a fail state and stops replying/pinging back; and seems to enter a rollback.
To a everyday player this looks like you lost your spot; to the autistic this looks like some terrible NBT and chunk rewriting going on. There are more details so please read on.
So I do think it is the size of the world or age, our realm is super old and super big.
Whatever it could be, I was able to get this same issue on a new map once I made it bigger than 3.5GB.doesn't that sound like a 32bit issue, and arent we in C x64 codebase?
Cause it seems to me like with bees every time you add new blocks to the registry and back-end of the engine it all fails miserably for months while you play bug catch-up.
Outside of making this a soapbox (and I don’t want that i’m trying to give effective actionable feedback is all) let me suggest some fixes.
let OP realms dictate when to rollout; i get you are but give them the option to roll back. In the last year we the public and semi private realms have watched you bend over backwards to give and allow the featured servers roll back to versions two builds before the official client.(So it’s obvious if you did it for Mineplex you can do it for realms too.)
let OP; or even users send crash errors/reports to themselves since having a pile of them isn’t helping your workload; having a ability as users to filter out and give more effective feedback might help both sides in the battle for stable code.
Give OP of realm a optimize this realm button; clearly we didn’t outgrow the need to optimize the world like we need/have in the Java builds. Something is going on and hiding it is silly.
let me expand on how and why i’m arriving at this.
So up until you rolled out .30 unexpectedly the downside is you broke the whole economy trying to fix one console; not cool.
(as in in a PC user base nothing was really game breaking or needed fixing; btw thanks for trying to fix Nintendo)I had just completed a 4000x16x16 nether highway in a 72 hour build off leading to new chunks on our gigantic world from the first days of realms.
This bad boy has been thru it all and trust me has had is terrible bug days in the past. ( Bees/Aquatic were the worse heartaches)The thing is this time around as compared to 3 months ago it was building a highway to get to new bee chunks.
Everything was working perfectly, the .20 build was amazing; we had our 6 members on around the clock again building like crazy.
AGAIN to your credit .20 was amazing in our eyes; any crash was only minutes or no data loss.
We started trusting you and the code base. No joke hundreds of hours have been stolen away in build time or rebuilding over the last year.
Players left realms for good over it, and we are seeing that again now.
The new .30 is so broken that, everyone is stuck on our realms even the OP and cam accounts we have.
At most you get minutes of game play, I found a method to bring it forward 5 min max and it’s really ghetto what I need to do to accomplish.
We use to stress it was too many dropped blocks not picked up; but once .30 came out it’s clear the mob and engine rules have changed!!!
Our fire spread and mob griefing switches got reverted back; and in the looping fail-state they can’t be toggled back off.So that meant for me a ghast spawned onto the leaves i was laying on the highway; so my highway is on fire and even if I try and run away the crashing loop happens. (gonna get a clip of this its epic)
now that your sucked into my story I hope you feel for and try and ease my pain.
ive tried easing yours by documenting and trying lots of solutions before pointing at the problem; here’s some clues
1) it’s in the engine
2) it’s not timer based ( every x ticks )
3) can be tricked (using old client let’s you bring it forward a save state)
4) is probably related to entity metadata and spawning algorithm
5) it’s inevitable you can’t avoid the crash and looping cycle
I feel like i’m living in groundhog day.. I have no joke tried getting out of this 19 times and counting,
*The biggest thing is waiting for it to crash, rollback and recover. I cant imagine this is nice to your DataCente*r.Its not block state or data related 110% mob related.
- I could TP somewhere and crash it all the fastest.
- Couldn’t dig out or build out into a new save state.
- I could put the fire out with illegal flowing water and make the lava lake obsidian and not crash the game (block state) but the second I saw mobs and they started animating it would crash.
oh also when building out a block at a time trying to get to new region files thinking it’s the files; i found that a certain number of sounds played like placing leaves; it would also eventually buffer overflow and crash the realm too.
the easiest check is when your chat stops or you can not open chests fly or interact with mobs or you know they stop animating
I toyed with it being chat too, so if I dug into the wall and hid out I could chat echo nonstop.
Also also the second another player gets on anywhere in the realm it dies, unsure of the other players mob vicinity but i think its just after X packets are read off or written too the whole thing crashes.
anwyays no I don’t want to private this or get anything back;
i just wanted to sit down and pour out what I think is going on this time;
if we’re at our limit can we rip out all the education stuff we can’t even use on realms?
same with the pocket edition textures and code base.i know you know we don’t need underwater TNT
i am sure we know it’s a dupe
but you guys keep privatizing these reports
hi day 1 realm veteran; alpha player converted to player for life
(super autism and 10 years in tech later i’ve been toying with this for a time)
[ why can’t we just all rollback when you push failed code public ?
Even my employer Apple let’s official downgrades happen especially when they drop the ball on a public build...]Symptom- Upon load as soon as player has written X data value packets to DB it kicks into a fail state and stops replying/pinging back; and seems to enter a rollback.
To a everyday player this looks like you lost your spot; to the autistic this looks like some terrible NBT and chunk rewriting going on. There are more details so please read on.
So I do think it is the size of the world or age, our realm is super old and super big.
Whatever it could be, I was able to get this same issue on a new map once I made it bigger than 3.5GB.doesn't that sound like a 32bit issue, and arent we in C x64 codebase?
Cause it seems to me like with bees every time you add new blocks to the registry and back-end of the engine it all fails miserably for months while you play bug catch-up.
Outside of making this a soapbox (and I don’t want that i’m trying to give effective actionable feedback is all) let me suggest some fixes.
let OP realms dictate when to rollout; i get you are but give them the option to roll back. In the last year we the public and semi private realms have watched you bend over backwards to give and allow the featured servers roll back to versions two builds before the official client.(So it’s obvious if you did it for Mineplex you can do it for realms too.)
let OP; or even users send crash errors/reports to themselves since having a pile of them isn’t helping your workload; having a ability as users to filter out and give more effective feedback might help both sides in the battle for stable code.
Give OP of realm a optimize this realm button; clearly we didn’t outgrow the need to optimize the world like we need/have in the Java builds. Something is going on and hiding it is silly.
let me expand on how and why i’m arriving at this.
So up until you rolled out .30 unexpectedly the downside is you broke the whole economy trying to fix one console; not cool.
(as in in a PC user base nothing was really game breaking or needed fixing; btw thanks for trying to fix Nintendo)I had just completed a 4000x16x16 nether highway in a 72 hour build off leading to new chunks on our gigantic world from the first days of realms.
This bad boy has been thru it all and trust me has had is terrible bug days in the past. ( Bees/Aquatic were the worse heartaches)The thing is this time around as compared to 3 months ago it was building a highway to get to new bee chunks.
Everything was working perfectly, the .20 build was amazing; we had our 6 members on around the clock again building like crazy.
AGAIN to your credit .20 was amazing in our eyes; any crash was only minutes or no data loss.
We started trusting you and the code base. No joke hundreds of hours have been stolen away in build time or rebuilding over the last year.
Players left realms for good over it, and we are seeing that again now.
The new .30 is so broken that, everyone is stuck on our realms even the OP and cam accounts we have.
At most you get minutes of game play, I found a method to bring it forward 5 min max and it’s really ghetto what I need to do to accomplish.
We use to stress it was too many dropped blocks not picked up; but once .30 came out it’s clear the mob and engine rules have changed!!!
Our fire spread and mob griefing switches got reverted back; and in the looping fail-state they can’t be toggled back off.So that meant for me a ghast spawned onto the leaves i was laying on the highway; so my highway is on fire and even if I try and run away the crashing loop happens. (gonna get a clip of this its epic)
now that your sucked into my story I hope you feel for and try and ease my pain.
ive tried easing yours by documenting and trying lots of solutions before pointing at the problem; here’s some clues
1) it’s in the engine
2) it’s not timer based ( every x ticks )
3) can be tricked (using old client let’s you bring it forward a save state)
4) is probably related to entity metadata and spawning algorithm
5) it’s inevitable you can’t avoid the crash and looping cycle
I feel like i’m living in groundhog day.. I have no joke tried getting out of this 19 times and counting,
*The biggest thing is waiting for it to crash, rollback and recover. I cant imagine this is nice to your DataCente*r.Its not block state or data related 110% mob related.
- I could TP somewhere and crash it all the fastest.
- Couldn’t dig out or build out into a new save state.
- I could put the fire out with illegal flowing water and make the lava lake obsidian and not crash the game (block state) but the second I saw mobs and they started animating it would crash.
oh also when building out a block at a time trying to get to new region files thinking it’s the files; i found that a certain number of sounds played like placing leaves; it would also eventually buffer overflow and crash the realm too.
the easiest check is when your chat stops or you can not open chests fly or interact with mobs or you know they stop animating
I toyed with it being chat too, so if I dug into the wall and hid out I could chat echo nonstop.
Also also the second another player gets on anywhere in the realm it dies, unsure of the other players mob vicinity but i think its just after X packets are read off or written too the whole thing crashes.
anwyays no I don’t want to private this or get anything back;
i just wanted to sit down and pour out what I think is going on this time;
if we’re at our limit can we rip out all the education stuff we can’t even use on realms?
same with the pocket edition textures and code base.i know you know we don’t need underwater TNT
i am sure we know it’s a dupe
but you guys keep privatizing these reports
hi day 1 realm veteran; alpha player converted to player for life
(super autism and 10 years in tech later i’ve been toying with this for a time)
[ why can’t we just all rollback when you push failed code public ?
Even my employer Apple let’s official downgrades happen especially when they drop the ball on a public build...]Symptom- Upon load as soon as player has written X data value packets to DB it kicks into a fail state and stops replying/pinging back; and seems to enter a rollback.
To a everyday player this looks like you lost your spot; to the autistic this looks like some terrible NBT and chunk rewriting going on. There are more details so please read on.
So I do think it is the size of the world or age, our realm is super old and super big.
Whatever it could be, I was able to get this same issue on a new map once I made it bigger than 3.5GB.doesn't that sound like a 32bit issue, and arent we in C x64 codebase?
Cause it seems to me like with bees every time you add new blocks to the registry and back-end of the engine it all fails miserably for months while you play bug catch-up.
Outside of making this a soapbox (and I don’t want that i’m trying to give effective actionable feedback is all) let me suggest some fixes.
let OP realms dictate when to rollout; i get you are but give them the option to roll back. In the last year we the public and semi private realms have watched you bend over backwards to give and allow the featured servers roll back to versions two builds before the official client.(So it’s obvious if you did it for Mineplex you can do it for realms too.)
let OP; or even users send crash errors/reports to themselves since having a pile of them isn’t helping your workload; having a ability as users to filter out and give more effective feedback might help both sides in the battle for stable code.
Give OP of realm a optimize this realm button; clearly we didn’t outgrow the need to optimize the world like we need/have in the Java builds. Something is going on and hiding it is silly.
let me expand on how and why i’m arriving at this.
So up until you rolled out .30 unexpectedly the downside is you broke the whole economy trying to fix one console; not cool.
(as in in a PC user base nothing was really game breaking or needed fixing; btw thanks for trying to fix Nintendo)I had just completed a 4000x16x16 nether highway in a 72 hour build off leading to new chunks on our gigantic world from the first days of realms.
This bad boy has been thru it all and trust me has had is terrible bug days in the past. ( Bees/Aquatic were the worse heartaches)The thing is this time around as compared to 3 months ago it was building a highway to get to new bee chunks.
Everything was working perfectly, the .20 build was amazing; we had our 6 members on around the clock again building like crazy.
AGAIN to your credit .20 was amazing in our eyes; any crash was only minutes or no data loss.
We started trusting you and the code base. No joke hundreds of hours have been stolen away in build time or rebuilding over the last year.
Players left realms for good over it, and we are seeing that again now.
The new .30 is so broken that, everyone is stuck on our realms even the OP and cam accounts we have.
At most you get minutes of game play, I found a method to bring it forward 5 min max and it’s really ghetto what I need to do to accomplish.
We use to stress it was too many dropped blocks not picked up; but once .30 came out it’s clear the mob and engine rules have changed!!!
Our fire spread and mob griefing switches got reverted back; and in the looping fail-state they can’t be toggled back off.So that meant for me a ghast spawned onto the leaves i was laying on the highway; so my highway is on fire and even if I try and run away the crashing loop happens. (gonna get a clip of this its epic)
now that your sucked into my story I hope you feel for and try and ease my pain.
ive tried easing yours by documenting and trying lots of solutions before pointing at the problem; here’s some clues
1) it’s in the engine
2) it’s not timer based ( every x ticks )
3) can be tricked (using old client let’s you bring it forward a save state)
4) is probably related to entity metadata and spawning algorithm
5) it’s inevitable you can’t avoid the crash and looping cycle
I feel like i’m living in groundhog day.. I have no joke tried getting out of this 19 times and counting,
*The biggest thing is waiting for it to crash, rollback and recover. I cant imagine this is nice to your DataCente*r.Its not block state or data related 110% mob related.
- I could TP somewhere and crash it all the fastest.
- Couldn’t dig out or build out into a new save state.
- I could put the fire out with illegal flowing water and make the lava lake obsidian and not crash the game (block state) but the second I saw mobs and they started animating it would crash.
oh also when building out a block at a time trying to get to new region files thinking it’s the files; i found that a certain number of sounds played like placing leaves; it would also eventually buffer overflow and crash the realm too.
the easiest check is when your chat stops or you can not open chests fly or interact with mobs or you know they stop animating
I toyed with it being chat too, so if I dug into the wall and hid out I could chat echo nonstop.
Also also the second another player gets on anywhere in the realm it dies, unsure of the other players mob vicinity but i think its just after X packets are read off or written too the whole thing crashes.
anwyays no I don’t want to private this or get anything back;
i just wanted to sit down and pour out what I think is going on this time;
if we’re at our limit can we rip out all the education stuff we can’t even use on realms?
same with the pocket edition textures and code base.i know you know we don’t need underwater TNT
i am sure we know it’s a dupe
but you guys keep privatizing these reports
hi day 1 realm veteran; alpha player converted to player for life
(super autism and 10 years in tech later i’ve been toying with this for a time)
[ why can’t we just all rollback when you push failed code public ?
Even my employer Apple let’s official downgrades happen especially when they drop the ball on a public build...]Symptom- Upon load as soon as player has written X data value packets to DB it kicks into a fail state and stops replying/pinging back; and seems to enter a rollback.
To a everyday player this looks like you lost your spot; to the autistic this looks like some terrible NBT and chunk rewriting going on. There are more details so please read on.
So I do think it is the size of the world or age, our realm is super old and super big.
Whatever it could be, I was able to get this same issue on a new map once I made it bigger than 3.5GB.doesn't that sound like a 32bit issue, and arent we in
C x64 codebase?Cause it seems to me like with bees every time you add new blocks to the registry and back-end of the engine it all fails miserably for months while you play bug catch-up.
Outside of making this a soapbox (and I don’t want that i’m trying to give effective actionable feedback is all) let me suggest some fixes.
let OP realms dictate when to rollout; i get you are but give them the option to roll back. In the last year we the public and semi private realms have watched you bend over backwards to give and allow the featured servers roll back to versions two builds before the official client.(So it’s obvious if you did it for Mineplex you can do it for realms too.)
let OP; or even users send crash errors/reports to themselves since having a pile of them isn’t helping your workload; having a ability as users to filter out and give more effective feedback might help both sides in the battle for stable code.
Give OP of realm a optimize this realm button; clearly we didn’t outgrow the need to optimize the world like we need/have in the Java builds. Something is going on and hiding it is silly.
let me expand on how and why i’m arriving at this.
So up until you rolled out .30 unexpectedly the downside is you broke the whole economy trying to fix one console; not cool.
(as in in a PC user base nothing was really game breaking or needed fixing; btw thanks for trying to fix Nintendo)I had just completed a 4000x16x16 nether highway in a 72 hour build off leading to new chunks on our gigantic world from the first days of realms.
This bad boy has been thru it all and trust me has had is terrible bug days in the past. ( Bees/Aquatic were the worse heartaches)The thing is this time around as compared to 3 months ago it was building a highway to get to new bee chunks.
Everything was working perfectly, the .20 build was amazing; we had our 6 members on around the clock again building like crazy.
AGAIN to your credit .20 was amazing in our eyes; any crash was only minutes or no data loss.
We started trusting you and the code base. No joke hundreds of hours have been stolen away in build time or rebuilding over the last year.
Players left realms for good over it, and we are seeing that again now.
The new .30 is so broken that, everyone is stuck on our realms even the OP and cam accounts we have.
At most you get minutes of game play, I found a method to bring it forward 5 min max and it’s really ghetto what I need to do to accomplish.
We use to stress it was too many dropped blocks not picked up; but once .30 came out it’s clear the mob and engine rules have changed!!!
Our fire spread and mob griefing switches got reverted back; and in the looping fail-state they can’t be toggled back off.So that meant for me a ghast spawned onto the leaves i was laying on the highway; so my highway is on fire and even if I try and run away the crashing loop happens. (gonna get a clip of this its epic)
now that your sucked into my story I hope you feel for and try and ease my pain.
ive tried easing yours by documenting and trying lots of solutions before pointing at the problem; here’s some clues
1) it’s in the engine
2) it’s not timer based ( every x ticks )
3) can be tricked (using old client let’s you bring it forward a save state)
4) is probably related to entity metadata and spawning algorithm
5) it’s inevitable you can’t avoid the crash and looping cycle
I feel like i’m living in groundhog day.. I have no joke tried getting out of this 19 times and counting,
*The biggest thing is waiting for it to crash, rollback and recover. I cant imagine this is nice to your DataCente*r.Its not block state or data related 110% mob related.
- I could TP somewhere and crash it all the fastest.
- Couldn’t dig out or build out into a new save state.
- I could put the fire out with illegal flowing water and make the lava lake obsidian and not crash the game (block state) but the second I saw mobs and they started animating it would crash.
oh also when building out a block at a time trying to get to new region files thinking it’s the files; i found that a certain number of sounds played like placing leaves; it would also eventually buffer overflow and crash the realm too.
the easiest check is when your chat stops or you can not open chests fly or interact with mobs or you know they stop animating
I toyed with it being chat too, so if I dug into the wall and hid out I could chat echo nonstop.
Also also the second another player gets on anywhere in the realm it dies, unsure of the other players mob vicinity but i think its just after X packets are read off or written too the whole thing crashes.
anwyays no I don’t want to private this or get anything back;
i just wanted to sit down and pour out what I think is going on this time;
if we’re at our limit can we rip out all the education stuff we can’t even use on realms?
same with the pocket edition textures and code base.i know you know we don’t need underwater TNT
i am sure we know it’s a dupe
but you guys keep privatizing these reports
hi day 1 realm veteran; alpha player converted to player for life
(super autism and 10 years in tech later i’ve been toying with this for a time)
[ why can’t we just all rollback when you push failed code public ?
Even my employer Apple let’s official downgrades happen especially when they drop the ball on a public build...]Symptom- Upon load as soon as player has written X data value packets to DB it kicks into a fail state and stops replying/pinging back; and seems to enter a rollback.
To a everyday player this looks like you lost your spot; to the autistic this looks like some terrible NBT and chunk rewriting going on. There are more details so please read on.
So I do think it is the size of the world or age, our realm is super old and super big.
Whatever it could be, I was able to get this same issue on a new map once I made it bigger than 3.5GB.doesn't that sound like a 32bit issue, and arent we in C+ x64 codebase?+
Cause it seems to me like with bees every time you add new blocks to the registry and back-end of the engine it all fails miserably for months while you play bug catch-up.
Outside of making this a soapbox (and I don’t want that i’m trying to give effective actionable feedback is all) let me suggest some fixes.
let OP realms dictate when to rollout; i get you are but give them the option to roll back. In the last year we the public and semi private realms have watched you bend over backwards to give and allow the featured servers roll back to versions two builds before the official client.(So it’s obvious if you did it for Mineplex you can do it for realms too.)
let OP; or even users send crash errors/reports to themselves since having a pile of them isn’t helping your workload; having a ability as users to filter out and give more effective feedback might help both sides in the battle for stable code.
Give OP of realm a optimize this realm button; clearly we didn’t outgrow the need to optimize the world like we need/have in the Java builds. Something is going on and hiding it is silly.
let me expand on how and why i’m arriving at this.
So up until you rolled out .30 unexpectedly the downside is you broke the whole economy trying to fix one console; not cool.
(as in in a PC user base nothing was really game breaking or needed fixing; btw thanks for trying to fix Nintendo)I had just completed a 4000x16x16 nether highway in a 72 hour build off leading to new chunks on our gigantic world from the first days of realms.
This bad boy has been thru it all and trust me has had is terrible bug days in the past. ( Bees/Aquatic were the worse heartaches)The thing is this time around as compared to 3 months ago it was building a highway to get to new bee chunks.
Everything was working perfectly, the .20 build was amazing; we had our 6 members on around the clock again building like crazy.
AGAIN to your credit .20 was amazing in our eyes; any crash was only minutes or no data loss.
We started trusting you and the code base. No joke hundreds of hours have been stolen away in build time or rebuilding over the last year.
Players left realms for good over it, and we are seeing that again now.
The new .30 is so broken that, everyone is stuck on our realms even the OP and cam accounts we have.
At most you get minutes of game play, I found a method to bring it forward 5 min max and it’s really ghetto what I need to do to accomplish.
We use to stress it was too many dropped blocks not picked up; but once .30 came out it’s clear the mob and engine rules have changed!!!
Our fire spread and mob griefing switches got reverted back; and in the looping fail-state they can’t be toggled back off.So that meant for me a ghast spawned onto the leaves i was laying on the highway; so my highway is on fire and even if I try and run away the crashing loop happens. (gonna get a clip of this its epic)
now that your sucked into my story I hope you feel for and try and ease my pain.
ive tried easing yours by documenting and trying lots of solutions before pointing at the problem; here’s some clues
1) it’s in the engine
2) it’s not timer based ( every x ticks )
3) can be tricked (using old client let’s you bring it forward a save state)
4) is probably related to entity metadata and spawning algorithm
5) it’s inevitable you can’t avoid the crash and looping cycle
I feel like i’m living in groundhog day.. I have no joke tried getting out of this 19 times and counting,
*The biggest thing is waiting for it to crash, rollback and recover. I cant imagine this is nice to your DataCenter.Its not block state or data related 110% mob related.
- I could TP somewhere and crash it all the fastest.
- Couldn’t dig out or build out into a new save state.
- I could put the fire out with illegal flowing water and make the lava lake obsidian and not crash the game (block state) but the second I saw mobs and they started animating it would crash.
oh also when building out a block at a time trying to get to new region files thinking it’s the files; i found that a certain number of sounds played like placing leaves; it would also eventually buffer overflow and crash the realm too.
the easiest check is when your chat stops or you can not open chests fly or interact with mobs or you know they stop animating
I toyed with it being chat too, so if I dug into the wall and hid out I could chat echo nonstop.
Also also the second another player gets on anywhere in the realm it dies, unsure of the other players mob vicinity but i think its just after X packets are read off or written too the whole thing crashes.
anwyays no I don’t want to private this or get anything back;
i just wanted to sit down and pour out what I think is going on this time;
if we’re at our limit can we rip out all the education stuff we can’t even use on realms?
same with the pocket edition textures and code base.i know you know we don’t need underwater TNT
i am sure we know it’s a dupe
but you guys keep privatizing these reports
hi day 1 realm veteran; alpha player converted to player for life
(super autism and 10 years in tech later i’ve been toying with this for a time)
[ why can’t we just all rollback when you push failed code public ?
Even my employer Apple let’s official downgrades happen especially when they drop the ball on a public build...]Symptom- Upon load as soon as player has written X data value packets to DB it kicks into a fail state and stops replying/pinging back; and seems to enter a rollback.
To a everyday player this looks like you lost your spot; to the autistic this looks like some terrible NBT and chunk rewriting going on. There are more details so please read on.
So I do think it is the size of the world or age, our realm is super old and super big.
Whatever it could be, I was able to get this same issue on a new map once I made it bigger than 3.5GB.doesn't that sound like a 32bit issue, and arent we in C+ x64 codebase?+
Cause it seems to me like with bees every time you add new blocks to the registry and back-end of the engine it all fails miserably for months while you play bug catch-up.
Outside of making this a soapbox (and I don’t want that i’m trying to give effective actionable feedback is all) let me suggest some fixes.
let OP realms dictate when to rollout; i get you are but give them the option to roll back. In the last year we the public and semi private realms have watched you bend over backwards to give and allow the featured servers roll back to versions two builds before the official client.(So it’s obvious if you did it for Mineplex you can do it for realms too.)
let OP; or even users send crash errors/reports to themselves since having a pile of them isn’t helping your workload; having a ability as users to filter out and give more effective feedback might help both sides in the battle for stable code.
Give OP of realm a optimize this realm button; clearly we didn’t outgrow the need to optimize the world like we need/have in the Java builds. Something is going on and hiding it is silly.
let me expand on how and why i’m arriving at this.
So up until you rolled out .30 unexpectedly the downside is you broke the whole economy trying to fix one console; not cool.
(as in in a PC user base nothing was really game breaking or needed fixing; btw thanks for trying to fix Nintendo)I had just completed a 4000x16x16 nether highway in a 72 hour build off leading to new chunks on our gigantic world from the first days of realms.
This bad boy has been thru it all and trust me has had is terrible bug days in the past. ( Bees/Aquatic were the worse heartaches)The thing is this time around as compared to 3 months ago it was building a highway to get to new bee chunks.
Everything was working perfectly, the .20 build was amazing; we had our 6 members on around the clock again building like crazy.
AGAIN to your credit .20 was amazing in our eyes; any crash was only minutes or no data loss.
We started trusting you and the code base. No joke hundreds of hours have been stolen away in build time or rebuilding over the last year.
Players left realms for good over it, and we are seeing that again now.
The new .30 is so broken that, everyone is stuck on our realms even the OP and cam accounts we have.
At most you get minutes of game play, I found a method to bring it forward 5 min max and it’s really ghetto what I need to do to accomplish.
We use to stress it was too many dropped blocks not picked up; but once .30 came out it’s clear the mob and engine rules have changed!!!
Our fire spread and mob griefing switches got reverted back; and in the looping fail-state they can’t be toggled back off.So that meant for me a ghast spawned onto the leaves i was laying on the highway; so my highway is on fire and even if I try and run away the crashing loop happens. (gonna get a clip of this its epic)
now that your sucked into my story I hope you feel for and try and ease my pain.
ive tried easing yours by documenting and trying lots of solutions before pointing at the problem; here’s some clues
1) it’s in the engine
2) it’s not timer based ( every x ticks )
3) can be tricked (using old client let’s you bring it forward a save state)
4) is probably related to entity metadata and spawning algorithm
5) it’s inevitable you can’t avoid the crash and looping cycle
I feel like i’m living in groundhog day.. I have no joke tried getting out of this 19 times and counting,
*The biggest thing is waiting for it to crash, rollback and recover. I cant imagine this is nice to your DataCenter.Its not block state or data related 110% mob related.
- I could TP somewhere and crash it all the fastest.
- Couldn’t dig out or build out into a new save state.
- I could put the fire out with illegal flowing water and make the lava lake obsidian and not crash the game (block state) but the second I saw mobs and they started animating it would crash.
oh also when building out a block at a time trying to get to new region files thinking it’s the files; i found that a certain number of sounds played like placing leaves; it would also eventually buffer overflow and crash the realm too.
the easiest check is when your chat stops or you can not open chests fly or interact with mobs or you know they stop animating
I toyed with it being chat too, so if I dug into the wall and hid out I could chat echo nonstop.
Also also the second another player gets on anywhere in the realm it dies, unsure of the other players mob vicinity but i think its just after X packets are read off or written too the whole thing crashes.
an
wyays no I don’t want to private this or get anything back;i just wanted to sit down and pour out what I think is going on this time;
if we’re at our limit can we rip out all the education stuff we can’t even use on realms?
same with the pocket edition textures and code base.i know you know we don’t need underwater TNT
i am sure we know it’s a dupe
but you guys keep privatizing these reports
hi day 1 realm veteran; alpha player converted to player for life
(super autism and 10 years in tech later i’ve been toying with this for a time)
[ why can’t we just all rollback when you push failed code public ?
Even my employer Apple let’s official downgrades happen especially when they drop the ball on a public build...]Symptom- Upon load as soon as player has written X data value packets to DB it kicks into a fail state and stops replying/pinging back; and seems to enter a rollback.
To a everyday player this looks like you lost your spot; to the autistic this looks like some terrible NBT and chunk rewriting going on. There are more details so please read on.
So I do think it is the size of the world or age, our realm is super old and super big.
Whatever it could be, I was able to get this same issue on a new map once I made it bigger than 3.5GB.doesn't that sound like a 32bit issue, and arent we in C++ x64 codebase?+
Cause it seems to me like with bees every time you add new blocks to the registry and back-end of the engine it all fails miserably for months while you play bug catch-up.
Outside of making this a soapbox (and I don’t want that i’m trying to give effective actionable feedback is all) let me suggest some fixes.
let OP realms dictate when to rollout; i get you are but give them the option to roll back. In the last year we the public and semi private realms have watched you bend over backwards to give and allow the featured servers roll back to versions two builds before the official client.(So it’s obvious if you did it for Mineplex you can do it for realms too.)
let OP; or even users send crash errors/reports to themselves since having a pile of them isn’t helping your workload; having a ability as users to filter out and give more effective feedback might help both sides in the battle for stable code.
Give OP of realm a optimize this realm button; clearly we didn’t outgrow the need to optimize the world like we need/have in the Java builds. Something is going on and hiding it is silly.
let me expand on how and why i’m arriving at this.
So up until you rolled out .30 unexpectedly the downside is you broke the whole economy trying to fix one console; not cool.
(as in in a PC user base nothing was really game breaking or needed fixing; btw thanks for trying to fix Nintendo)I had just completed a 4000x16x16 nether highway in a 72 hour build off leading to new chunks on our gigantic world from the first days of realms.
This bad boy has been thru it all and trust me has had is terrible bug days in the past. ( Bees/Aquatic were the worse heartaches)The thing is this time around as compared to 3 months ago it was building a highway to get to new bee chunks.
Everything was working perfectly, the .20 build was amazing; we had our 6 members on around the clock again building like crazy.
AGAIN to your credit .20 was amazing in our eyes; any crash was only minutes or no data loss.
We started trusting you and the code base. No joke hundreds of hours have been stolen away in build time or rebuilding over the last year.
Players left realms for good over it, and we are seeing that again now.
The new .30 is so broken that, everyone is stuck on our realms even the OP and cam accounts we have.
At most you get minutes of game play, I found a method to bring it forward 5 min max and it’s really ghetto what I need to do to accomplish.
We use to stress it was too many dropped blocks not picked up; but once .30 came out it’s clear the mob and engine rules have changed!!!
Our fire spread and mob griefing switches got reverted back; and in the looping fail-state they can’t be toggled back off.So that meant for me a ghast spawned onto the leaves i was laying on the highway; so my highway is on fire and even if I try and run away the crashing loop happens. (gonna get a clip of this its epic)
now that your sucked into my story I hope you feel for and try and ease my pain.
ive tried easing yours by documenting and trying lots of solutions before pointing at the problem; here’s some clues
1) it’s in the engine
2) it’s not timer based ( every x ticks )
3) can be tricked (using old client let’s you bring it forward a save state)
4) is probably related to entity metadata and spawning algorithm
5) it’s inevitable you can’t avoid the crash and looping cycle
I feel like i’m living in groundhog day.. I have no joke tried getting out of this 19 times and counting,
*The biggest thing is waiting for it to crash, rollback and recover. I cant imagine this is nice to your DataCenter.Its not block state or data related 110% mob related.
- I could TP somewhere and crash it all the fastest.
- Couldn’t dig out or build out into a new save state.
- I could put the fire out with illegal flowing water and make the lava lake obsidian and not crash the game (block state) but the second I saw mobs and they started animating it would crash.
oh also when building out a block at a time trying to get to new region files thinking it’s the files; i found that a certain number of sounds played like placing leaves; it would also eventually buffer overflow and crash the realm too.
the easiest check is when your chat stops or you can not open chests fly or interact with mobs or you know they stop animating
I toyed with it being chat too, so if I dug into the wall and hid out I could chat echo nonstop.
Also also the second another player gets on anywhere in the realm it dies, unsure of the other players mob vicinity but i think its just after X packets are read off or written too the whole thing crashes.
anyways no I don’t want to private this or get anything back;
i just wanted to sit down and pour out what I think is going on this time;
if we’re at our limit can we rip out all the education stuff we can’t even use on realms?
same with the pocket edition textures and code base.i know you know we don’t need underwater TNT
i am sure we know it’s a dupe
but you guys keep privatizing these reports
hi day 1 realm veteran; alpha player converted to player for life
(super autism and 10 years in tech later i’ve been toying with this for a time)
[ why can’t we just all rollback when you push failed code public ?
Even my employer Apple let’s official downgrades happen especially when they drop the ball on a public build...]Symptom- Upon load as soon as player has written X data value packets to DB it kicks into a fail state and stops replying/pinging back; and seems to enter a rollback.
To a everyday player this looks like you lost your spot; to the autistic this looks like some terrible NBT and chunk rewriting going on. There are more details so please read on.
So I do think it is the size of the world or age, our realm is super old and super big.
Whatever it could be, I was able to get this same issue on a new map once I made it bigger than 3.5GB.doesn't that sound like a 32bit issue, and arent we in C++ x64 codebase?+
Cause it seems to me like with bees every time you add new blocks to the registry and back-end of the engine it all fails miserably for months while you play bug catch-up.
Outside of making this a soapbox (and I don’t want that i’m trying to give effective actionable feedback is all) let me suggest some fixes.
let OP realms dictate when to rollout; i get you are but give them the option to roll back. In the last year we the public and semi private realms have watched you bend over backwards to give and allow the featured servers roll back to versions two builds before the official client.(So it’s obvious if you did it for Mineplex you can do it for realms too.)
let OP; or even users send crash errors/reports to themselves since having a pile of them isn’t helping your workload; having a ability as users to filter out and give more effective feedback might help both sides in the battle for stable code.
Give OP of realm a optimize this realm button; clearly we didn’t outgrow the need to optimize the world like we need/have in the Java builds. Something is going on and hiding it is silly.
let me expand on how and why i’m arriving at this.
So up until you rolled out .30 unexpectedly the downside is you broke the whole economy trying to fix one console; not cool.
(as in in a PC user base nothing was really game breaking or needed fixing; btw thanks for trying to fix Nintendo)I had just completed a 4000x16x16 nether highway in a 72 hour build off leading to new chunks on our gigantic world from the first days of realms.
This bad boy has been thru it all and trust me has had is terrible bug days in the past. ( Bees/Aquatic were the worse heartaches)The thing is this time around as compared to 3 months ago it was building a highway to get to new bee chunks.
Everything was working perfectly, the .20 build was amazing; we had our 6 members on around the clock again building like crazy.
AGAIN to your credit .20 was amazing in our eyes; any crash was only minutes or no data loss.
We started trusting you and the code base. No joke hundreds of hours have been stolen away in build time or rebuilding over the last year.
Players left realms for good over it, and we are seeing that again now.
The new .30 is so broken that, everyone is stuck on our realms even the OP and
camaccounts we have.
At most you get minutes of game play, I found a method to bring it forward 5 min max and it’s really ghetto what I need to do to accomplish.
We use to stress it was too many dropped blocks not picked up; but once .30 came out it’s clear the mob and engine rules have changed!!!
Our fire spread and mob griefing switches got reverted back; and in the looping fail-state they can’t be toggled back off.So that meant for me a ghast spawned onto the leaves i was laying on the highway; so my highway is on fire and even if I try and run away the crashing loop happens. (gonna get a clip of this its epic)
now that your sucked into my story I hope you feel for and try and ease my pain.
ive tried easing yours by documenting and trying lots of solutions before pointing at the problem; here’s some clues
1) it’s in the engine
2) it’s not timer based ( every x ticks )
3) can be tricked (using old client let’s you bring it forward a save state)
4) is probably related to entity metadata and spawning algorithm
5) it’s inevitable you can’t avoid the crash and looping cycle
I feel like i’m living in groundhog day.. I have no joke tried getting out of this 19 times and counting,
*The biggest thing is waiting for it to crash, rollback and recover. I cant imagine this is nice to your DataCenter.Its not block state or data related 110% mob related.
- I could TP somewhere and crash it all the fastest.
- Couldn’t dig out or build out into a new save state.
- I could put the fire out with illegal flowing water and make the lava lake obsidian and not crash the game (block state) but the second I saw mobs and they started animating it would crash.
oh also when building out a block at a time trying to get to new region files thinking it’s the files; i found that a certain number of sounds played like placing leaves; it would also eventually buffer overflow and crash the realm too.
the easiest check is when your chat stops or you can not open chests fly or interact with mobs or you know they stop animating
I toyed with it being chat too, so if I dug into the wall and hid out I could chat echo nonstop.
Also also the second another player gets on anywhere in the realm it dies, unsure of the other players mob vicinity but i think its just after X packets are read off or written too the whole thing crashes.
anyways no I don’t want to private this or get anything back;
i just wanted to sit down and pour out what I think is going on this time;
if we’re at our limit can we rip out all the education stuff we can’t even use on realms?
same with the pocket edition textures and code base.i know you know we don’t need underwater TNT
i am sure we know it’s a dupe
but you guys keep privatizing these reports
hi day 1 realm veteran; alpha player converted to player for life
(super autism and 10 years in tech later i’ve been toying with this for a time)
[ why can’t we just all rollback when you push failed code public ?
Even my employer Apple let’s official downgrades happen especially when they drop the ball on a public build...]Symptom- Upon load as soon as player has written X data value packets to DB it kicks into a fail state and stops replying/pinging back; and seems to enter a rollback.
To a everyday player this looks like you lost your spot; to the autistic this looks like some terrible NBT and chunk rewriting going on. There are more details so please read on.
So I do think it is the size of the world or age, our realm is super old and super big.
Whatever it could be, I was able to get this same issue on a new map once I made it bigger than 3.5GB.doesn't that sound like a 32bit issue, and arent we in C+++ x64 codebase?
Cause it seems to me like with bees every time you add new blocks to the registry and back-end of the engine it all fails miserably for months while you play bug catch-up.
Outside of making this a soapbox (and I don’t want that i’m trying to give effective actionable feedback is all) let me suggest some fixes.
let OP realms dictate when to rollout; i get you are but give them the option to roll back. In the last year we the public and semi private realms have watched you bend over backwards to give and allow the featured servers roll back to versions two builds before the official client.(So it’s obvious if you did it for Mineplex you can do it for realms too.)
let OP; or even users send crash errors/reports to themselves since having a pile of them isn’t helping your workload; having a ability as users to filter out and give more effective feedback might help both sides in the battle for stable code.
Give OP of realm a optimize this realm button; clearly we didn’t outgrow the need to optimize the world like we need/have in the Java builds. Something is going on and hiding it is silly.
let me expand on how and why i’m arriving at this.
So up until you rolled out .30 unexpectedly the downside is you broke the whole economy trying to fix one console; not cool.
(as in in a PC user base nothing was really game breaking or needed fixing; btw thanks for trying to fix Nintendo)I had just completed a 4000x16x16 nether highway in a 72 hour build off leading to new chunks on our gigantic world from the first days of realms.
This bad boy has been thru it all and trust me has had is terrible bug days in the past. ( Bees/Aquatic were the worse heartaches)The thing is this time around was easy compared to 3 months ago it was building a highway to get to new bee chunks.
(In the past we lost our highway builds in progress to random super far back rollback, now at least its minimal rollback)Everything was working perfectly, the .20 build was amazing; we had our 6 members on around the clock again building like crazy.
AGAIN to your credit .20 was amazing in our eyes; again any crash was only minutes or no data loss.
We started trusting you and the code base. No joke hundreds of hours have been stolen away in build time or rebuilding over the last year.
Players left realms for good over it, and we are seeing that again now.
The new .30 is so broken that, everyone is stuck on our realms even the OP and alt accounts we have.
At most you get minutes of game play, I found a method to bring it forward 5 min max and it’s really ghetto what I need to do to accomplish.
We use to stress it was too many dropped blocks not picked up; but once .30 came out it’s clear the mob and engine rules have changed!!!
Our fire spread and mob griefing switches got reverted back; and in the looping fail-state they can’t be toggled back off.So that meant for me a ghast spawned onto the leaves i was laying on the highway; so my highway is on fire and even if I try and run away the crashing loop happens. (gonna get a clip of this its epic)
now that your sucked into my story I hope you feel for and try and ease my pain.
ive tried easing yours by documenting and trying lots of solutions before pointing at the problem; here’s some clues
1) it’s in the engine
2) it’s not timer based ( every x ticks )
3) can be tricked (using old client let’s you bring it forward a save state)
4) is probably related to entity metadata and spawning algorithm
5) it’s inevitable you can’t avoid the crash and looping cycle
I feel like i’m living in groundhog day.. I have no joke tried getting out of this 19 times and counting,
*The biggest thing is waiting for it to crash, rollback and recover. I cant imagine this is nice to your DataCenter.Its not block state or data related 110% mob related.
- I could TP somewhere and crash it all the fastest.
- Couldn’t dig out or build out into a new save state.
- I could put the fire out with illegal flowing water and make the lava lake obsidian and not crash the game (block state) but the second I saw mobs and they started animating it would crash.
oh also when building out a block at a time trying to get to new region files thinking it’s the files; i found that a certain number of sounds played like placing leaves; it would also eventually buffer overflow and crash the realm too.
the easiest check is when your chat stops or you can not open chests fly or interact with mobs or you know they stop animating
I toyed with it being chat too, so if I dug into the wall and hid out I could chat echo nonstop.
Also also the second another player gets on anywhere in the realm it dies, unsure of the other players mob vicinity but i think its just after X packets are read off or written too the whole thing crashes.
anyways no I don’t want to private this or get anything back;
i just wanted to sit down and pour out what I think is going on this time;
if we’re at our limit can we rip out all the education stuff we can’t even use on realms?
same with the pocket edition textures and code base.i know you know we don’t need underwater TNT
![[MCPE Mod] Celesian](../../../data/avatars/users/81635.png){kind=small}
![[Helper] osfanbuff63](../../../data/avatars/users/94394.png){kind=small}
Thank you for your report!
Unfortunately, this report is not valid for the bug tracker and is a partial duplicate for several reasons:
1. Crashes such as these are logged automatically, this will therefore be investigated further by the development team internally.
2. The rollback that happens after the crash is being tracked as MCPE-12347, so that part is a duplicate
3. Much of your report consists of suggestions for new features. These should be submitted to the Feedback site at the link below.
However, if you can reliably reproduce a crash and provide a repeatable sequence of steps to do so, that can be useful to include in a (new) report. Please limit any such report to information related to reproducing the crash.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki – 📖 FAQs