Hiram Chavez
- ShadowFlame303
- shadowflame303
- Europe/Stockholm
- Yes
- No
MCPE-40162
I've been playing on a few survival servers and I've noticed that enchanting does not work.
Going uptoan enchantment table brings up the enchanting menu for a split second and then it dissapears.
Reproducing the bug is pretty simple, just go into any survival server and tryenchanting. Themenupops upand then dissapears.It doesn't work.
Also, I'm not sure if this a server side bug maybe because enchanting does work for me in singleplayer, multiplayer (local/wifi) and realms. It only doesn't work on servers.Android 8.0 (EMUI 8)
Huawei Mate 10 (ALP-L09)
MCPE 1.8 (1.8.0.24 play store version)
I've been playing on a few survival servers and I've noticed that enchanting does not work. I've tried on two different servers and encountered two ways it doesn't work.
Server 1) Going up to an enchantment table brings up the enchanting menu for a split second and then it dissapears.
Server 2) Going up to an enchantment table does bring up the menu but trying to put something in puts the item back into my inventory.
Also, I'm not sure if this a server side bug maybe because enchanting does work for me in singleplayer, multiplayer (local/wifi) and realms. It only doesn't work on servers.
Android 8.0 (EMUI 8)
Huawei Mate 10 (ALP-L09)
MCPE 1.8 (1.8.0.24 play store version)
Enchanting on MCPE 1.8.0.24 servers doesn't work
Tried transferring two (one amplified with large biomes, one default. Both with large world size) of my completely survival worlds with absolutely no cheats from PS4 Edition and both resulted in cheats being turned on and trophies unable to be earned.
After doing some testing by creating new completely survival worlds, I think it has to do something with turning on game rules such as fire spread in-game (with the little testing I did it seems that changing them in the world saves menu doesn't have the same affect).
Turning the game rules back to "default" (that the game would set if untouched in world settings) in PS4 edition before transferring them over to Bedrock still results in cheats being activated and no trophies being available to earn.
In conclusion, it seems that tinkering in anyway (off or back on) with game rules that don't get rid of trophies (such as fire spread) via the touchpad once inside the actual world in PS4 Edition, results in cheats being turned on once converted to Bedrock and trophies unable to be earned anymore
Tried transferring two (one amplified with large biomes, one default. Both with large world size) of my completely survival worlds with absolutely no cheats from PS4 Edition and both resulted in cheats being turned on and trophies unable to be earned.
After doing some testing by creating new completely survival worlds, I think it has to do something with turning on game rules such as fire spread in-game (with the little testing I did it seems that changing them in the world saves menu doesn't have the same affect).
Turning the game rules back to "default" (that the game would set if untouched in world settings) in PS4 edition before transferring them over to Bedrock still results in cheats being activated and no trophies being available to earn.
In conclusion, it seems that tinkering in anyway (off or back on) with game rules that don't get rid of trophies (such as fire spread) via the touchpad once inside the actual world in PS4 Edition, results in cheats being turned on once converted to Bedrock and trophies unable to be earned anymore
EDIT After doing a few more worlds to test it on, I honestly don't know what causes cheat to be turned on in completely survival worlds with no cheats in PS4 edition.
Some factors that may be causing this issue:
- Biome size
- World size
- Amplified
- World settings that don't turn on cheats such as fire spread
- World settings once inside the world accessed via the touchpad (again, such as fire spread)
Don't have enough time to test what causing it exactly since I have exams in a few hours but those are some likely causes.
Tried transferring two (one amplified with large biomes, one default. Both with large world size) of my completely survival worlds with absolutely no cheats from PS4 Edition and both resulted in cheats being turned on and trophies unable to be earned.
After doing some testing by creating new completely survival worlds, I think it has to do something with turning on game rules such as fire spread in-game (with the little testing I did it seems that changing them in the world saves menu doesn't have the same affect).
Turning the game rules back to "default" (that the game would set if untouched in world settings) in PS4 edition before transferring them over to Bedrock still results in cheats being activated and no trophies being available to earn.
In conclusion, it seems that tinkering in anyway (off or back on) with game rules that don't get rid of trophies (such as fire spread) via the touchpad once inside the actual world in PS4 Edition, results in cheats being turned on once converted to Bedrock and trophies unable to be earned anymore
EDIT After doing a few more worlds to test it on, I honestly don't know what causes cheat to be turned on in completely survival worlds with no cheats in PS4 edition.
Some factors that I think may be causing this issue from the few worlds I tried creating and then transferring over:
- Biome size
- World size
- Amplified
- World settings that don't turn on cheats such as fire spread
- World settings once inside the world accessed via the touchpad (again, such as fire spread)
Don't have enough time to test what causing it exactly since I have exams in a few hours but those are some likely causes.
Tried transferring two (one amplified with large biomes, one default. Both with large world size) of my completely survival worlds with absolutely no cheats from PS4 Edition and both resulted in cheats being turned on and trophies unable to be earned.
After doing some testing by creating new completely survival worlds, I think it has to do something with turning on game rules such as fire spread in-game (with the little testing I did it seems that changing them in the world saves menu doesn't have the same affect).
Turning the game rules back to "default" (that the game would set if untouched in world settings) in PS4 edition before transferring them over to Bedrock still results in cheats being activated and no trophies being available to earn.
In conclusion, it seems that tinkering in anyway (off or back on) with game rules that don't get rid of trophies (such as fire spread) via the touchpad once inside the actual world in PS4 Edition, results in cheats being turned on once converted to Bedrock and trophies unable to be earned anymore
EDIT After doing a few more worlds to test it on, I honestly don't know what causes cheat to be turned on in completely survival worlds with no cheats
inPS4 edition.Some factors that I think may be causing this issue from the few worlds I tried creating and then transferring over:
- Biome size
- World size
- Amplified
- World settings that don't turn on cheats such as fire spread
- World settings once inside the world accessed via the touchpad (again, such as fire spread)
Don't have enough time to test what causing it exactly since I have exams in a few hours but those are some likely causes.
Tried transferring two (one amplified with large biomes, one default. Both with large world size) of my completely survival worlds with absolutely no cheats from PS4 Edition and both resulted in cheats being turned on and trophies unable to be earned.
After doing some testing by creating new completely survival worlds, I think it has to do something with turning on game rules such as fire spread in-game (with the little testing I did it seems that changing them in the world saves menu doesn't have the same affect).
Turning the game rules back to "default" (that the game would set if untouched in world settings) in PS4 edition before transferring them over to Bedrock still results in cheats being activated and no trophies being available to earn.
In conclusion, it seems that tinkering in anyway (off or back on) with game rules that don't get rid of trophies (such as fire spread) via the touchpad once inside the actual world in PS4 Edition, results in cheats being turned on once converted to Bedrock and trophies unable to be earned anymore
EDIT After doing a few more worlds to test it on, I honestly don't know what causes cheat to be turned on in completely survival worlds with no cheats that are converted from PS4 edition.
Some factors that I think may be causing this issue from the few worlds I tried creating and then transferring over:
- Biome size
- World size
- Amplified
- World settings that don't turn on cheats such as fire spread
- World settings once inside the world accessed via the touchpad (again, such as fire spread)
Don't have enough time to test what causing it exactly since I have exams in a few hours but those are some likely causes.
Tried transferring two (one amplified with large biomes, one default. Both with large world size) of my completely survival worlds with absolutely no cheats from PS4 Edition and both resulted in cheats being turned on and trophies unable to be earned.
After doing some testing by creating new completely survival worlds, I think it has to do something with turning on game rules such as fire spread in-game (with the little testing I did it seems that changing them in the world saves menu doesn't have the same affect).
Turning the game rules back to "default" (that the game would set if untouched in world settings) in PS4 edition before transferring them over to Bedrock still results in cheats being activated and no trophies being available to earn.
In conclusion, it seems that tinkering in anyway (off or back on) with game rules that don't get rid of trophies (such as fire spread) via the touchpad once inside the actual world in PS4 Edition, results in cheats being turned on once converted to Bedrock and trophies unable to be earned anymore
EDIT After doing a few more worlds to test it on, I honestly don't know what causes cheat to be turned on in completely survival worlds with no cheats and trophies being able to be earned that are converted from PS4 edition.
Some factors that I think may be causing this issue from the few worlds I tried creating and then transferring over:
- Biome size
- World size
- Amplified
- World settings that don't turn on cheats such as fire spread
- World settings once inside the world accessed via the touchpad (again, such as fire spread)
Don't have enough time to test what causing it exactly since I have exams in a few hours but those are some likely causes from the different worlds that I was creating and then transferring.
Tried transferring two (one amplified with large biomes, one default. Both with large world size) of my completely survival worlds with absolutely no cheats from PS4 Edition and both resulted in cheats being turned on and trophies unable to be earned.
After doing some testing by creating new completely survival worlds, I think it has to do something with turning on game rules such as fire spread in-game (with the little testing I did it seems that changing them in the world saves menu doesn't have the same affect).
Turning the game rules back to "default" (that the game would set if untouched in world settings) in PS4 edition before transferring them over to Bedrock still results in cheats being activated and no trophies being available to earn.
In conclusion, it seems that tinkering in anyway (off or back on) with game rules that don't get rid of trophies (such as fire spread) via the touchpad once inside the actual world in PS4 Edition, results in cheats being turned on once converted to Bedrock and trophies unable to be earned anymore
EDIT After doing a few more worlds to test it on, I honestly don't know what causes cheat to be turned on in completely survival worlds with no cheats and trophies being able to be earned that are converted from PS4 edition.
Some factors that I think may be causing this issue from the few worlds I tried creating and then transferring over:
- Biome size
- World size
- Amplified
- World settings that don't turn on cheats such as fire spread
- World settings once inside the world accessed via the touchpad (again, such as fire spread)
Don't have enough time to test what causing it exactly since I have exams in a few hours but those are some likely causes from the different worlds that I was creating and then transferring.
EDIT 2 I was able to transfer over my worlds successfully without getting cheats turned on in Bedrock by setting my world settings to "default",as in, the world settings the game would have turned on or off if you create a new world without tinkering with anything. Such as: PvP on, fire spread on and tnt explosiones on, also turned back on autosave.
I'm not sure which one causes cheats to be turned on once it's transferred over to Bedrock but it's one or multiple world settings that causes this it seems, such as:
- PvP
- Fire Spread
- TnT explosions
- Autosave
Tried transferring two (one amplified with large biomes, one default. Both with large world size) of my completely survival worlds with absolutely no cheats from PS4 Edition and both resulted in cheats being turned on and trophies unable to be earned.
After doing some testing by creating new completely survival worlds, I think it has to do something with turning on game rules such as fire spread in-game (with the little testing I did it seems that changing them in the world saves menu doesn't have the same affect).
Turning the game rules back to "default" (that the game would set if untouched in world settings) in PS4 edition before transferring them over to Bedrock still results in cheats being activated and no trophies being available to earn.
In conclusion, it seems that tinkering in anyway (off or back on) with game rules that don't get rid of trophies (such as fire spread) via the touchpad once inside the actual world in PS4 Edition, results in cheats being turned on once converted to Bedrock and trophies unable to be earned anymore
EDIT After doing a few more worlds to test it on, I honestly don't know what causes cheat to be turned on in completely survival worlds with no cheats and trophies being able to be earned that are converted from PS4 edition.
Some factors that I think may be causing this issue from the few worlds I tried creating and then transferring over:
- Biome size
- World size
- Amplified
- World settings that don't turn on cheats such as fire spread
- World settings once inside the world accessed via the touchpad (again, such as fire spread)
Don't have enough time to test what causing it exactly since I have exams in a few hours but those are some likely causes from the different worlds that I was creating and then transferring.
EDIT 2 I was able to transfer over my worlds successfully without getting cheats turned on in Bedrock by setting my world settings to "default"
,as in,the world settings the game would have turned on or off if you create a new world without tinkering with anything. Such as: PvP on, fire spread on and tnt explosiones on, also turned back on autosave.I'm not sure which one causes cheats to be turned on once it's transferred over to Bedrock but it's one or multiple world settings that causes this it seems, such as:
- PvP
- Fire Spread
- TnT explosions
- Autosave
Tried transferring two (one amplified with large biomes, one default. Both with large world size) of my completely survival worlds with absolutely no cheats from PS4 Edition and both resulted in cheats being turned on and trophies unable to be earned.
After doing some testing by creating new completely survival worlds, I think it has to do something with turning on game rules such as fire spread in-game (with the little testing I did it seems that changing them in the world saves menu doesn't have the same affect).
Turning the game rules back to "default" (that the game would set if untouched in world settings) in PS4 edition before transferring them over to Bedrock still results in cheats being activated and no trophies being available to earn.
In conclusion, it seems that tinkering in anyway (off or back on) with game rules that don't get rid of trophies (such as fire spread) via the touchpad once inside the actual world in PS4 Edition, results in cheats being turned on once converted to Bedrock and trophies unable to be earned anymore
EDIT After doing a few more worlds to test it on, I honestly don't know what causes cheat to be turned on in completely survival worlds with no cheats and trophies being able to be earned that are converted from PS4 edition.
Some factors that I think may be causing this issue from the few worlds I tried creating and then transferring over:
Biome sizeWorld sizeAmplifiedWorld settings that don't turn on cheats such as fire spreadWorld settings once inside the world accessed via the touchpad (again, such as fire spread)
Don't have enough time to test what causing it exactly since I have exams in a few hours but those are some likely causes from the different worlds that I was creating and then transferring.EDIT 2 I was able to transfer over my worlds successfully without getting cheats turned on in Bedrock by setting my world settings to "default" in PS4 Edition first, and by "default" I mean the world settings the game would have turned on or off if you create a new world without tinkering with anything. Such as: PvP on, fire spread on and tnt explosiones on, also turned back on autosave.
I'm not sure which one causes cheats to be turned on once it's transferred over to Bedrock but it's one or multiple world settings that causes this it seems, such as:
- PvP
- Fire Spread
- TnT explosions
- Autosave
Tried transferring two (one amplified with large biomes, one default. Both with large world size) of my completely survival worlds with absolutely no cheats from PS4 Edition and both resulted in cheats being turned on and trophies unable to be earned.
After doing some testing by creating new completely survival worlds, I think it has to do something with turning on game rules such as fire spread in-game (with the little testing I did it seems that changing them in the world saves menu doesn't have the same affect).
Turning the game rules back to "default" (that the game would set if untouched in world settings) in PS4 edition before transferring them over to Bedrock still results in cheats being activated and no trophies being available to earn.
In conclusion, it seems that tinkering in anyway (off or back on) with game rules that don't get rid of trophies (such as fire spread) via the touchpad once inside the actual world in PS4 Edition, results in cheats being turned on once converted to Bedrock and trophies unable to be earned anymore
EDIT After doing a few more worlds to test it on, I honestly don't know what causes cheat to be turned on in completely survival worlds with no cheats and trophies being able to be earned that are converted from PS4 edition.
Some factors that I think may be causing this issue from the few worlds I tried creating and then transferring over:
Biome sizeWorld sizeAmplifiedWorld settings that don't turn on cheats such as fire spreadWorld settings once inside the world accessed via the touchpad (again, such as fire spread)
Don't have enough time to test what causing it exactly since I have exams in a few hours but those are some likely causes from the different worlds that I was creating and then transferring.EDIT 2 I was able to transfer over my worlds successfully without getting cheats turned on in Bedrock by setting my world settings to "default" in PS4 Edition first, and by "default" I mean the world settings the game would have turned on or off if you create a new world without tinkering with anything. Such as: PvP on, fire spread on and tnt explosiones on, also turned back on autosave.
I'm not sure which one causes cheats to be turned on once it's transferred over to Bedrock but it's one or multiple world settings that causes this it seems, such as:
- PvP
- Fire Spread
- T
nT explosions- Autosave
Tried transferring two (one amplified with large biomes, one default. Both with large world size) of my completely survival worlds with absolutely no cheats from PS4 Edition and both resulted in cheats being turned on and trophies unable to be earned.
After doing some testing by creating new completely survival worlds, I think it has to do something with turning on game rules such as fire spread in-game (with the little testing I did it seems that changing them in the world saves menu doesn't have the same affect).
Turning the game rules back to "default" (that the game would set if untouched in world settings) in PS4 edition before transferring them over to Bedrock still results in cheats being activated and no trophies being available to earn.
In conclusion, it seems that tinkering in anyway (off or back on) with game rules that don't get rid of trophies (such as fire spread) via the touchpad once inside the actual world in PS4 Edition, results in cheats being turned on once converted to Bedrock and trophies unable to be earned anymore
EDIT After doing a few more worlds to test it on, I honestly don't know what causes cheat to be turned on in completely survival worlds with no cheats and trophies being able to be earned that are converted from PS4 edition.
Some factors that I think may be causing this issue from the few worlds I tried creating and then transferring over:
Biome sizeWorld sizeAmplifiedWorld settings that don't turn on cheats such as fire spreadWorld settings once inside the world accessed via the touchpad (again, such as fire spread)
Don't have enough time to test what causing it exactly since I have exams in a few hours but those are some likely causes from the different worlds that I was creating and then transferring.EDIT 2 I was able to transfer over my worlds successfully without getting cheats turned on in Bedrock by setting my world settings to "default" in PS4 Edition first, and by "default" I mean the world settings the game would have turned on or off if you create a new world without tinkering with anything. Such as: PvP on, fire spread on and tnt explosiones on, also turned back on autosave.
I'm not sure which one causes cheats to be turned on once it's transferred over to Bedrock but it's one or multiple world settings that causes this it seems, such as:
- PvP
- Fire Spread
- TNT explosions
- Autosave
As for how to try to reproduce this bug, I would say to start off by making a survival world with no cheats in PS4 Edition and turning off these 4 world settings, PvP, Fire Spread, TNT explosiones and Autosave, and then converting over the world.
Try different combinations or one by one to see which one is causing cheats to be turned on in survival worlds once converted to Bedrock from worlds with no cheats in PS4 Edition
Tried transferring two (one amplified with large biomes, one default. Both with large world size) of my completely survival worlds with absolutely no cheats from PS4 Edition and both resulted in cheats being turned on and trophies unable to be earned.
After doing some testing by creating new completely survival worlds, I think it has to do something with turning on game rules such as fire spread in-game (with the little testing I did it seems that changing them in the world saves menu doesn't have the same affect).
Turning the game rules back to "default" (that the game would set if untouched in world settings) in PS4 edition before transferring them over to Bedrock still results in cheats being activated and no trophies being available to earn.
In conclusion, it seems that tinkering in anyway (off or back on) with game rules that don't get rid of trophies (such as fire spread) via the touchpad once inside the actual world in PS4 Edition, results in cheats being turned on once converted to Bedrock and trophies unable to be earned anymore
EDIT After doing a few more worlds to test it on, I honestly don't know what causes cheat to be turned on in completely survival worlds with no cheats and trophies being able to be earned that are converted from PS4 edition.
Some factors that I think may be causing this issue from the few worlds I tried creating and then transferring over:
Biome sizeWorld sizeAmplifiedWorld settings that don't turn on cheats such as fire spreadWorld settings once inside the world accessed via the touchpad (again, such as fire spread)
Don't have enough time to test what causing it exactly since I have exams in a few hours but those are some likely causes from the different worlds that I was creating and then transferring.EDIT 2 I was able to transfer over my worlds successfully without getting cheats turned on in Bedrock by setting my world settings to "default" in PS4 Edition first, and by "default" I mean the world settings the game would have turned on or off if you create a new world without tinkering with anything. Such as: PvP on, fire spread on and tnt explosiones on, also turned back on autosave.
I'm not sure which one causes cheats to be turned on once it's transferred over to Bedrock but it's one or multiple world settings that causes this it seems, such as:
- PvP
- Fire Spread
- TNT explosions
- Autosave
As for how to try to reproduce this bug, I would say to start off by making a survival world with no cheats in PS4 Edition and turning off these 4 world settings, PvP, Fire Spread, TNT explosiones and Autosave, and then converting over the world.
Try different combinations or one by one to see which one is causing cheats to be turned on in survival worlds once converted to Bedrock from worlds with no cheats in PS4 Edition
Tried transferring two (one amplified with large biomes, one default. Both with large world size) of my completely survival worlds with absolutely no cheats from PS4 Edition and both resulted in cheats being turned on and trophies unable to be earned.
EDIT 2 I was able to transfer over my worlds successfully without getting cheats turned on in Bedrock by setting my world settings to "default" in PS4 Edition first, and by "default" I mean the world settings the game would have turned on or off if you create a new world without tinkering with anything. Such as: PvP on, fire spread on and tnt explosiones on, also turned back on autosave.
I'm not sure which one causes cheats to be turned on once it's transferred over to Bedrock but it's one or multiple world settings that causes this it seems, such as:
- PvP
- Fire Spread
- TNT explosions
- Autosave
As for how to try to reproduce this bug, I would say to start off by making a survival world with no cheats in PS4 Edition and turning off these 4 world settings, PvP, Fire Spread, TNT explosiones and Autosave, and then converting over the world.
Try different combinations or one by one to see which one is causing cheats to be turned on in survival worlds once converted to Bedrock from worlds with no cheats in PS4 Edition
I have a fully explored world from legacy console edition (about 2544x2544) in which I haven't been outside that area awaiting 1.18 and having completely new chunks generate outside that area.
There seems to be an issue where subchunks are only created up to a circular area (red circle in the map below) of 2440 in old chunks, leaving an area of void visible from y 0 to -64 in the rest of my old chunks where they failed to generate (outside the red circle in the map I attached)
New chunks (y= 320 to -64) are generated correctly outside of my 2544x2544 legacy console edition area (white area around the map)
Teleporting to 0, y, 0 and walking below bedrock shows that subchunks generate below y=0 correctly until you reach to about the red circle represented in the map below.
I have a fully explored world from legacy console edition (about 2544x2544) in which I haven't been outside that area awaiting 1.18 and having completely new chunks generate outside that area.
There seems to be an issue where subchunks are only created up to a circular area (red circle in the map below) of 2440 in old chunks, leaving an area of void visible from y 0 to -64 in the rest of my old chunks where they failed to generate (outside the red circle in the map I attached)
New chunks (y= 320 to -64) are generated correctly outside of my 2544x2544 legacy console edition area (white area around the map)
Teleporting to 0, y, 0 and walking below bedrock shows that subchunks generate below y=0 correctly until you reach to about the red circle represented in the map below.
Currently uploading a copy of my world so you can check it yourselves, as well as a clip walking from 0 to 2500ish to show the issue. Will add links as soon as they´re up.
I have a fully explored world from legacy console edition (about 2544x2544) in which I haven't been outside that area awaiting 1.18 and having completely new chunks generate outside that area.
There seems to be an issue where subchunks are only created up to a circular area (red circle in the map below) of 2440 in old chunks, leaving an area of void visible from y 0 to -64 in the rest of my old chunks where they failed to generate (outside the red circle in the map I attached)
New chunks (y= 320 to -64) are generated correctly outside of my 2544x2544 legacy console edition area (white area around the map)
Teleporting to
0, y, 0andwalking below bedrockshows that subchunks generate below y=0 correctly until you reach to about the red circle represented in the map below.
Currently uploading a copy of my world so you can check it yourselves, as well as a clip walking from 0 to 2500ish to show the issue. Will add links as soon as they´re up.
I have a fully explored world from legacy console edition (about 2544x2544) in which I haven't been outside that area awaiting 1.18 and having completely new chunks generate outside that area.
There seems to be an issue where subchunks are only created up to a circular area (red circle in the map below) of 2440 in old chunks, leaving an area of void visible from y 0 to -64 in the rest of my old chunks where they failed to generate (outside the red circle in the map I attached)
New chunks (y= 320 to -64) are generated correctly outside of my 2544x2544 legacy console edition area (white area around the map)
Teleporting to around 2544 in any direction and going below bedrock will allow you to see the issue.
Also teleporting to 0, y, 0 and walking below bedrock shows that subchunks generate below y=0 correctly until you reach to about the red circle represented in the map below.
Currently uploading a copy of my world so you can check it yourselves, as well as a clip walking from 0 to 2500ish to show the issue. Will add links as soon as they´re up.
I have a fully explored world from legacy console edition (about 2544x2544) in which I haven't been outside that area awaiting 1.18 and having completely new chunks generate outside that area.
There seems to be an issue where subchunks are only created up to a circular area (red circle in the map below) of 2440 in old chunks, leaving an area of void visible from y 0 to -64 in the rest of my old chunks where they failed to generate (outside the red circle in the map I attached)
New chunks (y= 320 to -64) are generated correctly outside of my 2544x2544 legacy console edition area (white area around the map)
Teleporting to around 2544 in any direction and going below bedrock will allow you to see the issue.
Also teleporting to 0, y, 0 and walking below bedrock shows that subchunks generate below y=0 correctly until you reach to about the red circle represented in the map below.
Currently uploading a copy of my world so you can check it yourselves, as well as a clip walking from 0 to 2500ish to show the issue. Will add links as soon as they´re up.
World download: https://1drv.ms/u/s!ArG7tvnDDwS4mn7haTnCQktqA4Mz?e=rrPCGy
I have a fully explored world from legacy console edition (about 2544x2544) in which I haven't been outside that area awaiting 1.18 and having completely new chunks generate outside that area.
There seems to be an issue where subchunks are only created up to a circular area (red circle in the map below) of 2440 in old chunks, leaving an area of void visible from y 0 to -64 in the rest of my old chunks where they failed to generate (outside the red circle in the map I attached)
New chunks (y= 320 to -64) are generated correctly outside of my 2544x2544 legacy console edition area (white area around the map)
Teleporting to around 2544 in any direction and going below bedrock will allow you to see the issue.
Also teleporting to 0, y, 0 and walking below bedrock shows that subchunks generate below y=0 correctly until you reach to about the red circle represented in the map below.
Currently uploading a copy of my world so you can check it yourselves, as well as a clip walking from 0 to 2500ish to show the issue. Will add links as soon as they´re up.
World download: https://1drv.ms/u/s!ArG7tvnDDwS4mn7haTnCQktqA4Mz?e=rrPCGy
I have a fully explored world from legacy console edition (about 2544x2544) in which I haven't been outside that area awaiting 1.18 and having completely new chunks generate outside that area.
There seems to be an issue where subchunks are only created up to a circular area (red circle in the map below) of 2440 in old chunks, leaving an area of void visible from y 0 to -64 in the rest of my old chunks where they failed to generate (outside the red circle in the map I attached)
New chunks (y= 320 to -64) are generated correctly outside of my 2544x2544 legacy console edition area (white area around the map)
Teleporting to around 2544 in any direction and going below bedrock will allow you to see the issue.
Also teleporting to 0, y, 0 and walking below bedrock shows that subchunks generate below y=0 correctly until you reach to about the red circle represented in the map below.
Currently uploading a copy of my world so you can check it yourselves, as well as a clip walking from 0 to 2500ish to show the issue. Will add links as soon as they´re up.
World download: https://1drv.ms/u/s!ArG7tvnDDwS4mn7haTnCQktqA4Mz?e=rrPCGy
I have a fully explored world from legacy console edition (about 2544x2544) in which I haven't been outside that area awaiting 1.18 and having completely new chunks generate outside that area.
There seems to be an issue where subchunks are only created up to a circular area (red circle in the map below) of 2440 in old chunks, leaving an area of void visible from y 0 to -64 in the rest of my old chunks where they failed to generate (outside the red circle in the map I attached)
New chunks (y= 320 to -64) are generated correctly outside of my 2544x2544 legacy console edition area (white area around the map)
Teleporting to around 2544 in any direction and going below bedrock will allow you to see the issue.
Also teleporting to 0, y, 0 and walking below bedrock shows that subchunks generate below y=0 correctly until you reach to about the red circle represented in the map below.
Currently uploading a copy of my world so you can check it yourselves, as well as a clip walking from 0 to 2500ish to show the issue. Will add links as soon as they´re up.
World download: https://1drv.ms/u/s!ArG7tvnDDwS4mn7haTnCQktqA4Mz?e=rrPCGy
I have a fully explored world from legacy console edition (about 2544x2544) in which I haven't been outside that area awaiting 1.18 and having completely new chunks generate outside that area.
There seems to be an issue where subchunks are only created up to a circular area (red circle in the map below) of 2440 in old chunks, leaving an area of void visible from y 0 to -64 in the rest of my old chunks where they failed to generate (outside the red circle in the map I attached)
New chunks (y= 320 to -64) are generated correctly outside of my 2544x2544 legacy console edition area (white area around the map)
Teleporting to around 2544 in any direction and going below bedrock will allow you to see the issue.
Also teleporting to 0, y, 0 and walking below bedrock shows that subchunks generate below y=0 correctly until you reach to about the red circle represented in the map below.
Currently uploading a copy of my world so you can check it yourselves, as well as a clip walking from 0 to 2500ish to show the issue. Will add links as soon as they´re up.
World download (from 1.17 releases, upgradable to 1.18 beta): https://1drv.ms/u/s!ArG7tvnDDwS4mn7haTnCQktqA4Mz?e=rrPCGy
I have a fully explored world from legacy console edition (about 2544x2544) in which I haven't been outside that area awaiting 1.18 and having completely new chunks generate outside that area.
There seems to be an issue where subchunks are only created up to a circular area (red circle in the map below) of 2440 in old chunks, leaving an area of void visible from y 0 to -64 in the rest of my old chunks where they failed to generate (outside the red circle in the map I attached)
New chunks (y= 320 to -64) are generated correctly outside of my 2544x2544 legacy console edition area (white area around the map)
Teleporting to around 2544 in any direction and going below bedrock will allow you to see the issue.
Also teleporting to 0, y, 0 and walking below bedrock shows that subchunks generate below y=0 correctly until you reach to about the red circle represented in the map below.
Currently uploading a copy of my world so you can check it yourselves, as well as a clip walking from 0 to 2500ish to show the issue. Will add links as soon as they´re up.
World download (from 1.17 releases, upgradable to 1.18 beta): https://1drv.ms/u/s!ArG7tvnDDwS4mn7haTnCQktqA4Mz?e=rrPCGy
Going from 0, y, 0 all the way to 2544 (new chunks) and showing how subchunks fail to generate after a certain distance (2450~): https://youtu.be/H2S2uGQDv_g
I have a fully explored world from legacy console edition (about 2544x2544) in which I haven't been outside that area awaiting 1.18 and having completely new chunks generate outside that area.
There seems to be an issue where subchunks are only created up to a circular area (red circle in the map below) of 2440 in old chunks, leaving an area of void visible from y 0 to -64 in the rest of my old chunks where they failed to generate (outside the red circle in the map I attached)
New chunks (y= 320 to -64) are generated correctly outside of my 2544x2544 legacy console edition area (white area around the map)
Teleporting to around 2544 in any direction and going below bedrock will allow you to see the issue.
Also teleporting to 0, y, 0 and walking below bedrock shows that subchunks generate below y=0 correctly until you reach to about the red circle represented in the map below.
Currently uploading a copy of my world so you can check it yourselves, as well as a clip walking from 0 to 2500ish to show the issue. Will add links as soon as they´re up.
World download (from 1.17 releases, upgradable to 1.18 beta): https://1drv.ms/u/s!ArG7tvnDDwS4mn7haTnCQktqA4Mz?e=rrPCGy
Going from 0, y, 0 all the way to 2544 (new chunks) and showing how subchunks fail to generate after a certain distance (2450~): https://youtu.be/H2S2uGQDv_g
I have a fully explored world from legacy console edition (about 2544x2544) in which I haven't been outside that area awaiting 1.18 and having completely new chunks generate outside that area.
There seems to be an issue where subchunks are only created up to a circular area (red circle in the map below) of 2440 in old chunks, leaving an area of void visible from y 0 to -64 in the rest of my old chunks where they failed to generate (outside the red circle in the map I attached)
New chunks (y= 320 to -64) are generated correctly outside of my 2544x2544 legacy console edition area (white area around the map)
Teleporting to around 2544 in any direction and going below bedrock will allow you to see the issue.
Also teleporting to 0, y, 0 and walking below bedrock shows that subchunks generate below y=0 correctly until you reach to about the red circle represented in the map below.
Currently uploading a copy of my world so you can check it yourselves, as well as a clip walking from 0 to 2500ish to show the issue. Will add links as soon as they´re up.
World download (from 1.17 releases, upgradable to 1.18 beta): https://1drv.ms/u/s!ArG7tvnDDwS4mn7haTnCQktqA4Mz?e=rrPCGy
Going from 0, y, 0 all the way to 2544 (new chunks) and showing how subchunks fail to generate after a certain distance (2450~): https://youtu.be/H2S2uGQDv_g (watch at 2x speed)
After taking into consideration that something with villages is the cause of the crashes, I decided to test it.
Doing some quick tests in the seed "Chepo", I can confirm it has something to do with villages. I was able to generate a new world, actually load into the world, close the world and reopen it right at spawn (I didn't move from spawn).
I was able to reopen the world without problems but after going east about 200 blocks to the nearest village, I decided to look for fetching tables before closing and trying to reopen the world, found no fetching tables and it still resulted in a crash.
It's not the fetching table causing the crash but it has to do something with being in/near a village
After doing some more tests with the same seed/village. I have come to the conclusion that the grindstone is the one causing the crashes.
Generated the same seed, broke the cauldrons, closed the world and trying to reopen the same world resulted in a crash.
Tested the other work blocks that villagers use as well.
Doing the same thing but breaking the only grindstone in the village resulted in a success. I was able to reopen the world after breaking it.
Been studying for exams since those are coming up but I realized that what you said is right after some testing though I didn't have time to respond right away.
Some random events that occur in the village when in loading at different speeds does seem to be the cause of some of the crashes but I still have to say that the some of the workplace blocks have to something about it or are a different cause of crashes.
Like I said during in the conclusion of some of my tests,
"After doing some more tests with the same seed/village. I have come to the conclusion that the grindstone is the one causing the crashes.
Generated the same seed, broke the cauldrons, closed the world and trying to reopen the same world resulted in a crash.
Tested the other work blocks that villagers use as well.
Doing the same thing but breaking the only grindstone in the village resulted in a success. I was able to reopen the world after breaking it."
The only way I was able to reopen the world was by breaking the grindstone beforehand.
I don't have another legacy console edition world to test on. I would have to create a new one and go around exploring as well as buying a realm subscription to be able to move the world over to W10 and test in the 1.18 beta.
Also, I don't know if this same issue would appear in a world originally created in Bedrock (non-legacy console edition) as I don't have a world as big as my legacy console edition world to test it on.
Can confirm that bug is fixed in the 1.18.0.22 Beta, at least my world (the one attached) doesn't have this issue anymore.