All versions
0.1-alpha
Alpha
Mahou Isekai 0.1-alphalast month 35
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Changes
Version: Alpha 0.1 "The Awakening"
The first major functional update. The core mechanics have been completely rewritten, establishing a rock-solid backend foundation and introducing the central awakening system.
Awakening System & Mechanics
- Talent Roulette: Engineered a probability distribution system spanning 9 distinct tiers. Players are permanently assigned custom classes based on their rolled potential.
- Cinematic Ritual: Authored a 5-second aesthetic awakening sequence consisting of a rising soul-fire vortex, sequential Warden heartbeat acoustics, and a terminal non-lethal lightning visual strike.
- Mana Sync: Automated immediate integration to sync Minecraft experience levels directly into the maximum mana pool upon awakening.
Graphical User Interface (HUD)
- Dynamic Magic Overlay: Implemented a customizable client HUD that tracks the active spell, draws accurate item-stack renders dynamically from the registry IDs, and shifts border colors depending on the magic tier.
- Real-time Cooldowns: Programmed ticking visual cooldown clocks displayed directly over the HUD, combined with player level restriction locks.
Comprehensive Localization
- Multi-Language Manifests: Structured dual language catalogs (en_us.json and ru_ru.json), providing seamless translations for spells, system messages, and titles.
- Custom Titles: Adapted the highest rank specifically for English players as "The Chosen One".
Architecture & Network Synchronization (Backend)
- Network Pipeline: Fully implemented a robust server-to-client network pipeline via PacketHandler.
- State Persistence: Transferred critical player states (cooldowns, spell indexes, class keys) into server-managed NBT compounds via player.getPersistentData(), preventing data loss upon relog.
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:APP3ZLRB:lxCVWoAA"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:APP3ZLRB:lxCVWoAA"
}

