All versions
1.0.0
Release
Memory SMP 1.0.03 months ago 41
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Paper
Purpur
Changes
Changelog
All notable changes for RG_Memory_SMP are documented in this file.
1.0.0
Initial public release.
Added
- Core memory system with configurable starting, minimum, and maximum values
- Memory loss handling for normal, PvP, lava/fire, and void deaths
- Memory rewards for player, Warden, and Wither kills
- Five memory tiers with escalating gameplay restrictions
- Automatic elimination flow when a player reaches
0memory - Rejoin blocking for eliminated players
- Bound player head drops on elimination
- Custom items:
Memory Crystal,Echo Fragment,Forgotten Relic, andUnban Head - Configurable custom item names, lore, glow, materials, and custom model data
- Echo Fragment and Forgotten Relic crafting recipes
- Player-bound relic crafting when using an eliminated player's head
- GUI-based item and recipe viewer with
/memory items - GUI-based relic flow for creating player-specific Unban Heads
- Revival ritual system with bossbar, action bar, particles, sounds, and success/failure handling
- Ritual failure logic for head break, nearby explosions, ritual owner death, and server restart
- Configurable restored memory on successful revival
- Join handling for revived players, including post-revival teleport
- Gradient nametags with memory display and optional team formatting
- Configurable team system and admin team assignment commands
- Automatic recipe discovery on player join
- Structure chest loot injection for Memory Crystals
- Admin commands for setting memory, giving items, forcing OUT state, unbanning, viewing player info, assigning teams, and reloading config
- Persistent per-player YAML data storage for memory, OUT state, team, revival status, and ritual spawn location
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:oOk5dbdV:Xl2wcGPs"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:oOk5dbdV:Xl2wcGPs"
}

