Frequently Asked Questions

General Questions

What Minecraft versions work with this?

The tool should work with Java Edition resource packs for custom music discs. It handles both older model override formats and the newer item definition format from 1.21.4+.

What's the difference between V1 and V2 API?

V1 is the standard Custom item API format that most servers use. V2 is specifically for Geyser's experimental Custom item API V2, you'll probably only need this if your server is using custom item components that specifically require V2 format. If you're not sure, stick with V1.

Is this tool free to use?

Yep, completely free. Everything runs in your browser, no account needed. Your audio files stay on your device and don't get uploaded anywhere.

Why should I upload my previous .mcpack?

When you upload the old .mcpack, the tool keeps the same UUIDs. This means the new pack can overwrite the old one in players' storage instead of being saved as a separate duplicate. Without this, players end up with multiple versions of your pack taking up space. They'll still download the update either way, but keeping UUIDs prevents storage bloat.

Can I use this for commercial purposes?

Yeah, you can use this tool and its output however you want, including on commercial servers. Just make sure you have the rights to the audio content you're converting.

Troubleshooting

The converter says "No music disc models found"

This usually means your pack doesn't have the item definition files in the right place. Check that your pack includes JSON files for custom music discs. The exact location depends on which format you're using, but they should be in your pack somewhere.

Bedrock players aren't getting the pack

Try checking these:

• Make sure the .mcpack is in /plugins/geyser-(version)/packs/
• Geyser needs to be reloaded or restarted after you add the pack
• Players need to reconnect after the pack is added
• Look for any errors in the server console about pack loading

The pack downloads but there's no sound

A few things to check:

• The mapping JSON needs to be in /plugins/geyser-(version)/custom_mappings/
• Your audio files in the Java pack should be valid OGG Vorbis format
• Check that your sounds.json properly references the audio files
• Look in the Geyser console for errors related to custom mappings

The console shows audio analysis errors

The tool tries to analyze OGG files to show you technical info. If that fails for a file, the conversion still continues. The audio gets included in the pack without the detailed metadata. This shouldn't affect whether it works or not.

Textures are missing in Bedrock

The converter copies textures from your Java pack if they're there. Make sure your source pack includes texture files in assets/minecraft/textures/item/. If they're not in the Java pack, they won't be in the output either.

Players keep getting the full pack download

Players will always download pack updates. But if UUIDs change between versions, Bedrock treats it as a brand new pack and keeps both the old and new. Always upload your previous .mcpack when updating so the new version overwrites instead of duplicating.

Can I convert older packs?

Yeah, the tool should work with both the old model override system and the newer 1.21.4+ item definition format. If your pack uses the old format, the converter should still handle it.

Technical Stuff

Do I need to convert my audio files?

Nope. From testing, Bedrock seems pretty flexible about OGG Vorbis specs like sample rate, bitrate, mono vs stereo. The tool just displays that info for reference but doesn't modify the audio.

How does UUID preservation work?

When you upload a previous .mcpack, the tool extracts the two UUIDs from its manifest. These get reused in the new pack with just the version number bumped up. This tells Bedrock "hey, this is an update to that pack you already have" so it overwrites the cached version instead of saving both.

What happens to my files during conversion?

Your .zip gets processed in your browser using JavaScript. The server only gets a list of filenames, which it uses to generate conversion instructions. All the actual file reading and pack building happens locally on your device.