We may need to ask you to share the world so that we can try and reproduce the issue. If there are conversion errors with blocks or other data we would like to hear about them. You can report these in the same way. Please read this carefully before downloading. Known limitations. Items are currently only supported within the same platform Java to Java or Bedrock to Bedrock Entities are not currently supported and should remain where they were If a chunk cannot be loaded it will appear red and cannot be modified There are some issues with the block translations and some blocks that have not been implemented yet.
It supports multiple selection boxes. It stores sub-chunks individually so memory is not wasted on empty sub-chunks. Amulet is currently just a 3D world editor and a converter but there is nothing stopping it from being more.
Behind the UI is a powerful but simple to use world editing system which enables editing multiple world formats interchangeably. In the past tool makers have had to handle the world logic on their own meaning that tools generally only worked on one platform. It is our hope that Amulet can become a hub. Amulet is written in Python 3 with a full API to modify world data.
Users can write python code to modify world data and do complex tasks that would not be possible any other way. Read before downloading. You can open more than one world in Amulet at once which will make it easier but is not required to copy between worlds. Amulet is able to import an export. We plan to add the.
Amulet is able to edit any version of Java from 1. Once the new version gets near to release we will start adding support for them. Amulet is able to convert between any two worlds that it is able to open. The supported versions are any version of Java from 1. Note that conversion can be within the same platform as well as between them. This means that you can convert a world to an older world version if you want to.
In the 3D edit sub-program chunks are loaded and displayed in a 3D editor. At the base and ceiling of the chunk is a square to help identify where the chunk boundaries are.
Blue squares are chunks that exist and may or may not contain blocks and other data. Black squares are chunks that do not yet exist. If you explore these chunks in game it will generate the chunk data and save it to disk. Next time you load it in Amulet it should be a blue square.
If you have deleted chunks in Amulet they will go back to the non existstant state and will be recreated next time you explore them in game. The final state is the red state.
You hopefully won't see this state but this is used if something went wrong when loading the chunk. This may be due to a bug in Amulet, a corrupted chunk or a newer version of the chunk that we do not yet support.
The console window will contain error messages for every chunk that failed to load with a traceback as to why. Amulet does have a plugin system so that users can write custom code that Amulet will run. In Amulet they are known as operations and can be found in the 3D editor sub-program in the operation tab. MCEdit filters are not directly compatible and will need to be rewritten to work with Amulet. These files cannot be directly opened by Amulet but if you change the extension back to.
Note that by default file extensions are hidden on Windows. In order to change them you will need to change the setting in file explorer to show them. In order to make the game recreate a chunk all the chunk data needs to be deleted which can only be done by deleting the whole chunk. With a bit of work a user could delete the blocks from part of the chunk and copy over blocks from another world to produce the desired result but this cannot be done automatically.
0コメント