1.0.1-REOBF
Compatibility
Changes
This version added the offline function to echesttools, now you can use all arguments in echesttools to all players to have ever connected to your server instead of just the ones online. This was made by reading and modifying player data directly into the world's folder instead of relying on paper's tools.
For the moment, the offlines options are unaviable for inventorytools and inventoryclear, i have to work on a centralized data manager for that so it isn't as chaotic as it is rn, see you next update ;D
Btw, from now on, you have two different jar files, the 1.0.1 and 1.0.1-reobf, try both and see which one works the best, for me, reobf worked perfectly so you should have no problem running it (all this has to do with some libraries i had to add to be able to actually touch minecraft's files without dying each new version).
Full Changelog: https://github.com/NahumNaranjo/nahum-Inventory-stuff/commits/1.0.1
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:zUhgS2WH:sfGcs9XX"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:zUhgS2WH:sfGcs9XX"
}

