1.2.0-neoforge
Compatibility
Changes
Version 1.2.0-beta
This release brings SnackStay onto Cobblemon 1.8, hardens how snack spawns are locked, and gives you control over lock notifications.
What's new
Cobblemon 1.8
- Targets Cobblemon 1.8.0 and up (Minecraft 1.21.1)
- Spawn buckets are handled as strings (Cobblemon removed the old
SpawnBuckettype) - Compatible with the 1.8 snack / fishing / wild spawn pipeline
Alpha Pokémon
- New config option:
persistAlphas(default true) - Alphas that match your rules are locked so they do not despawn
/snackstay whyreportsalpha=true/false
Notifications you can style
- Choose where the lock message appears:
actionbar,chat,both, ornone - Custom format string with placeholders:
{species}·{reasons}
- Supports familiar
&formatting codes (colors, bold, italic, underline, reset, and so on)
Example default: &aSnackStay locked &f{species} &7({reasons})
Filters (unchanged, still fully configurable)
- Spawn buckets (
rare,ultra-rare, …) - Species labels (legendary, mythical, ultra_beast, paradox, …)
- Shinies
- Hidden ability
- Min perfect IVs / min IV total
- Species include / exclude lists
- Optional fishing and natural wild matching
Persistence
- Locks via
setPersistenceRequiredplus NBT (SnackStayLocked, bucket, source) - Re-applies on chunk load when enabled
- Bucket is stored at lock time so
/snackstay whycan explain the decision later
Commands
/snackstay reload— reload config (op level 2)/snackstay why— nearest Pokémon: stay/despawn reasons, labels, shiny, alpha, IVs, NBT/snackstay status— quick summary of active settings/snackstay persist— force-lock nearest wild Pokémon (op level 2)
Config
- File:
config/snackstay.json - New keys for this beta:
persistAlphasnotifyModenotifyFormatnotifyRadius
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:ESbTDO3M:zNfYqX7Q"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ESbTDO3M:zNfYqX7Q"
}

