- Support Custom Block (Ready for test and use)
- Fix shield
- Support custom gui and skip font. Example code for file to make it:
[ "\uE200":{ "skip": true }, "0xE201":{ "skip": true, "gui": [0, 6] }, "":{ "skip": false, "gui": [0, 16] } // if skip is not set and gui is set, then the font will skip and the gui will be executed ]
Please disable itemadder protection unzip
To run, simply:
./converter.sh MyResourcePack.zip
To run without settings prompts, use flags:
-w (true|false)whether or not to show the warning prompt-m (pack_to_merge.mcpack)filename of Bedrock Edition resource pack in the same diretory to merge with result of the conversion-a (attachable_material)material to use for attachables written by the script-b (block_material)material to use for blocks written by the script-f (https://somesite.com/fallback_pack.zip|null)URL of a Java Edition resource to use for fallback textures before the default pack-v (default_asset_version)version of Minecraft Java Edition for which to pull default assets
For example:
./converter.sh MyResourcePack.zip -w "false" -m "MyBedrock.mcpack" -a "entity_alphatest_one_sided" -b "alpha_test" -f "null" -v "1.18.2"
If you prepare 2D sprites for your 3D models, you can provide the converter with mappings for these sprites to be incorporated into item_texture.json and the exported Geyser mappings. To do so, simply include a file called sprites.json in the root of your Java resource pack. The format of this file is as follows:
{
"leather": [
{
"custom_model_data": 1,
"sprite": "textures/path/to/texture_in_bedrock_rp/texture1"
},
{
"custom_model_data": 2,
"sprite": "textures/path/to/texture_in_bedrock_rp/texture2"
}
],
"diamond_axe": [
{
"damage_predicate": 2,
"unbreakable": true,
"sprite": "textures/path/to/texture_in_bedrock_rp/texture3"
}
]
}When utilizing this feature, you should also use the merge feature to combine the converted pack with an existing Bedrock resource pack containing the specified sprite textures. If using the Github Actions based converter, simply provide a direct download URL of said Bedrock resource pack as done for the Java pack.
You may also run the converter through Github Actions in this repository by creating an issue with the Pack Conversion template. You are only required to enter the link to the Java pack, though the options described above may also be configured. Your pack will then be queued for conversion by Github Actions. After conversion is complete, the Github Actions bot will reply to your issue with a link to download your converted pack and associated mappings file. Included in the bundle is a behavior pack and addon to view the models in single player, as well as a configuration file containing the paths to the models converted from the Java resource pack and their corresponding identifiers in the Bedrock resource pack.
NOTICE: Due to MCPE-152191, any blocks that are larger than 1.9 blocks will not load. This is only relavent to those using the preview pack to display converted models in single player.
The script has been updated to handle parent models and 2D items. It will generate multiple sprite sheets for 3D models without repeating the inclusion of any given texture. 2D item textures will be copied over individually. Note that sprites for 3D items must be added manually.
Your script and resource pack zip file must be in the same directory. Ensure that this zip file is properly setup. It should not have a root directory. Your resource pack must also be formatted correctly, to vanilla specifications. By default, this script will download the default assets in order to generate texture atlases in cases in which you have utilized those. If you wish to use different default assets, you may specify this at the beginning. The default pack will then be downloaded after your specified assets, with your specified assets taking precedence. As long as you provide valid JSON, the script should output something you can use.
You may also specify an input bedrock pack to merge with the output assets produced by the converter. This should be in the same directory as the script and your input Java pack. Like the Java pack, ensure that it is compressed with no root folder. When prompted, type the file name of the input file, such as example_rp.mcpack. Merging of behavior packs is not currently supported.
The packs generated by this script can currently only be used in Bedrock Edition 1.16.210.59 and above. Please be sure to enable the experimental setting "Holiday Creator Features" on world generation. You'll probably also want to be in creative mode as that will be the only way to give yourself the blocks generated by the script. Here are the commands to obtain one of the items or place them in your head slot:
/give @p geysercmd:gmdl_xxxxxxx
/replaceitem entity @p slot.armor.head 0 geysercmd:gmdl_xxxxxxx
The xxxxxxx term corresponds to the short hash assigned to the model. These are written to config.json, which can be found in the target directory, along with packaged and non-packaged versions of the output assets. This will specify the corresponding item and nbt for each input predicate. The short hash is constructed by combining the predicate entry's item, custom model data, damage, and damaged predicates, taking the md5 hash of this string, and keeping only the first 7 characters. As a result, this hash value will remain the same across conversions.
Also note that this script requires:
- jq (1.6+)
- sponge
- imagemagick (6+)
- nodejs
- spritesheet-js
It will exit if you fail to meet these dependencies. While the ultimate intention here is to import these via Geyser, the script currently generates a behavior pack so that you may view your converted models in Bedrock Edition. It also generates a mappings file compliant with Geyser's custom item mappings system.
Should you have any complaints about getting this to run because you "only use windows", do note that I was able to run this perfectly fine on a Mac running Parallels to run Windows to run WSL to run Ubuntu 20. Therefore, I am sure it is perfectly possible for you to get this working, regardless of your OS. I will gladly take such criticism only if you are willing to help develop this into a proper cross platform program.
sudo apt-get install moreutils jq imagemagick unzip zip nodejs uuid-runtime
npm i -g spritesheet-jsbrew install moreutils jq imagemagick unzip zip nodejs uuid-runtime
npm i -g spritesheet-jssudo yum install moreutils jq imagemagick unzip zip nodejs uuid-runtime
npm i -g spritesheet-jssudo pacman -S moreutils jq imagemagick unzip zip nodejs uuid-runtime
npm i -g spritesheet-jsImpossible; consider WSL.
In general, packages on WSL seem to be a little wonky, and sometimes jq-1.5 will be installed, which will not work. To manually install jq-1.6 on WSL, at least for Ubuntu:
wget https://github.com/stedolan/jq/releases/download/jq-1.6/jq-linux64 && sudo chmod +x jq-linux64 && sudo mv jq-linux64 /usr/bin/jqIf you install spritesheet-js globally, but the script fails due to missing the dependency, ensure that the folder containing your global node modules is added to your path. If, after installing, which spritesheet-js returns no output, you may add global node modules to your path by:
echo "export PATH=$PATH:$(npm config --global get prefix)/bin" >> ~/.bashrc && source ~/.bashrc