Tags
Creators
Details
Beta-0.2
Compatibility
Changes
UPDATE TO Beta 0.2.6 (aka Beta0.2)
Main changes
- Made JsonArgumentType
- Added ListComparator for command list identification
- Added JSON Parse option to ConfigElem
- Added config methods to get available ids for the command
- Added use of command to append to lists
Minor changes
- edited the gitignore to ignore html files
- edited README.md
- edited config file writer (hoped a better JSON String parsing)
- added folder creating log to the backup method
- added Fabric API dependence, instead of just crashing the game
- moved gamerules to the PLAYERS category
TODO:
[✓] Player death Mixins altering drop ✓ Check if mod activated ✓ Check if keepInventory (vanilla) is true ✓ Check if death correspond to the wanted list ✓ Check if doVanishingCurse is activated ✓ Apply or not Curse of Vanishing if activated [ ] Usage of config file ✓ Creating config file on read if missing ✓ Creating config file backup and a new one if error on read • Make backup name organised by number • Allow restoring backup from number • Make restoring able to backup actual config file ✓ Reading file on server startup and generate config data ✓ Change config data to save gamerules change before stop ✓ Save config on server stop [ ] Use commands to alter config data ✓ Create the command x Create CDIActionArgumentType for first argument (no) ✓ Create CDIListArgumentType for command list selection ✓ Create JsonArgumentType for command editing config data ✓ Use command to add conditions • Implement config more data edition from command ✓ Add command alias for easier use [ ] Pure development (post-beta?) • Add documentations to (as much as possible) all classes [ ] And a few tests, as well...
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:64koG3e4:PvRs82Fg"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:64koG3e4:PvRs82Fg"
}

