Links
Tags
Creators
Details
2.0.0
Compatibility
Changes
This new major update completely alters the structure of the Naked and Afraid Plugin, adding support for a large range of versions and very important features.
Additions/Changes
- Added support for Minecraft versions 1.8-1.21.8 for all Paper/Spigot/Folia and Purpur server loaders.
- Added reflection for variables across all classes to avoid API-related errors and crashes.
- Added a new MaterialCompat class, which remaps items when called, avoiding API-related errors.
- Added new config.yml variables,
disable-totems, with a default boolean variable of true, and under thearmor-damagegroup,armor-slotandarmor-materialandinclude-offhand. - Added new Totem of Undying disabling logic, present inside the new TotemDisablerListener class, which disables the death-saving mechanic when turned on in the config.yml file.
- Updated ArmorDamageListener to account for new config variables, allowing for control over what type and armor slot the damage will be dealt on.
- Added a new TeleportHelperExtension class.
- Added new Main class inside the entrypoint module, which is responsible for choosing what module to enable during server startup.
- Changed main class in plugin.yml from
com.crimsonwarpedcraft.nakedandafraid.NakedAndAfraidtocom.crimsonwarpedcraft.nakedandafraid.entrypoint.Main. - Removed
api-versionline from plugin.yml. - Changed the Team Block material for all versions below 1.16 from the Lodestone block to the new default Beacon block.
- Updated
README.mdfile.
Bug Fixes
- A bug regarding players being invisible when the Tablist Hiding was enabled was fixed.
With that, the plugin is now almost closing in all obligatory features, but will still continued to be worked and developed on.
As always, stay alert for new versions, and have a fun time using the plugin!
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:6f8r8hV0:9KDdFzLZ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:6f8r8hV0:9KDdFzLZ"
}

