Mod
Pebble's Cobblemon Spawn Events
No reviews yet
Create custom legendary, event or normal Pokemon spawns with weighted probability and spawn intervals!
Does not follow a specific thematic focus apart from vanilla Minecraft.
Used for mods with little to no gameplay elements.
Includes a large focus on traversing worlds with enhanced world generation, structures, dungeons, and more for players to find unique loot.
Adds tools to customize the user interface and menus.
Adds extra features or content to an existing mod.
Features small, self-contained games within Minecraft.
Inspired by or including content related to the Pokemon franchise.
Community voices
Reviews
Click once to include, again to exclude, again to clear
No reviews yet. Be the first to review this project!
Get it on
Available Platforms
Compatibility
Supported Environments
About
Project Details
For authors
Embed Badge
If you're the author of this project, you can embed a live badge anywhere that supports HTML or Markdown. It updates automatically whenever ratings change.
Use HTML for any page that supports it, or Markdown for README files and Markdown-based descriptions.
Identifiers
Platform IDs
Resources
External Links
About
Description
Pebble's Cobblemon Spawn Events
Pebble's Spawn Events mod for Fabric and Forge Minecraft version 1.20.1
Make sure you have Fabric Language Kotlin installed (or Kotlin For Forge)!
Architechtury API is also a requirement.
Create dynamic and configurable spawnevents that chooses random players and Pokemon from the pool based on assigned weights. The randomiser for player tries to deprioritise the 2 latest players if more than 2 players are online so you won't see the same events happening on the same players constantly.
Commands
/spawnevent: Opens the spawn events UI containing live event and all the event history/spawnevent reload: Requires OP (permission level >=2), reloads the spawn event configuration. Preferably a restart is safer as the event cycles and who knows what happens if you make huge changes :v
Important
Certain interactions such as that with CobbleClear might give unexpected result. It is best that the event Pokemon species gets whitelisted from being autocleared.
Configurations
On first launch, a config folder is generated in config/pebbles-spawnevents
config.json
{
"enabled": true,
"minPlayers": 1, // Minimum online players for event to trigger
"spawnInterval": 1 //Spawn interval in minute between each event being rolled in
}
event-history/event-history-config.jsonAllows for custom label on how the event was ended on the display screen.
{
"enabled": true,
"capturedStatus": "<green>Captured",
"killedStatus": "<red>Killed",
"despawnedStatus": "<yellow>Despawned",
"unknownStatus": "<gray>Unknown"
}
event-history/event-history-screen.jsonAllows for flexible screen customisation, you can also use a bitmap title for custom overlay. Look at screenshot for how the screen appears.
{
"title": "<blue>Legendary Spawn History",
"liveSpawnSlot": 4,
"liveSpawnLores": [
"{pokemon}",
"<gray>Spawned near <aqua>{player_name.spawned}</aqua> in {dimension} <red>{time_passed}</red> ago",
"<gray>Biome: <yellow>{biome}"
],
"historySlots": [18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35],
"historyLores": [
"{pokemon}",
"<gray>Spawned near <aqua>{player_name.spawned}</aqua> in {dimension} <red>{time_passed}</red> ago",
"<gray>Biome: <yellow>{biome}",
"Status: {status} by {player_name.acted}"
],
"navForwardSlots": [
37
],
"navForwardStack": {
"displayName": "<aqua>Next Page",
"material": "minecraft:arrow",
"amount": 1,
"nbt": "",
"lore": [
"<yellow>Click to view next page"
]
},
"navBackSlots": [
36
],
"navBackStack": {
"displayName": "<aqua>Previous Page",
"material": "minecraft:arrow",
"amount": 1,
"nbt": "",
"lore": [
"<yellow>Click to view previous page"
]
},
"emptySlotStack": {
"displayName": "<gray>",
"material": "minecraft:gray_stained_glass_pane",
"amount": 1,
"nbt": "",
"lore": [
""
]
}
}
spawns/Contains all the spawn events. A Zapdos example is generated on first launch, feel free to copy the file and make as many different events as you want. The weight determines the chance. For example, if you have Zapdos (1 weight), Moltres (1 weight) and Articuno (2 weight), the odds for Zapdos spawning is 1/4 (25%), Moltress is 1/4 (25%) and Articuno is 1/2 (50%)
{
"pokemonProperties": "zapdos lvl=50 special_attack_iv=31",
"broadcast": {
"spawn": "<blue>The mythical entity, <yellow>Zapdos</yellow>, has been spotted in <light_purple>{biome}!\n<gray>It will be available for the next <green>{duration}</green> minutes.</gray>\n\n<blue>Closest player: <aqua>{player_name.spawned}</aqua>",
"despawn": "<blue>The mythical entity, <yellow>Zapdos</yellow>, has despawned.</blue>",
"capture": "<blue>The mythical entity, <yellow>Zapdos</yellow>, has been captured by <aqua>{player_name.acted}</aqua>!</blue>",
"kill": "<blue>The mythical entity, <yellow>Zapdos</yellow>, has been killed by <aqua>{player_name.acted}</aqua>!</blue>"
},
"spawnWeight": 1,
"despawnTimerMinutes": 10,
"sound": "minecraft:entity.lightning_bolt.thunder"
}
Supporter:
Osu of Cobblehaven helped fund this mod.
Versions
Files
Relations
Project Relations
More like this
Similar Mods
Suggestions use data such as tags, dependencies, dependents, descriptions, titles, and more to rank how much they overlap with this mod.
On ModDex
Community snapshot
By the numbers
Statistics
Want to reach Minecraft players?
We're looking for a server hosting partner to feature here and other parts of the site. Interested? Send us a message!
Get in touchGet it on
Available Platforms
On ModDex
Community snapshot
By the numbers
Statistics
Resources
