Jenny Mod Compatibility Matrix: Supported Devices, Operating Systems & Game Versions

Match the device to the edition it runs

Chromebooks vary: an Android Minecraft installation and a Linux Java installation are separate setups with different files. Console editions restrict ordinary direct file importing, so a desktop JAR is not a console download. Evaluate multiplayer worlds or Realm delivery under the platform's actual pack and content rules rather than assuming a phone import proves console compatibility. The practical first question is which edition starts on the device, followed by the exact game version and the package system it accepts.

Read engine declarations and server requirements

JennyModBeh and JennyModRes declare minimum engine 1.13.0; Jenny Dweller declares 1.17.0. These are manifest lower bounds, not a list of every newer Minecraft build that has been played successfully. Java archive names point to the 1.12.2 route, while modern remakes have their own loader and game requirements. For a Java server, client and server mod lists and supported versions must agree wherever the mod requires both sides. For Bedrock, activate the required behavior/resources on the hosting world. If you are joining someone else's server, its operator chooses the allowed content; a local file does not override that policy.

Check support in layers

Check the device first, edition second, game version third, loader or pack engine fourth, and the selected package last. This order prevents a fix for one layer from being mistaken for another. A phone running Bedrock cannot use a desktop Forge JAR through a filename change. A Windows computer running Bedrock is still on the Bedrock route even though the same computer may also have Java Edition. A Java profile running the correct game version still needs the appropriate loader to discover the archive.

Next check the environment in which the content will run. A local Creative world, a Realm, a dedicated server and a console world do not expose identical installation controls. Uploading or joining a world is not itself proof that its custom entities and resources will be supported in that environment. For a hosted server, check the host's loader support and the package's requirements. For Bedrock, check that both components remain attached to the world and that clients receive the required resources.

Finally check interactions with the rest of your content. Two packs can each import correctly yet compete over an entity definition or resource. Two Java archives can both target 1.12.2 yet declare the same mod ID, as these two variants do. Keep one selected Java archive per profile. If another mod or pack causes a problem, reproduce the issue with that addition removed before looking for a new Jenny download. Matching file format, game branch and identity is more useful than a broad claim that a file works on every device.

Handle Chromebook, console and hosted-world questions

Chromebook is a device category, not a Minecraft file format. If the device uses the Android edition, follow the Bedrock package route. If a supported Linux environment runs Java Edition, that is a separate desktop-style setup with its own launcher, runtime and instance directory. Do not move a Java archive into Android storage and expect Bedrock to load it. Hardware capability, school or device-management restrictions and the installed edition can all affect which route is available.

Xbox, PlayStation and Switch use console-managed content workflows. A phone tutorial that relies on a file manager and Open with Minecraft should not be presented as a universal console procedure. Start from the content and world-sharing options supported by the console and service you use. Avoid a download page promising a one-click console installer for the desktop JAR: it does not change the archive's code or the console's import controls.

For a hosted world, separate the host configuration from the joining player's files. A Bedrock world must carry its required behavior and resource components. A Java server must support the relevant loader and server content where required by the mod. Matching game version alone does not resolve a missing custom entity definition. If joining fails, read the server's stated requirements and mismatch message before changing a working single-player profile.

For content conflicts, return to one selected package or bundle and a new world or isolated instance. Add other content only after that setup loads. If the failure appears after adding one resource pack, inspect overlap on the resource side; if the loader names a duplicate ID, remove the conflicting archive. This keeps a device-support question from turning into an unrelated world or mod-conflict problem.

Check the boundary between a supported format and an available workflow

Edition compatibility and installation access are separate checks. A Bedrock device belongs to the same broad game family as another Bedrock device, but the operating system can expose different file associations, storage controls and world-sharing options. A phone can offer a file manager's Open with action while a console follows its own content-management workflow. Choose instructions for the actual device rather than assuming that the same extension guarantees identical installation controls.

The same distinction applies on desktop. A Windows computer can have Java Edition, Bedrock and multiple Java launchers at once. Each installation can use its own content location. A valid archive in the wrong location is still unavailable to the selected game. On macOS and Linux, the Java route uses the chosen launcher's runtime and instance directory; a Windows path copied literally does not identify that directory. Use the instance's own folder control wherever possible.

For multiplayer, ask which environment hosts the content. The host's game edition, server loader or active Bedrock world packs determine the setup other players join. Client presentation resources and server-side content have different jobs. A successful local single-player profile does not change a remote server's installed content. Match the host's stated configuration, keep a separate local profile when necessary and avoid changing an unrelated working installation just to join a different world.

If the file format and workflow match but a problem remains, move to the specific symptom guide. Version messages, missing resources and duplicate identities are narrower questions than device support. Solving that next layer keeps the compatibility decision clear and avoids labelling a whole platform unsupported because one profile or world was configured incorrectly.

The five-point compatibility check

• Device: desktop, mobile, Chromebook or console.
• Edition: Java Edition or Bedrock Edition.
• Game version: the complete number shown in Minecraft.
• Loader: Forge or another loader required by the Java build.
• File format: .jar for Java mods; .mcaddon/.mcpack for Bedrock add-ons.

Java compatibility

Java mods are version-sensitive. A build made for 1.12.2 should be launched with the matching game and Forge profile. Moving it into a newer mods folder does not convert it.

Bedrock compatibility

The inspected Jenny Dweller add-on contains linked behavior and resource packs at version 0.0.1 with minimum engine 1.17.0. Its manifest does not declare a maximum version, so a broad version range should not be treated as a verified test result.

Signs of a mismatch

• The file opens in an unrelated program.
• Forge reports an incompatible or missing dependency.
• The mod is absent from the Mods list.
• A Bedrock pack imports but cannot be activated.
• The game crashes before reaching the menu.

Device compatibility matrix

Choose your next step

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

Frequently asked questions