Tags
Creators
Details
Licensed ARR
Published 2 years ago
Updated 5 days ago
All versions
1.1.4
Release
Solo Craft: Reawakening 1.1.45 days ago 581
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Changes
Solo Leveling: ReAwakening (1.1.4)
Changelog
- Fixed Job Change kills being credited more than once, which could make the counter jump unexpectedly. Completion now waits for the whole active attempt, cleans up its mobs, and opens vessel selection after a short safe delay.
- Improved Job Change failure and retry handling so deaths, stale mobs, loot, and interrupted attempts cannot corrupt the next run or strand players at the return portal.
- Fixed procedural dungeon exit portals appearing only after backtracking. The exit now spawns immediately at a safe entrance-side location when the boss is defeated.
- Improved Clear Dungeon shadow navigation: shadows advance toward the dungeon objective, handle partial paths better, and recover instead of repeatedly running into walls.
- Improved Shadow Beru AI. Beru stays grounded for normal combat, uses flight for airborne targets and limited boss situations, escapes water/elevation problems, and uses the correct flight animations while airborne.
- Fixed missing Demon King's Castle permit pedestals. Boss completion repairs the pedestal immediately, and existing affected saves can self-repair it when the player approaches.
- Restored Daily Quest punishment before Job Change completion. Failed dailies send eligible players to the 120-second penalty zone until the Job Change quest is fully finished, while still respecting the soloPunishment gamerule.
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:YdsLXFph:FLuCf3M7"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:YdsLXFph:FLuCf3M7"
}

