Content generated with AI — it may contain mistakes.

ExyliaCombat/HelpUpdated in v1.1.0

Common problems

Fixes for the problems server owners hit most: nothing restricted, no barrier, logouts not punished, kills not counting and no kill money.

Page 19 of 253 min read

Find your symptom, then follow the fix.

The plugin does not start#

The console names what is missing. ExyliaLib is required. The loader installs it for you and asks for a restart. See Install ExyliaCombat.

I am never restricted when I test#

Operators hold exyliacombat.bypass, which frees them from every restriction and the barrier, and exyliacombat.bypass.logout, which spares them the logout punishment. Test with a normal player, or deny both permissions. See Permissions.

Nothing is restricted and logging out is not punished#

Another combat plugin is deciding the tag. With combat.provider: AUTO, DeluxeCombat, CelestCombat or PvPManager take over as soon as they are installed, and the restrictions, the barrier and the logout punishment become theirs. The console names the provider on start. To use ExyliaCombat's own rules, set combat.provider: BUILTIN in config.yml and run /combatadmin reload. See Combat tag.

A logout was not punished#

The player is spared when the server is stopping, when they hold exyliacombat.bypass.logout, when they stand in a world listed in combat.logout.exempt-worlds, or when they were kicked and combat.punish-on-kick is false (the default). A timeout is always punished. See Punish combat logging.

The barrier does not show, or entering spawn is not refused#

The plugin needs a source that says where PvP is off. Check that:

  • The spawn has pvp deny in WorldGuard, or is a claim, town or island with PvP off.
  • That source is on under safe-zones in config.yml.
  • The player stands outside the zone: the wall is not drawn from inside one.

Without packetevents the barrier is drawn with fake blocks instead of translucent tiles. See Restrict a tagged player.

A command is still allowed in combat#

By default only /msg, /tell, /w, /r, /reply and /discord work while tagged. If you set commands.mode to BLOCK, only the listed commands are refused. Check commands in modules/combat-restrictions/config.yml.

Kills do not count#

kill-abuse is on by default. A second kill of the same victim within five minutes, and kills between accounts on the same address, count for neither stats nor rewards. Two friends testing from one home count as one address. See Stop kill farming.

Kills give no money#

money.enabled in modules/kill-rewards/config.yml is false by default, and it needs an economy that ExyliaLib can use. Kills flagged by kill-abuse, and kills in disabled-worlds or disabled-regions, pay nothing either. Kill streaks and milestones also need the stats module on.

I changed a module switch and nothing happened#

Module switches and command names are read at startup. Restart the server. /combatadmin reload reads the settings and messages, not the switches.

My TAB prefixes disappear during a fight#

That is combat-nametag: a colour, prefix or suffix puts a tagged player in a team of its own. Use only glow: true with an empty colour, prefix and suffix, or switch the module off. It is off by default.

A placeholder shows as text#

PlaceholderAPI is missing, the module of that placeholder is off, or the stat name is misspelled. See Placeholders.

Something missing on this page? Tell us on Discord