1.20.4-6.0-fabric+forge+neo
Compatibility
Required content
Changes
The big 6.0 update!
Without extra configuration, the mod remains the same. '/starterkit set' still exists.
Old starterkit files are automatically converted to the new format.
See the description for examples!
There are (a few) extra features:
Improved tracking to see if a kit should be given. Inside the world folder.
Added support for potion effects to give alongside the starterkit gear.
You can add multiple kits, with an option to let players choose or give one randomly.
Players can choose kits, when enabled, via a custom GUI inventory screen.
If the mod is not installed on the client, players can still choose a kit via commands.
Kit descriptions! Give your instance more of an RPG-vibe with kit backstories.
There are 3 new (inactive) default starterkits, as an example of how the configuration works.
These kits are the inactive folder by default: Archer, Lumberjack and Witch.
Added an alias for /starterkit, /sk.
As an admin you can use the following new commands:
/sk add (kit_name)
Adds your current inventory to the active kits.
/sk set (kit_name)
Sets your current inventory as the only active kit.
/sk give <player> (kit_name)
Give a player a random (or specific) starter kit.
/sk activate <kit_name>/_all
Moves kit_name or all kits from inactive to active.
/sk deactivate <kit_name>/_all
Moves kit_name or all kits from active to inactive.
/sk list (inactive)
Lists all active (or inactive) kits.
/sk reset
Resets all tracking. Players receive another kit on join.
/sk reload
Reloads starter kit changes from the config folder.
...and probably some more I forgot. Hope you like the new changes!
The complete changelog with previous versions can be found at:
https://serilum.com/mods?changelog=starter-kit
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:6L3ydNi8:7BD3dh3n"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:6L3ydNi8:7BD3dh3n"
}


