Jenny Mod Version Guide: Java Archive Versions, Fapcraft 1.1.0 & Bedrock Engine History

Read three different kinds of version number

For the Java downloads, 1.12.2 appears in the archive name as the game target. Fapcraft reports internal mod version 1.1.0; the file labelled v1.9.0 reports 1.8.0. Neither internal number tells you to launch Minecraft 1.8 or 1.1. The Bedrock pair instead uses pack version 1.0.0 and minimum engine 1.13.0. Dweller uses pack version 0.0.1 and minimum engine 1.17.0. Read the field names alongside their values before selecting a replacement. This prevents a newer-looking filename from being mistaken for a compatible upgrade.

Upgrade a profile without mixing releases

Create a separate game directory for the replacement Java archive, copy your backed-up world there only after the profile launches, and keep one archive for the shared mod ID. With Bedrock, compare the pack UUID and version because Minecraft uses those identities when importing an update. A second copy with the same UUID and no higher version may be treated as the existing pack rather than a distinct release. Modern projects such as Pleasure Horizons describe a Fabric remake with their own release records. Evaluate those as separate projects: choose their documented game version, loader and dependencies rather than treating them as renamed downloads of the legacy JAR.

Follow a release trail rather than a search label

Use the exact filename, internal identity and source release as a three-part reference. The word latest is relative to a project, and a mirror's upload date is not necessarily the original author's release date. A filename can be renamed without recompiling a mod. That is why the Java file labelled v1.9.0 is displayed here alongside its internal 1.8.0 value. Fapcraft's 1.1.0 belongs to a different naming sequence; comparing 1.1 and 1.8 numerically does not tell you which archive contains a particular character.

Choose by the feature or setup you need. For the additional Galath and Manglelie resources described in the character guide, start with Fapcraft. For a guide referring specifically to the SchnurriTV archive, match that file instead. Neither selection requires keeping both in the same mods directory. Both declare sexmod, so placing them together creates competing implementations of the same mod identity rather than a combined character expansion.

For Bedrock, pair version and UUID. JennyModBeh and JennyModRes are separate 1.0.0 packs connected by a dependency. Dweller is a separate 0.0.1 bundle. A small version number does not imply a smaller Minecraft version. Likewise, a minimum-engine declaration is a lower-bound field in a manifest, not a list of every subsequent Minecraft update on which the pack has been played. When the game rejects an import, read its specific version or dependency message before choosing another file.

Compare package contents before replacing a release

The inspected Java packages share a mod ID but differ in attribution, internal version and resources. Fapcraft contains 2,890 non-directory files; the SchnurriTV archive contains 2,666. Those counts include code, textures, sound and other assets. They are useful fingerprints of package structure, not a score of quality or a count of playable characters. Use the character comparison for a roster question and the file record for a byte-identity question. A larger archive can include additional media without changing the installation procedure.

The Bedrock companion packs differ in role as well as size. Jenny-mod.mcpack contains the behavior package and has 62 files; Jenny-texture.mcpack contains the resources and has 33. Their matching 1.0.0 versions do not make them duplicates. Importing only the larger file leaves the other role unfulfilled. The 40-file Dweller bundle carries a separate behavior/resource pairing, so its smaller size is not evidence that it is a compressed copy of the Java mod. Keep each comparison within the relevant package family.

When moving between releases, preserve the previous setup outside the active game directory. With Java, stop the game, copy the profile or back up its saves, replace the selected archive and reopen the same loader profile. Avoid carrying both variants into the new instance. With Bedrock, preserve a world copy before replacing an imported pack used by that world. Pack identity determines whether Minecraft treats an import as the same content; a filename alone does not.

If a tutorial names a historical version absent from the current file list, match the tutorial to its actual source instead of assuming a nearby number is equivalent. This page describes the inspected releases available from the named community source. New Minecraft versions, newly uploaded mirrors and project remakes belong to different release trails. Check their own identity, loader and dependency information before treating them as an upgrade path for an existing save.

Use the field name when comparing numbers

Write each version beside the thing it identifies. Minecraft 1.12.2 names the base game branch. Forge has a build for that branch. Java 8 identifies a runtime generation. The mod's internal 1.8.0 or 1.1.0 identifies content within the selected archive. Bedrock's pack 1.0.0 and minimum engine 1.13.0 describe different fields again. These numbers coexist; they are not expected to become identical.

For example, a launcher entry opening Minecraft 1.12.2 with Forge can legitimately display a mod version of 1.8.0. That is the inspected identity of the named-v1.9.0 archive. Changing the launcher to Minecraft 1.8 to make the numbers look alike would change the game branch. Similarly, Dweller pack 0.0.1 does not ask for Minecraft 0.0.1. Read the pack's minimum-engine field and the current game's actual import result instead.

For an update decision, compare the exact old and new artifact within the same project. Check identity, dependencies and the world or profile using it before replacement. If you switch projects, set up a new instance or world first. Keeping that boundary clear avoids a release-number comparison turning into an accidental migration of an existing save.

Choose an update by the content it replaces

Start with the content you already use. A Java world opened with one archive has a game version, loader, configuration and mod identity around that archive. A Bedrock world has a selected set of pack identities. Replacing a filename is therefore one part of an update, not the whole decision. Keep the previous world and package available separately before changing the selected content. That gives you a practical return point if the replacement changes resources used by the save.

For a Java roster change, compare the character resources rather than sorting filenames numerically. The Fapcraft archive adds the Galath and Manglelie resources described here and uses its own internal 1.1.0 label. The named-v1.9.0 archive identifies itself as 1.8.0. Both declare sexmod, so moving between them means choosing an implementation, not stacking a small expansion onto a larger base mod. Keep the comparison in separate profiles when you want access to both sets of resources.

For the companion Bedrock pair, compare behavior and resources together. Their 1.0.0 package versions accompany a dependency relationship; replacing one side with an unrelated pack changes that relationship. Dweller has its own two components and version 0.0.1. The minimum-engine fields provide another comparison, 1.13.0 for the companion pair and 1.17.0 for Dweller. Those fields describe engine requirements independently of the pack's own release numbering.

Use a project's release notes for an actual dated change history. The file comparison on this page identifies the inspected artifacts and the differences visible in them. If you choose a separate modern remake, follow that project's release trail and requirements from the beginning. Keep a functioning legacy profile intact while setting up the new project, and move an existing world only after considering the content it depends on.

Why version numbers are confusing

A label such as 1.12.2 usually describes the supported Minecraft version. It does not automatically identify a unique Jenny Mod release. Files promoted for 1.16.5, 1.18.2, 1.20 or 1.21 may be ports, recreations or renamed files.

Common version paths

• Java 1.12.2: commonly associated with the original mod format and a matching Forge installation.
• Newer Java releases: require a port built for the exact Minecraft and loader version.
• Bedrock and MCPE: use add-on formats and do not load a Java .jar file.
• Consoles: normal direct third-party file importing is restricted.

How we document a version

A useful version record should include Minecraft edition, exact supported game version, loader, file extension, source, size, SHA-256 hash, scan date and test status. A vague “latest” badge is not enough.

Choosing a version safely

• Prefer a traceable source over a mirror with a newer date.
• Do not install an executable presented as a normal Java mod.
• Match all three: game version, loader version and mod build.
• Keep a backup before testing an unofficial port.

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