Repository navigation
Configuration
This is the Configuration Page of LightFight. In here you will any information regarding the plugin config.yml entries and its features. It is advised to read this guide carefully in order to better understand how to properly set the values for the plugin. Alternatively, every key is commented to remind you of what it does and how to eventually change it. You can change every option in this page with the ingame command /lightfight set
The plugin will automatically update all of its configuration files periodically. If you do not like this behaviour, you can disable it by setting this value to false. The reload can be done manually using the command /lightfight reload.
This value enables or disables the combat tag for the players. If it is set to false, hitting a player will NOT put the hitters and the hitted in combat.
Just like player-ct, setting this value to false will disable the combat tag for entities (that are not players).
The entity-whitelist is a list of Minecraft entities that will be ignored by the plugin if entity-ct is enabled. You can check out a list of all the entities here. For example, if the word "Skeleton" is added, a player hit by a Skeleton will not be put in command.
The plugin offers the ability to enable or disable a player's PvP mode. By setting this option to
true, the user who disabled her/his PvP will not be able to hit other players, unless they turn it on again.
This option has the same functionality of pvp-backwards, but only extended to general entities (not players).
Setting the value of this key to true means that when everybody that were hitting a player run away or get killed, the player wil be put out of combat and will be safe to logout.
Self-explanatory: when the player dies, she/he will be automatically respawned.
The time (in seconds) that the combat tag should last before the player is safe again. Hitting again another player will reset the timer.
If a player in combat tries to log off while this option is set to true, she/he will be killed and her/his death will count as a kill by one of the hitters.
Just like kill-on-quit, but handles the "kick" part. You can enable the quit and disable the kick so that a user will be killed only when she/he logs off autonomously.
The following are all grace section. "Grace" is a status where the player that logged on for the first time in the server will be safe from any kind of PvP and PvE activities (See below for more).
The time (in minutes) that the grace should last. This will be calculated according to the player's first login in the server and not the first activation of the plugin.
Setting this value to true will keep the player safe from other users trying to attack her/him.
Similar to pvp, but for all the other Minecraft entities.
If prevent-pvp is turned on, the user will NOT be able to hit any user until she/his out of the grace status. Conficts with deny-on-pvp
Similarly to prevent-pvp, enabling this option will prevent the user from attacking any kind of mob. Conficts with deny-on-pve
If the user tries to attack a player while deny-on-pvp is enabled, she/he will lose her/his grace status prematurely. Only works if prevent-pvp is disabled!
Similar to deny-on-pvp, but extended to all the Minecraft entities. Only works if prevent-pve is disabled!
In here you can specify a list of all the ignored worlds. If the player is hit or hits and she/he is in one of these worlds, they will not be put in combat mode.
If set to false, when the user tries to pull towards herself/himself another entity (or player), they will be both tagged.
If this option is disabled, even players in Creative Gamemode will be put in combat when hitting someone.
By setting this setting to true, if the player attacks or gets attacked while they are flying, they will lose their ability to fly, and they will only get it back out of combat. Of course, if the player did not have permissions to fly before, they will not get it after.
The enable section contains a list of many options that enable or disable some part of the gameplay during the combat tag status.
If it is disabled, a player in combat will not be able to chat.
If it is disabled, a player in combat will not be able to change Gamemode.
If it is disabled, a player in combat will not be able to open their inventory.
If it is disabled, a player in combat will not be able to drop items.
If it is disabled, a player in combat will not be able to teleport (or be teleported). Commands such as /spawn, /tp... will NOT work.
If it is disabled, a player in combat will not be able to teleport using Enderpearls.
LightFight is compatible with WorldGuard and more specifically with the flag "pvp". If a player is in combat and this option is active, she/he will not be able to enter a pvp deny zone.
In here you can specify how you want to push back the player that tries to enter a "pvp deny" zone. There are three available options:
-
BLOCK: places blocks in the zone walls; -
KNOCKBACK: knocks back the player that tries to enter; -
NONE: prevents the player to access that area.
If barrier-type is set to BLOCK, here you can specify which block. Keep in mind that some blocks (like RED_STAINED_GLASS) will not be available in some versions.
If barrier-type is set to BLOCK, here you can specify the radius of the wall.
Specify how to display the timer message in game. There are four available options:
-
ACTIONBAR: displays an ActionBar right above the player's hotbar; -
PROGRESS: displays a progress right above the player's hotbar (check messages.yml to edit the Progress characters); -
BOSSBAR: displays a BossBar in the upper side of the screen; -
NONE: do not display anything.
Choose the BossBar timer-message color. You can check a full list of BossBar Colors here.
This option will only work if you are in 1.9 or above and the option timer-message is set to BOSSBAR.
Similarly to timer-message, in here you can specify how you want to tell the server when a player entered combat mode. There are four entries:
-
ACTIONBAR: displays an ActionBar right above the player's hotbar; -
BOSSBAR: displays a BossBar in the upper side of the screen; -
MESSAGE: displays a message in chat; -
NONE: do not display anything.
If this option is enabled, when a player gets hit by another user, they will both receive a glow effect. This is only supported on 1.9 and above.
Specify the color of the glow effect. You can check a full list of available colors here.
glow-color will only work if glow-enabled is set to true.
By default the plugin blocks every command issued while the user is in combat mode. However, in here you can specify the commands that should be allowed. Keep in mind that specifying a command alias will also work, since the plugin tries to get every command from the server with every alias.
In here you can specify a list of all the potions that should be disabled when the player enters the combat mode. You can see a full list of potions here.
Adding a projectile type to this list will prevent it from putting a player in combat mode. You can check a list of all the available projectiles (and entities) here.