Amulet-Map-Editor
Amulet-Map-Editor copied to clipboard
[Bug Report] Some of the Sealanterns and Concrete Powder Are NOT Converted
Bug Report
Some of the Sealanterns and Concrete Powder Are NOT Being Converted.
Current Behaviour:
When converting worlds from bedrock edition to java edition, some of the sealanterns and concrete powder are not being converted.
Expected behavior:
All the sealanterns and concrete powder should be converted.
Steps To Reproduce:
- Choose a bedrock world which contains many sealanterns / concrete powder
- Convert it into a java world
- Open the java world and some of the sealanterns / concrete powder disappear.
- Check the console log you can see warning info for sealanterns / concrete powder.
Environment:
- OS: Windows 11
- Minecraft Platform: Bedrock to Java
- Minecraft Version: BE1.19.22 to JE1.19
- Amulet Version: 0.10.1, 0.10.0, 0.9.*
Screenshots
Worlds
It seems that this issue only happens after the world was updated from 1.18.12(bedrock) to a higher version as sea lanterns placed recently has no such issue.
I am aware of this issue and know what is causing it. I am working on a project to extract data from Bedrock edition so that issues like this should not happen again.
This is fixed in the translator and will be included in the next build.
This is fixed in the translator and will be included in the next build.
I've tried the new build, but there are still sealanterns missing. 😢
Hmm okay. Is this after converting again?
Hmm okay. Is this after converting again?
Yes, but this time I converted to an 1.18.2 world instead of 1.19 world. The console log still produced a warning that it could not find a translation information.
Is this still an issue in the newest version of Amulet?
Yes, there're still sealanterns missing, and I still find warnings in the console log.
This is the latest copy of the BE world. I hope this would help. The missing sealanterns can be found near (-221,70,514) after being converted to JE world. Bedrock World
I see what the issue is. Will get this fixed.
This should be fixed in the next build