Tags
Creators
Details
Licensed LGPL-3.0-only
Published 5 years ago
Updated yesterday
All versions
5.0.0-Beta.5+mc26.3-fabric
Beta
5.0.0-Beta.5 for Fabric 26.3yesterday 1,157
Compatibility
Minecraft: Java Edition
26.3
Platform
Fabric
Supported environments
Client-side
Client and server
Required content
Any compatible version
Changes
This release includes major breaking changes for all other mods that interact with this mod!
- Added multiloader support for NeoForge
- Added support for 26.3
- The mod ID has been changed to
female_gender_mod - Player configurations have been largely rewritten, and now save in a more structured format
- Armor rendering now uses vanilla rendering methods where possible
- Please report any visual issues that may be caused by this change, especially in regard to armor trims and modded armors!
- Syncing with the connected server (if supported) has also been heavily changed:
- The mod now requires both sides to support a hello packet in the configuration phase, and will not attempt to sync unless both sides support the same sync protocol version
- The play phase sync packet IDs have been changed to
female_gender_mod:{client,server}bound/sync - Sync packets between the client and server will now omit irrelevant data where possible
- Fixed an issue with default skins using the wrong texture path in the UV Editor screen
- Fix rendering of upside down entities in UIs (for players like Dinnerbone, Grumm, or any other names mods may tweak to be upside down)
- Updated/added translations for Russian, Turkish, Spanish, Chinese, LOLCAT, and various English locales (Canadian, British, Australian, and Upside Down)
- Holiday themes have been removed
Supplementary resources
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:bcOsQHnC:OQqLMTt6"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:bcOsQHnC:OQqLMTt6"
}

