Tags
Creators
Details
Beta-0.3
Compatibility
Changes
UPDATE TO Beta 0.3.4 (aka Beta0.3)
Main changes
- Added last command arguments
- Made command globally working (can still have bugs)
- Set some command outputs to be displayed to all OP members
Minor changes
- customized the JSON parsed to ensure proper lines and spacings
- renamed the command alias from "cdi" to "cki" ("keep")
- removed useless methods from a few classes, added some
- discovered a not-so-dumb way to parse JSON (I'm proud)
- changed a Mixin invoke method
- Guess what? The version changed as well
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 • Add a "dimension" condition : Config file versioning (add version tag) : Rename "held_item" to "weapon" [ ] Use commands to alter config data ✓ Create the command ✓ Create CDIListArgumentType for command list selection ✓ Create JsonArgumentType for command editing config data ✓ Create command sub-functions: ✓ Use command to toggle auto backup when game starts ✓ Use command to add conditions ✓ Use command to edit conditions ✓ Use command to consult conditions ✓ Use command to remove condition ✓ Use command to toggle condition (t->f;f->t) ✓ Use command to reload config file ✓ Use command to save config file ✓ Use command to backup config file ✓ Use command to list available backups ✓ Use command to restore backup ✓ Add command alias for easier use • Correct the OP broadcast to display as the right user -> might wish to use a "command_called" boolean param [ ] Pure development (post-beta?) • Add documentations to (as much as possible) all classes [ ] And a few tests, as well...
• = working on it ✓ = done : = v1+ [ ] = not finished
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:jTM6lt5D"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:64koG3e4:jTM6lt5D"
}

