Jenny Mod Characters: Reference List, Variants & Verification Notes

This page is a reference for character names and visual variants associated with Jenny Mod material documented on JennyGamee. Character availability and behavior can differ between Java builds and community-made Bedrock/mobile adaptations, so names are not presented as universal package features.

Package context used on JennyGamee

The current Java package documented on JennyGamee is Jenny-Mod-Forge-1.12.2-v1.9.0.jar, recorded on the public Java release page. The Bedrock/MCPE release documented here contains Jenny-mod.mcpack, Jenny-texture.mcpack and jenny-dweller.mcaddon, recorded on the public MCPE release page.

Those release records verify the package identities, but JennyGamee has not yet completed a runtime roster test proving which of the character names below appear in each exact package. Character availability therefore remains package-specific unless directly demonstrated.

Character reference

Important: This is not a guarantee that all fourteen names appear in Jenny-Mod-Forge-1.12.2-v1.9.0.jar or in the three Bedrock assets currently documented on JennyGamee. A community port can use a different roster from a Java build.

Visual evidence in the JennyGamee archive

JennyGamee has retained images previously used to illustrate Jenny Mod characters. These images can support visual identification, but they do not by themselves prove a character’s exact spawn rules, combat statistics, voice lines or availability in a specific package.

Why character lists differ online

“Jenny Mod” is used online for more than one package or adaptation. A Java mod, a modified community build and a Bedrock add-on can use different character rosters. A name seen in a screenshot or on another site should not be treated as proof that the same character exists in your package.

How to verify a character in your build

1. Identify whether you are using Java or Bedrock/MCPE.
2. Record the exact filename: for example the current Java v1.9.0 jar or one of the three documented Bedrock assets.
3. Check the package’s own entity/spawn information or in-game creative inventory where applicable.
4. Capture the result with the game version and package name visible in your test record.
5. If a behavior cannot be reproduced in that exact build, keep the claim unverified.

Behavior and interaction claims

Detailed jobs, spawn locations, combat roles, voice support, affection systems and automatic village protection should not be treated as universal character traits without build-specific evidence. Use the Gameplay & Interactions guide for behavior and animation verification guidance.

Java vs Bedrock character availability

Do not assume that a character present in a Java build is present in a Bedrock community port, or vice versa. For the exact package records, see the Java / Forge guide and the Bedrock / mobile guide.

Models and appearance

For skins, models, visual examples and the current Jenny-texture.mcpack context, use the dedicated Models & Skins reference.

Related references

• Main Jenny Mod guide
• Java / PC / Forge package guide
• Bedrock / MCPE package guide
• Gameplay and animations
• Models and skins
• CurseForge source check

Reference policy

• Names are listed as names associated with Jenny-related material, not as a promise of universal availability.
• Spawn, combat, dialogue and progression claims require build-specific evidence.
• Bedrock/community packages are kept separate from Java.
• Where package-level testing is incomplete, the page says so rather than filling the gap with a generic claim.