Jenny Mod Bedrock Edition & MCPE Guide: Behavior Packs, Resource Packs & Add-ons

JennyModBeh and JennyModRes are linked by identity

The resource archive's header has that exact UUID. Their version arrays are [1,0,0] and minimum engine arrays are [1,13,0]. This is why you activate JennyModBeh in Behavior Packs and JennyModRes in Resource Packs for the same world. The file names shown by the browser differ from the labels displayed inside Minecraft. If the import message names JennyModBeh after you opened Jenny-mod.mcpack, you are seeing the expected manifest name rather than a different download.

Dweller uses a different bundle

Jenny Dweller's two manifests link resource UUID 401f57c9-74ff-4646-92ce-2a82c5d1f189 with behavior UUID 4bf56a8e-0344-4ce7-a6b7-f550778ff316. Both specify pack version 0.0.1 and minimum engine 1.17.0, and the entity definition uses pa:jenny. Its mcaddon delivers both components in one importable archive. That makes it a separate choice from the two companion mcpacks, not their missing third dependency. On Android, iOS and Windows Bedrock, the import step gets files into Minecraft; world activation selects where those files take effect. Make sure you edit the world you actually open after importing, particularly if you keep several copies of a save.

From import to an active world

The import notification means Minecraft processed a package; it does not mean that package is active in the world you are about to enter. Return to the world's settings and inspect both Behavior Packs and Resource Packs. The companion behavior pack expects the resource identity declared by its dependency. Two packs with similar display names but different UUIDs are not necessarily the matching pair. Use Jenny-mod.mcpack with Jenny-texture.mcpack from the same download records rather than combining random mirrors.

The behavior dependency names resource UUID 8e430597-42b0-4075-a97c-917743c8fdd3. That identity matches the companion resource pack's header. Dweller instead carries its own linked behavior and resource components and entity pa:jenny. Importing Dweller does not satisfy a missing JennyModRes dependency for the separate companion pack. Treat each bundle as its own world setup, especially while identifying an import error.

On Android, use the file manager's Open with or share action if tapping the download opens an archive viewer. On iPhone or iPad, the Files share sheet may offer Minecraft as the receiving application. If the game is not offered, check that the actual extension remains .mcpack or .mcaddon rather than .zip appended by a download service. Renaming an unrelated archive does not convert its contents. On Windows Bedrock, opening the association can start Minecraft's import, but copying files to a Java mods folder will never activate a Bedrock world pack.

Read the manifest as a set of linked fields

A pack manifest has a header describing the pack and modules describing its content type. The header UUID identifies the pack; a module has its own identity. A dependency can name another pack's header UUID and version. Keep those roles separate when diagnosing a mismatch. A player does not need to edit these JSON values to perform a normal import. The matching files already contain their identities, and changing them produces a modified package rather than the exact archive listed in the download registry.

JennyModBeh has header UUID 942b5fa8-4e20-47cf-b71a-43df28e01b5a and depends on resource UUID 8e430597-42b0-4075-a97c-917743c8fdd3. JennyModRes uses that resource header identity. Both declare pack version 1.0.0 and minimum engine 1.13.0. The minimum-engine field tells Minecraft about the version the pack was written for and relevant backward-compatibility handling. It is not a substitute for the current game's import result or a promise that every later change to the engine preserves the pack unchanged.

Dweller's header identities are different: behavior 4bf56a8e-0344-4ce7-a6b7-f550778ff316 and resource 401f57c9-74ff-4646-92ce-2a82c5d1f189. Its bundled packs declare version 0.0.1 and minimum engine 1.17.0. If a world expects the companion resource identity, these Dweller values will not match it. Choose one setup first and confirm its active components before mixing additional add-ons. This avoids mistaking two unrelated Jenny-named packs for interchangeable halves of a single installation.

After activation, discover content in Creative using the selected pack's own entries. Do not expect Java's Forge Mods screen, Java character roster or Java item namespace to appear in Bedrock. A Bedrock entity declaration and its resource presentation belong to that edition's pack system. If the world loads but only the appearance fails, use the resource troubleshooting route; if behavior is absent, check world activation and dependencies first.

Use world settings as the installation boundary

A downloaded pack, an imported pack and an active world pack are three distinct stages. The file manager handles the first transition by sending the intact download to Minecraft. Minecraft storage holds the imported package. The world settings select what the game actually uses when that save opens. Check the stage where the problem appears rather than repeating every stage. An import failure belongs to the archive or its declarations; a successful import followed by an unchanged world often belongs to activation or a conflicting pack.

For the companion pair, locate JennyModBeh under behavior and JennyModRes under resources in the intended world. The dependency links those two identities. For Dweller, use the components bundled in its own MCADDON. Keep a copied world for changes to an existing save and start with a single bundle while discovering content. If another world has different packs active, its behavior can differ even though the device has the same imported files.

Resource order matters when multiple packs define overlapping presentation. A pack can import successfully but have its textures replaced by another active resource. Behavior conflicts similarly require checking the active content rather than a phone's browser settings. Once the intended setup loads, keep that world's pack choice clear before adding more content. The detailed import guide and the Bedrock troubleshooting page cover the file-manager and conflict steps separately.

Recognize pack structure before editing files

The manifest identifies a pack, while the folders beside it hold the content described by that pack. Resource folders can contain models, textures, animations, render controllers and sounds. Behavior folders hold definitions such as entity JSON. The companion download divides those responsibilities between two MCPACK files. Keep the intact import files for ordinary installation; unpacking their individual folders is a development task rather than the normal player workflow.

If you inspect a manifest to understand a dependency message, read the header and the dependency separately. The header names the pack you are examining. The dependency names another required identity. Modules describe what kind of content the current pack contributes and can have their own UUIDs. For the companion pair, match the behavior dependency to the resource header, not to an arbitrary module UUID or a similar display name.

Changing a version number, UUID or minimum-engine value changes the package rather than updating Minecraft. Such an edited file also has a different fingerprint from the listed original. For a normal setup, use the unchanged approved files and resolve activation or pairing through the world settings. If you intentionally develop a modified pack later, keep that project separate from the original downloads and from worlds that already rely on their identities.

Bedrock file formats

A .mcaddon can bundle packs; a .mcpack normally represents an individual pack. Some downloads arrive as archives containing both. Do not try to import a Java .jar into Bedrock.

Typical setup

• Confirm the add-on supports your installed Bedrock version.
• Open the .mcaddon or .mcpack with Minecraft.
• Check that the import completes without errors.
• Activate required behavior and resource packs for a new test world.
• Enable experimental options only when documented.

Android and iPhone considerations

Mobile operating systems handle downloads and file associations differently. Use Minecraft's normal import flow and avoid third-party installers asking for unnecessary permissions.

Expected limitations

Java and Bedrock have different engines and modding APIs. A Bedrock recreation may not provide the same menus, logic or animations, even when screenshots and names look similar.

Read the companion and Dweller identities

JennyModBeh entity declarations

Choose your next step

• Download files and check SHA-256
• Choose the right installation route
• Compare edition and device support
• Solve loading and pack problems

Frequently asked questions