Tags
Creators
Details
2.0
Compatibility
Changes
This changelog includes changelogs from 2.0 betas
2.0 Update !
This updates includes breaking changes, before updating, please save you config if you want to keep parts of it, then delete the 'RandomItemChallenge' folder.
Scenarios !
You can now handle multiple game scenarios without needing to change the config all the time.
There are 6 default scenarios available at the moment:
- allItems (uses all Items of the game)
- Base (previous default config)
- noweapon (No weapons)
- cheat (almost complete opposite, fun to play)
- rarities1 (explaination below)
- rarities2 (Current default, my personal favorite, with custom items)
Rarities
There is a new scenario type available: Rarities !
With this scenario, instaed of giving each player a fully random item, a random Rarity is chosen and each player gets an item from this category. Each one can have a different probability to appear.
If you want to test this, the default scenario rarities2 is available for you !
New drop types
To understand how to create such drops, look into the plugin description and look through the default configuration to understand.
"custom" drop type
Instead of only giving one type of item, you can now give a few different items, with different quantites, custom names, enchantments !
They are created inside of the custom_drops/custom folder.
"any" drop type
Instead of giving one specific item, you can create a list of items inside of the custom_drops/any folder, and one will be chosed amongst those for the drop.
Added new items from recent updates :
- Vault and trial keys from 1.21
- Resin clump and pale moss from 1.21.4
- Happy Ghast spawn egg and purple harness from 1.21.6
Command Changes
- New command alias: /ric
- Permission for the command is now
randomitemchallenge.admininstead ofrandomitemchallenge.start - There are now 3 subcommands:
/ric start [scenario],/ric stop,/ric scenario <set|setDefault> [scenario]
Random Changes
Stopped announcing advancements
Random should be more random
Did many internal optimisations
Bugfixes
- Fixed two minor bugs
- Fixed a major bug for Paper reported on the discord
- Fixed a duplication bug when offhanding the nearest enemy tracker
Optional dependencies
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:T2kQCmGI:I3KwZION"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:T2kQCmGI:I3KwZION"
}

