Resolve the dependency behind missing behavior or textures
Open the affected world's Behavior Packs and Resource Packs screens and confirm that both are active there, not simply listed in global storage. If behavior exists but textures are missing, start with the resource entry and competing resource-pack order. If the whole add-on is inactive, start with the behavior entry and dependency messages. Do not add Dweller as a repair for the missing companion resource pack: Dweller uses different UUIDs and includes its own paired components. Fix the component named by Minecraft's message instead of importing every similarly named download into the same world.
Handle duplicate imports and archive errors
A duplicate-pack message concerns the pack UUID and version, not just the filename on your phone. Back up the world, inspect stored copies under Minecraft's Storage settings, and remove the obsolete duplicate before importing the intended pair again. A not-valid-zip message calls for checking download completion and the actual file extension. If a browser appended .zip to a known mcpack, restore the original extension only after confirming the file is the correct pack; renaming a JAR never converts it. After successful import, return to the world settings and activate both components. Resource reload keyboard shortcuts from Java are not a replacement for Bedrock pack activation.
Repair the specific import or world symptom
For a missing-dependency message, compare the dependency UUID with the installed resource pack rather than comparing only names. JennyModBeh expects the companion resource identity 8e430597-42b0-4075-a97c-917743c8fdd3. Import Jenny-texture.mcpack from the matching record and check that JennyModRes is active in the same world. The unrelated Dweller resource pack has a different identity, so importing it cannot satisfy that dependency.
For a duplicate-pack result, check whether the same UUID and version are already imported. Repeating an identical file may produce a duplicate message while the original remains available for activation. Open the world settings before deciding that the package is absent. If replacing an older import is necessary, back up affected worlds and remove only the intended pack from storage. Do not clear all Minecraft data. Editing UUIDs merely to bypass a duplicate message can break dependency matching and makes the edited file different from the listed hash.
For visible entities with missing textures, check resources and competing packs first. For no custom entity or item, check behavior activation and the selected bundle. For an import failure before either pack appears, inspect the extension and download completeness. A browser may have saved an HTML page or an extra ZIP wrapper. Return to the direct asset and verify its hash rather than repeatedly extracting and renaming files. If the current game reports an unsupported engine or content format, use the actual message and the pack's manifest fields; switching every experimental option on is not a substitute for resolving the stated cause.
Separate cached imports from the world configuration
Minecraft storage can contain a pack that no world currently uses. The world's active list can also refer to a pack you removed or replaced. These are different states. Open the affected world's settings and inspect which behavior and resource packs are active before clearing storage. If a duplicate import was the only message, the existing pack may simply need activation. If the world names a missing dependency, identify that exact dependency and import its matching file.
Use Settings and Storage only for the specific imported content you intend to replace. Menu labels can vary by platform and language, but the principle is the same: preserve worlds, remove the selected obsolete pack when necessary, and reimport the intact matching download. Do not delete every resource pack or clear application data as a first repair. Other saved worlds may rely on content that is unrelated to the current problem.
If the game reports a resource conflict, start with the companion pair alone in a new world. Another active resource pack can override presentation assets. If the pair works alone, reintroduce other packs gradually and inspect their order and overlapping content. An import-success notification does not resolve an override that occurs only when the world loads. If the behavior itself is absent, check the behavior active list rather than moving textures around manually.
For the separate Dweller bundle, use its own behavior/resource components and pa:jenny identity. Do not replace the companion resource file with Dweller or assume all Jenny-named entries form a single pack. After resolving the error, exit the world and reopen it with the intended components active. If a current Minecraft update rejects an older declaration, keep the actual error and manifest field in view instead of repeatedly renaming the archive. A changed extension does not update the pack's internal format.
Activate every included component
After importing, open the world's Behavior Packs and Resource Packs settings. Activate each component supplied by the add-on, then restart the test world before troubleshooting individual features.
Check manifest facts
- Jenny Dweller: linked behavior and resource packs
- Pack version: 0.0.1
- Minimum engine: 1.17.0
- The manifests specify a minimum version but no tested maximum version.
Resolve duplicate-pack errors
Remove or deactivate an older copy that uses the same pack UUID, restart Minecraft and import the intended package again. Duplicate identifiers can make Minecraft retain an older version or reject the import.
If import succeeds but nothing appears
- Create a new test world.
- Confirm both packs are active in world settings.
- Check the release's spawn or item instructions.
- Do not apply Java Forge steps to Bedrock.
- Back up a world before changing packs on an existing save.
Match the Bedrock result to the next check
| Result | Check | Action |
|---|---|---|
| Duplicate pack | Look for the existing identity in storage and the world lists. | Activate the intended existing pack before deciding that another import is needed. |
| Missing companion resources | Match the JennyModBeh dependency to the JennyModRes header UUID. | Import the matching resource file and activate both components in the same world. |
| Import succeeds but the world is unchanged | Compare active behavior and resources with a fresh world using that bundle. | Preserve a copy, correct the selected components and reopen the affected world. |
Choose your next step
Sources used for this guide
These primary references support the technical file, loader and package details on this page.
- GitHub: ZellRaihan/Jenny-Mod releasesgithub.com
- Microsoft Learn: Add-on pack manifest referencelearn.microsoft.com
- Microsoft Learn: Add-on development workflowlearn.microsoft.com
- Microsoft Learn: Latest platform version guidancelearn.microsoft.com
Frequently asked questions
Why are textures missing?+
The add-on's resource component may not be imported or active for the world.
Does a minimum engine version prove it works on every newer release?+
No. It states a lower engine boundary, not a tested maximum compatibility promise.
Will Dweller repair missing JennyModRes textures?+
No. Install and activate the paired JennyModRes resource pack; Dweller is another bundle.
What identifies a duplicate pack?+
Minecraft compares the manifest UUID and version rather than the phone’s filename.
Is a successful import the end of troubleshooting?+
Check both active world components next; storage and activation are separate states.
What should I preserve before clearing old packs?+
Back up worlds that use them before removing or replacing stored content.
Can changing UUIDs repair the companion dependency?+
Use the matching original pack first. JennyModBeh names the resource header identity supplied by JennyModRes, so a missing-dependency message calls for checking that resource file and its activation. Editing a UUID creates a modified package and can disconnect references that previously matched. It also changes the original file’s fingerprint. If you are installing as a player, reimport the intact approved pair and inspect the affected world’s active lists. Keep development edits in a separate project if you intentionally create a variant later. Do not use an unrelated Dweller component to fill the dependency: it has its own identity and belongs to a different bundle.
What should I compare if the pack works in a fresh world?+
Compare the affected world’s active behavior and resource lists with the fresh world. Look for the missing member of the pair, a different variant or another pack that overrides the same presentation. Preserve a copy of the existing world before changing its content. Then adjust one relevant pack selection and reopen that copy. The files can be imported on the device while different worlds activate different combinations, so reinstalling the application is not the first step. If you remove obsolete imported content through Storage, select only the intended pack and retain backups for worlds that use it. Keep the known intact downloads available for reimport.