How to Install Jenny Mod on Minecraft Java Edition and Bedrock / MCPE

Choose a launcher and an isolated installation

Prism Launcher, CurseForge App, Modrinth App and ATLauncher organize content into instances or profiles. The important choice is the instance you actually launch, not which launcher has the most prominent download button. Create a Java 1.12.2 installation for the legacy archives, add its matching Forge loader, and open that profile's directory when installing the JAR. A third-party launcher's built-in catalog and a manually supplied local file are separate sources. Finding no matching catalog entry does not change where the selected instance reads its mods folder.

Prepare worlds, install once and remove cleanly

Close Minecraft before copying a world backup so the save files are no longer changing. Keep that backup outside the active profile. For Java, place one intact approved JAR in mods and launch Forge before adding other mods. For Bedrock, import the companion behavior/resource pair or the separate Dweller bundle, then activate its components in a new world. To remove Java content, move the archive out of that profile's mods folder while the game is closed. To remove Bedrock content, deactivate the packs in the world's settings. Worlds containing mod-specific entities or items should be preserved with their original content as a separate backup before you continue without it.

Choose the next guide by the task in front of you

Use the Java PC tutorial when Minecraft opens normally but you still need Forge and a modded instance. Use the mods-folder tutorial when Forge is already installed and the remaining problem is locating the directory. Use the Android/Bedrock tutorial when your files end in .mcpack or .mcaddon and Minecraft handles the import. These are different operations: copying a Java file into a directory is not the same as importing a Bedrock pack into the game.

Before changing a working installation, decide which world you want to use. A fresh Creative world is useful for finding items and separating setup issues from an existing world's settings. Keep your survival save separate until the selected content loads. Java instance directories can hold independent mods, config and saves folders; Bedrock activation belongs to the specific world. Installing a pack in Minecraft's storage does not automatically activate it in every saved world.

After the first launch, check the edition-specific result. Java should identify Forge and list the selected mod; only then open a world and search the inventory. Bedrock should show the required packs in the world's active lists; only then enter the world. If Minecraft itself cannot open, solve that earlier stage first. If it opens but the content is absent, move to Mod Not Showing or Bedrock Pack Not Working rather than repeating every download step.

Complete setup in a predictable order

Begin with an installed, working copy of Minecraft. Open the edition you intend to use before adding content, then close it for file changes. This separates account, launcher and base-game problems from mod installation. A download of the character archive is not a solution for an account sign-in error or a game that cannot start without mods. Once the base game works, choose one of the edition routes below and stay with that route through its final check.

On Java, choose the game branch first and the loader second. The legacy files here point to Minecraft 1.12.2 and Forge. Create a separate profile, establish its game directory and start the loader without added content. When that reaches the title screen, place one selected intact JAR into its mods folder. Return to the same launcher entry and confirm the internal mod identity in the Mods list. If you installed Forge into a different launcher, locate the equivalent instance settings instead of assuming that every launcher shares one directory.

On Bedrock, start with the file pairing. Download both companion MCPACK files or choose the separate Dweller MCADDON. Open the intact files with Minecraft, wait for each result and then edit the intended world's pack settings. Importing is a storage step; activating is a world step. The resource pack supplies presentation while the behavior pack supplies its data definitions. If the game reports a missing resource dependency, resolve that named pair before adding unrelated packs or changing world experiments.

For the first world launch, Creative mode makes inventory discovery easier and keeps the installation separate from survival progress. Use the archive-specific character and item names, then move to the focused guide if one item is absent. When the content works, keep the instance name or world selection clear so you can return to the same setup. If a later addition breaks it, remove that addition first. A clean first setup provides a useful reference without asking you to maintain screenshots or testing records.

Move from the installation hub to the detailed task

Choose Java PC for the complete desktop sequence, Mods Folder for path discovery and Android/Bedrock for importing packs. The desktop tutorial covers the official launcher's profile selection as well as the intact archive. The folder guide provides operating-system paths and explains why a custom game directory overrides them. The mobile guide explains the two companion imports, the separate Dweller bundle and world activation. You can use the same edition decision on Windows, where the computer may have both game editions installed.

After installation, use the next guide that matches what you see. If the mod list is empty, check the active profile and file location. If Bedrock lists a missing dependency, check its matching resource pack. If the game closes, use the exception in the latest launch's log. If only one character is missing, compare the roster. This lets you keep successful steps and repair only the stage that failed.

Prepare file access before changing game content

Choose a location your normal user account can read and write. The game directory stores changing files such as configuration, logs and saves, so it belongs in an accessible user location rather than an operating-system program folder. If a launcher manages instances, use its folder control to reach that location. This also avoids confusing the launcher's application files with the files used by a particular game installation.

Before copying a world, exit to the menu and close the game so the save is no longer changing. Copy the complete world folder to a separate backup location. Keep that backup outside the active saves directory and outside mods. For Bedrock, use a copied world for pack changes when available through the game's world-management controls. A backup is most useful when it remains separate from the content you are about to replace.

On a shared computer, check which operating-system account and launcher instance you are using. Another account's default Minecraft path can be different. On Linux, an isolated launcher can also have its own permitted storage location. Use the path shown by the selected instance instead of changing folder permissions across the entire machine. On mobile, wait until a downloaded cloud file is available locally before sending it to Minecraft through the file manager.

Then perform only the operation needed by your edition. Java copies an intact archive into the selected instance; Bedrock imports a package and activates it in a world. After the change, start the same selected installation or world. If it fails, keep your backup untouched and use the guide matching that stage. You can return to the previous setup without deleting all launcher data, clearing mobile application storage or moving unrelated worlds.

Before you begin

• Open Minecraft and record the edition and exact version.
• Create a backup of saved worlds.
• Verify the download source, extension and hash.
• Remove unrelated mods from the test profile.
• Keep security software enabled.

Java PC path

Install the matching Forge build, create or select its launcher profile, run it once, then place the intact compatible .jar in that profile's mods folder. Launch the Forge profile and confirm the entry appears in the Mods list.

Bedrock/mobile path

Open the compatible .mcaddon or .mcpack with Minecraft, wait for the import result, create a test world and activate every required behavior/resource pack. Check the add-on instructions for experimental settings.

After installation

• Test in a new world before using an important save.
• Confirm the expected spawn method or items.
• Add other mods one at a time.
• Keep the original source and hash in your records.

Pick the correct setup path

Choose your next step

• Download files and check SHA-256
• Compare edition and device support
• Solve loading and pack problems

Frequently asked questions