Saltar al contenido principal

Crear Eventos

webapp_banner.jpg

Esta guía es para EliteMobs 10 y posteriores

¿Qué son los Eventos Personalizados?

Custom Events here refer to events that occur randomly in-game, whether based on player actions or having a timed trigger. The plugin comes preloaded with a number of Custom Events, such as the Balrog event, the Kraken event and the Treasure Goblin events, to name a few.

This system is called Custom Events because the events can not only be customized but created from scratch. What follows is a guide on how to create and customize your own events.

Crear tus Eventos Personalizados

Custom event configuration files should be created in: plugins/EliteMobs/customevents/

Files must use the .yml format. The filename (without .yml extension) becomes the event identifier.

Example: my_cool_event.yml is referenced as my_cool_event

Configuraciones comunes

The following settings can/should be used for both action and timed events.


isEnabled

Sets if the event is enabled.

KeyValuesDefault
isEnabledBooleantrue
Ejemplo
isEnabled: true

eventType

Sets the type of event.

KeyValuesDefault
eventTypeDEFAULT / BREAK_BLOCK / FISH / TILL_SOIL / TIMEDnone

Note that BREAK_BLOCK, FISH and TILL_SOIL are Action Events and TIMED is Timed Events. DEFAULT is for events triggered by other means or special conditions.

Ejemplo
eventType: BREAK_BLOCK

bossFilenames

Sets the list of bosses which will be spawned. Mandatory!

KeyValuesDefault
bossFilenamesString Listnone
Ejemplo
bossFilenames:
- balrog.yml
- my_event_boss.yml

announcementPriority

Sets the announcement priority.

KeyValuesDefault
announcementPriorityInteger0
Ejemplo
announcementPriority: 1

startMessage

Sets the message sent at the start of the event.

KeyValuesDefault
startMessageStringnone
Ejemplo
startMessage: An event has started!

create_events_start_message.jpg


endMessage

Sets the message sent at the end of the event.

KeyValuesDefault
endMessageStringnone
Ejemplo
endMessage: An event has ended!

create_events_end_message.jpg


eventStartCommands

Sets the commands that run at the start of the event.

KeyValuesDefault
eventStartCommandsString Listnone
Ejemplo
eventStartCommands:
- say The event now starts!!
- "$chance=0.5$ say What a spawn!"

create_events_start_commands.jpg


eventEndCommands

Sets the commands that run at the end of the event.

KeyValuesDefault
eventEndCommandsString Listnone
Ejemplo
eventEndCommands:
- say The event ends, so sad.
- "$chance=0.5$ say Too slow bud!"

create_events_end_commands.jpg


Ejemplo de Configuración de Evento
isEnabled: true
bossFilenames:
- "cool_boss.yml"
- "other_cool_boss.yml"
announcementPriority: 3
startMessage: "Cool event is starting!"
endMessage: "Cool event is ending!"
eventStartCommands:
- say The event started!
eventEndCommands:
- say The event ended!

Ejemplo Completo de Evento Temporizado
isEnabled: true
eventType: TIMED
bossFilenames:
- "my_timed_boss.yml"
announcementPriority: 3
startMessage: "A timed event has started!"
endMessage: "The timed event has ended!"
eventStartCommands:
- say The timed event began!
eventEndCommands:
- say The timed event concluded!
spawnType: "my_spawn_location.yml"
localCooldown: 120
globalCooldown: 30
weight: 100
eventDuration: 15
endEventWithBossDeath: true
minimumPlayerCount: 1

Eventos de Acción

Events that have a chance of running when a specific action, such as breaking a block or fishing, happen.

Note: Action events automatically apply a 60-minute cooldown per player to prevent the same player from repeatedly triggering events.

chance

Sets the chance of the event happening when the action happens.

KeyValuesDefault
chanceValue between 0.0 and 1.00
Ejemplo
chance: 0.001

breakableMaterials

Sets the list of materials to check if the action is set to BREAK_BLOCK.

KeyValuesDefault
breakableMaterialsList of materialsnone
Ejemplo
breakableMaterials:
- BEEHIVE
- BIRCH_WOOD

Ejemplo de Configuración de Evento
chance: 0.001
breakableMaterials:
- COAL_ORE

Sets a 0.1% chance of running the event when a coal ore block is broken, assuming that the event type is BREAK_BLOCK.


Ejemplo Completo de Evento de Acción
isEnabled: true
eventType: BREAK_BLOCK
bossFilenames:
- "mining_boss.yml"
announcementPriority: 2
startMessage: "You've awakened something..."
chance: 0.001
breakableMaterials:
- DIAMOND_ORE
- EMERALD_ORE

Eventos Temporizados

Timed Events are events that happen at configurable time intervals. Once the cooldown for a timed event is over, a random timed event is picked from the list of timed events based on the weight of the event.

spawnType

Sets the Custom Spawn used by the event, which defines where the boss can spawn.

KeyValuesDefault
spawnTypeFilenamenone
Ejemplo
spawnType: nether_spawn.yml

localCooldown

Sets the amount of time, in minutes, before this event can be picked again.

KeyValuesDefault
localCooldownDouble0
Ejemplo
localCooldown: 120

globalCooldown

Sets the amount of time, in minutes, before the next event will be picked.

KeyValuesDefault
globalCooldownDouble0
Ejemplo
globalCooldown: 60

weight

Sets the weight of the event, affecting the chance that it will be picked over other events. Recommended: 100.

The weight system determines relative probability of event selection. For example:

  • Event A with weight 100 vs Event B with weight 50 = Event A is twice as likely to be selected
  • Higher weight = higher chance of being picked
  • Events are evaluated approximately every 5 minutes
KeyValuesDefault
weightDouble0
Ejemplo
weight: 60.5

eventDuration

Sets the maximum duration of the event, in minutes.

KeyValuesDefault
eventDurationDouble0
Ejemplo
eventDuration: 30

endEventWithBossDeath

Sets if the event ends with the boss death.

KeyValuesDefault
endEventWithBossDeathBooleantrue
Ejemplo
endEventWithBossDeath: true

eventEndTime

Sets the in-game time (in ticks) when the event ends. Use Minecraft's time system where 0=dawn, 6000=noon, 12000=dusk, 18000=midnight, 23000=late night. Set to -1 to disable time-based ending.

KeyValuesDefault
eventEndTimeInteger (0-24000, -1 to disable)-1
Ejemplo
eventEndTime: 23000

minimumPlayerCount

Sets the minimum amount of online players before the event will start.

KeyValuesDefault
minimumPlayerCountInteger1
Ejemplo
minimumPlayerCount: 5

Note that events get queued, meaning they will only start once the conditions defined in the spawnType are met.

Ejemplo de Configuración de Evento
isEnabled: true
bossFilenames:
- "cool_boss.yml"
- "other_cool_boss.yml"
announcementPriority: 3
startMessage: "Cool event is starting!"
endMessage: "Cool event is ending!"
eventStartCommands:
- say The event started!
eventEndCommands:
- say The event ended!
spawnType: "myCoolSpawn.yml"
localCooldown: 30
globalCooldown: 15
weight: 100
eventDuration: 20
endEventWithBossDeath: true
eventEndTime: 10000
minimumPlayerCount: 5