Skip to main content

🚨 Troubleshooting

This page covers common EventForge setup issues and how to fix them.

If something does not work, check your server console first. EventForge tries to show validation warnings when an event file has a problem.

Event does not load

Check the basics first:

The file is inside plugins/EventForge/events/
The file ends with .yml
The event has an id
enabled is true
duration is valid
the objective type is valid
YAML indentation is correct

Example:

id: mining_rush
enabled: true
display-name: "&bMining Rush"
duration: 10m
tip

Most event loading issues are caused by YAML spacing or a missing required section.

YAML spacing issues

YAML is spacing-sensitive.

Good:

messages:
  start:
    - "&aEvent started!"

Bad:

messages:
 start:
   - "&aEvent started!"

Use spaces, not tabs.

Event starts but nothing scores

Check:

The event is active
The objective type is correct
The scoring section is configured correctly
The player is doing the correct action
The block/mob/item names are valid
The score values are greater than 0

For mining events, check the block names:

blocks:
  STONE:
    points: 1

For mob events, check entity names:

mobs:
  ZOMBIE:
    points: 2

Event cannot start

An event may fail to start because of:

cooldown
not enough players
already active
invalid event ID
world conditions
permission conditions
time conditions
weather conditions

In v1.0.1, compatible addons and PlaceholderAPI can show the start reason.

Example PlaceholderAPI placeholder:

%eventforge_event_start_reason_mining_rush%

Cooldown problems

Cooldowns are configured inside an event file:

cooldown:
  enabled: true
  duration: 1h

Cooldowns start after a natural event finish.

They do not start after:

forced stop
reload
shutdown

Cooldowns are saved in:

plugins/EventForge/cooldowns.yml

Event will not start because of cooldown​

Wait for the cooldown to end or clear it using an admin command/addon tool.

Cooldown did not start​

Make sure the event finished naturally.

A forced stop does not start the cooldown.

Cooldown stayed after restart​

This is expected.

Cooldowns persist through cooldowns.yml.

Variable problems

Event variables are configured like this:

variables:
  event_color: "&b"
  arena_name: "Spawn Mine"

They are used like this:

{var:event_color}
{var:arena_name}

Variable does not parse​

Check:

The variable exists
The variable key is spelled correctly
The variable is used in a supported section
The event loaded successfully

Blank variable is ignored​

This is invalid:

variables:
  arena_name: ""

Use an actual value:

variables:
  arena_name: "Spawn Mine"

Nested variable does not work​

Variables must be simple values.

Bad:

variables:
  arena:
    name: "Spawn Mine"

Good:

variables:
  arena_name: "Spawn Mine"

Chance reward problems

Chance rewards use percentages.

chance-rewards:
  rare_key:
    chance: 5.0
    commands:
      - "crate key give {player} rare 1"

Rules:

chance must be greater than 0
chance above 100 is treated as 100
commands cannot be empty

Chance reward did not run​

That may be normal.

A 5.0 chance means 5%, not guaranteed.

For testing, use:

chance: 100.0

Chance reward shows a warning​

Check that the reward has commands:

commands:
  - "give {player} diamond 1"

Reward command does not work

Reward commands run from console.

Good:

commands:
  - "eco give {player} 100"

Bad:

commands:
  - "/eco give {player} 100"

Check:

The command works from console
The command does not start with /
The player placeholder is correct
The reward section is enabled
The player qualified for the reward

Multi-objective problems

Multi-objective events use:

objectives:
  mining:
    type: MINE_BLOCKS

Single-objective events use the older format:

objective:
  type: MINE_BLOCKS

Both can work, but do not mix them unless you know how your config is intended to behave.

Only one objective is loaded​

Make sure you used:

objectives:

for multi-objective events.

Scores are higher than expected​

Check the objective multiplier:

weight: 1.5

A weight of 1.5 means scores from that objective are multiplied by x1.5.

Objective type is unknown​

Check:

The objective type is spelled correctly
The addon for custom objective types is installed
The addon loaded before the event was reloaded

Action and trigger problems

Actions are configured under:

triggers:
  event-start:
    actions:
      - type: BROADCAST
        message: "&aEvent started!"

Action does not run​

Check:

The trigger name is correct
The action type is correct
The event is loaded
The event is reaching that trigger

Unknown action type​

This usually means:

The action type is misspelled
The addon that registers it is missing
The addon failed to load

Player action does nothing​

Some actions need a player, such as:

MESSAGE
ACTIONBAR

Use those with player-based triggers like:

player-score

Webhook problems

Webhook actions require an HTTPS URL.

triggers:
  event-start:
    actions:
      - type: WEBHOOK
        url: "https://discord.com/api/webhooks/..."
        message: "{event_display} has started!"

Check:

The URL starts with https://
The webhook URL is valid
The webhook was not deleted
The server can make outbound web requests
The message is not empty
warning

Do not post real webhook URLs publicly.

Dialogue problems

Dialogues are configured inside an event file:

dialogues:
  guide_intro:
    lines:
      - "&eGuide: &fHello there!"

Dialogue does not start​

Check:

The event is loaded
The dialogue ID is correct
An addon/Skript/custom objective is starting it
The player is online

EventForge provides the dialogue engine, but something still needs to trigger the dialogue.

Sound does not play​

Check that the sound name is valid.

sound: ENTITY_VILLAGER_AMBIENT

Completion command does not run​

Check:

The dialogue finishes naturally
The command works from console
The command does not start with /

PlaceholderAPI problems

If placeholders do not work, check:

PlaceholderAPI is installed
EventForge is installed
EventForge started successfully
The event is loaded
The placeholder spelling is correct

Test with:

/papi parse me %eventforge_loaded_events%

For event variables:

/papi parse me %eventforge_event_variable_mining_rush_arena_name%

GUI problems

GUI title did not change​

Check:

The title key is correct
YAML spacing is valid
EventForge was reloaded
You opened the correct menu

GUI rows did not change​

This is expected in v1.0.1.

gui.rows is reserved for future layout updates. Current menus still use 6 rows.

Button items did not change​

Button config exists for future expansion, but button customization is not fully applied across every menu yet.

Reload problems

If /eventforge reload fails:

Check console for validation errors
Fix the event/config file mentioned
Use spaces instead of tabs
Make sure every YAML section is indented correctly

If the plugin asks for confirmation, follow the confirmation message.

Still stuck?

Try this order:

1. Check console errors
2. Check YAML spacing
3. Temporarily simplify the event file
4. Test with one objective
5. Test without rewards
6. Test without triggers/actions
7. Add sections back one at a time

This usually makes it easier to find the broken section.