Tags
Creators
Details
Licensed MIT
Published 4 years ago
Updated 4 days ago
All versions
3.8
Release
CrazyVouchers 3.82 years ago 78
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platforms
Folia
Paper
Purpur
Changes
Notice:
- Once 1.21.2 drops, NBT-API will be stripped from the plugin.
- This is your warning to migrate old vouchers players have and technically the second warning, I forgot to push this update.
- All old vouchers will stop working once NBT-API is removed!
- The migration for old configurations has been removed.
- If you need to migrate, use 3.7.4 as the migration works there.
Future Changes:
- MiniMessage Support
- There will be a migration from Legacy Color Codes -> MiniMessage
- Updates to configurations with materials, sounds, and how items work
- Internally, all materials, and trims will be handled internally, so need not worry about that.
- Sounds will have to be migrated manually, not much I can do about that.
- This change with sounds will allow custom sounds from resource packs.
- This is a step in removing a large chunk of deprecated, or otherwise outdated ways of doing things as Minecraft has changed a lot internally.
Additions:
- Added dupe protection for vouchers which is toggled false.
- A config option was also added to append a line to the lore.
Changes:
- Switched vouchers to use PersistantDataContainer which is much more performant, and achieves a similar goal.
- Previous vouchers will work until 1.21.2, so please migrate them.
- Allowed switching between file systems on
/crazyvouchers reload- There will not be a migration to switch between.
- Updated vital api
Fixes:
- Fixed an issue on Folia #73
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:EMORKQjj:9SwYYaZR"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:EMORKQjj:9SwYYaZR"
}

