- 1,297 views, 0 today
- 26
- 24
- 10
296
Many people wish that a favorite pack of theirs’ was made for Bedrock Edition rather than just Java. I’m going to show you how to port a pack using StackPack made by Fishstacks as an example.
NOTE: If you plan on publishing this pack or sharing it with anyone you should make sure to ask for permission and credit them as required. If it is just a personal pack still make sure to credit them anyways.
THIS TUTORIAL IS STILL VALID & WORKING, HOWEVER YOU CAN SKIP SOME STEPS OF THIS BY USING THIS CONVERTER: (https://modifiedcommand.github.io/ConvertJavaTextureToBedrock/) *does not currently work for 1.20 textures, but can still be used by changing the Java pack.mcmeta to be for 1.19
Step 1:
Download the Java pack and unzip to view:
Step 2:
You will need to create a folder for your bedrock pack in Minecraft/games/com.mojang/development_resource_packs.
Step 3:
Now we need to create subfolders for the textures to go in. Inside your newly created folder create another folder called ”textures”. Inside textures you will create more subfolders like “blocks”, “items”, “entity”, “models”, “environment”, “misc”, “map”, “colormap”, “painting”, “particle”, “ui”, and “gui”.
NOTE: The file structure can be looked at in the Vanilla Resource Pack In addition, not all of these folders are used in every pack. You do not need to include folders that are not needed for your pack.
Step 4:
Now we need to create a manifest.json for our pack to show up in game. This is like the pack.mcmeta for Java edition.
A quick json editor that works on most devices is (https://jsoneditoronline.org/). Replace the name with whatever the pack is called and the description with a short thing about the pack or the author. You will also need to go to (https://www.uuidgenerator.net/) and replace both of the UUID’s in mine to a new one.
NOTE: Download my manifest here: https://www.mediafire.com/file/hvzikoee5ikfchs/manifest.json/file
Now you will need to save it as a .json file with the name “manifest” and put it into the bedrock pack folder next to your “textures” folder.
Step 5:
You should now go to the Java pack and copy the pack.png to your bedrock pack folder like you did with the manifest.json. It needs to be renamed to pack_icon.png.
Now if you reload Minecraft it will show up in game under settings/global resources. It won’t do anything yet as the textures have not been added yet.
NOTE: Without a pack_icon.png it will still work but will show as a missing texture.
Step 6:
You will need to copy all the textures from the Java edition pack folder “block” into the Bedrock edition pack folder “blocks” that you created in the last tutorial. You should also do the same for the folder “item” and pasting those textures into the “items” folder. This will also have to be done for all other folders.
Step 7:
Although all those textures have been copied, a large amount of them still won’t show up in game due to Bedrock’s different file naming system for textures. For example, “spruce_door_top” on Java edition is “door_spruce_upper” on Bedrock edition.
This means you will have to rename the textures to their bedrock names based on the Vanilla resource pack. If you used the converter, you will only need to do this on 1.20 textures or for any that did not convert properly. I recommend keeping a list to refer to while testing.
Thanks for using this tutorial! There are more coming in the future.
NOTE: If you plan on publishing this pack or sharing it with anyone you should make sure to ask for permission and credit them as required. If it is just a personal pack still make sure to credit them anyways.
THIS TUTORIAL IS STILL VALID & WORKING, HOWEVER YOU CAN SKIP SOME STEPS OF THIS BY USING THIS CONVERTER: (https://modifiedcommand.github.io/ConvertJavaTextureToBedrock/) *does not currently work for 1.20 textures, but can still be used by changing the Java pack.mcmeta to be for 1.19
Step 1:
Download the Java pack and unzip to view:
Step 2:
You will need to create a folder for your bedrock pack in Minecraft/games/com.mojang/development_resource_packs.
Step 3:
Now we need to create subfolders for the textures to go in. Inside your newly created folder create another folder called ”textures”. Inside textures you will create more subfolders like “blocks”, “items”, “entity”, “models”, “environment”, “misc”, “map”, “colormap”, “painting”, “particle”, “ui”, and “gui”.
NOTE: The file structure can be looked at in the Vanilla Resource Pack In addition, not all of these folders are used in every pack. You do not need to include folders that are not needed for your pack.
Step 4:
Now we need to create a manifest.json for our pack to show up in game. This is like the pack.mcmeta for Java edition.
A quick json editor that works on most devices is (https://jsoneditoronline.org/). Replace the name with whatever the pack is called and the description with a short thing about the pack or the author. You will also need to go to (https://www.uuidgenerator.net/) and replace both of the UUID’s in mine to a new one.
NOTE: Download my manifest here: https://www.mediafire.com/file/hvzikoee5ikfchs/manifest.json/file
Now you will need to save it as a .json file with the name “manifest” and put it into the bedrock pack folder next to your “textures” folder.
Step 5:
You should now go to the Java pack and copy the pack.png to your bedrock pack folder like you did with the manifest.json. It needs to be renamed to pack_icon.png.
Now if you reload Minecraft it will show up in game under settings/global resources. It won’t do anything yet as the textures have not been added yet.
NOTE: Without a pack_icon.png it will still work but will show as a missing texture.
Step 6:
You will need to copy all the textures from the Java edition pack folder “block” into the Bedrock edition pack folder “blocks” that you created in the last tutorial. You should also do the same for the folder “item” and pasting those textures into the “items” folder. This will also have to be done for all other folders.
Step 7:
Although all those textures have been copied, a large amount of them still won’t show up in game due to Bedrock’s different file naming system for textures. For example, “spruce_door_top” on Java edition is “door_spruce_upper” on Bedrock edition.
This means you will have to rename the textures to their bedrock names based on the Vanilla resource pack. If you used the converter, you will only need to do this on 1.20 textures or for any that did not convert properly. I recommend keeping a list to refer to while testing.
Thanks for using this tutorial! There are more coming in the future.
Credit | @Fishstacks |
Tags |
1 Update Logs
Update #1 : by IronDuke 08/17/2023 1:13:39 pmAug 17th, 2023
Added steps 6 & 7
Cleaned up instructions
Added link to a converter
Cleaned up instructions
Added link to a converter
5684224
6
Create an account or sign in to comment.
And, how does .mcpack work?
I'm looking to port one of my packs, and it works ingame (yay) but I would still need to upload it in some form. (I'm currently looking into modrinth because of multiple versions, so it probably won't be uploaded soon)
I may ask some questions later when I actually try to port something. =]