Çözüldü Towny İçin PvPManager

  • Konuyu Başlatan Konuyu Başlatan hemrekir
  • Başlangıç tarihi Başlangıç tarihi
  • Görüntüleme 1.186
Durum
Üzgünüz bu konu cevaplar için kapatılmıştır...

hemrekir

Odunlara Vur Vur Vur!
Katılım
6 Mayıs 2021
Mesajlar
25
Elmaslar
2
Puan
3.770
Minecraft
hemrekir

Discord:

hemrekir

Merhabalar.Biz towny sunucumuzda pvp için PvPManager kullanmaktayız.PvpManager da insanlar combat halindeyken sadece alan WorldGuard le pvp ye kapatıldıysa sokmamakta.Ancak townda pvp kapalıysa o alana girebilmekte/ve hasar almamakta.Ne önerirsiniz?
 
Merhabalar.Biz towny sunucumuzda pvp için PvPManager kullanmaktayız.PvpManager da insanlar combat halindeyken sadece alan WorldGuard le pvp ye kapatıldıysa sokmamakta.Ancak townda pvp kapalıysa o alana girebilmekte/ve hasar almamakta.Ne önerirsiniz?
Anladığım kadarıyla wg bölgelere giremiyor ama town bölgelerine girebiliyor.
Sebebi ise PVPManager towny eklentisini desteklemiyor olabilir, bu nedenle CombatLogX kullanınız.
1622737711370.png
 
Anladığım kadarıyla wg bölgelere giremiyor ama town bölgelerine girebiliyor.
Sebebi ise PVPManager towny eklentisini desteklemiyor olabilir, bu nedenle CombatLogX kullanınız.
Ekli dosyayı görüntüle 177318
CombatLogX i ayarlamak istiyorum mesela eşya bırakma/alma vb. ancak configte böyle bir yer bulunmamakta.Nasıl yapabilirim?Spigot un sayfasından indirdim.
 
# Default Settings Configuration for CombatLogX
# Made by SirBlobman for v10.3.8.5

# Please DO NOT change this value or your config may be corrupted
generated-by-version: "10.3.8.5"

# What is the name of the language file for CombatLogX?
# If the file does not exist, the default will be used
# File Location: /plugins/CombatLogX/language/<choice>.yml
#
# Default: "en_us"
language: "en_us"

# This option only works correctly in Spigot 1.12.2+
# Should the plugin try to make the messages the same language that was selected by the player?
# (Unknown or undetectable languages will use the language configured above)
#
# Default: true
per-player-locale: true

# Should extra messages be printed for certain tasks?
# Only use this if you are having issues or you are asked to by SirBlobman
#
# Default: false
debug: false

# Should the plugin check for updates after it's enabled?
#
# Default: true
update-checker: false

broadcast:
# Should a message be broadcasted when the plugin is loaded by Bukkit?
#
# Default: true
on-load: false

# Should a message be broadcasted when the plugin is enabled?
#
# Default: true
on-enable: false

# Should a message be broadcasted when the plugin is disabled?
#
# Default: true
on-disable: false

# This is a list of worlds that CombatLogX will not tag players in
# World names are case sensitive. "world" is not the same as "WoRlD"
# Make sure you are not using the world aliases from Multiverse
disabled-worlds: []

# Set this to true to use the 'disabled-worlds' as a whitelist.
# Default: false
disabled-worlds-is-whitelist: false

# This is a list of commands that will be executed whenever a player is tagged.
# Commands will run in console by default
# Available Prefixes:
# [PLAYER] - run the command as the player that was tagged
# [OP] - run the command as the player that was tagged, but with "Server Operator" permissions (not recommended)
# Set this list to empty to disable the commands
# e.g. "combat-sudo-command-list: []"
combat-sudo-command-list: []

# This is a list of commands that will be executed whenever a player is untagged
# Commands will be run in console by default
# Available Prefixes:
# [PLAYER] - run the command as the player that was tagged
# [OP] - run the command as the player that was tagged, but with "Server Operator" permissions (not recommended)
# Set this list to empty to disable the commands
# e.g. "untag-sudo-command-list: []"
untag-sudo-command-list: []


# Set this to true to link wolves, cats, parrots, and other pets to the entity that owns them.
# This will only link the owner if the pet is the attacker
#
# Default: true
link-pets: true

# Set this to true to link arrows, potions, snowballs, eggs, and other projectiles that can be shot by entities.
# This will only link the shooter if they are the attacker
#
# Default: true
link-projectiles: true

combat:
# How long should players be tagged?
# The timer is in seconds.
#
# Default: 15
timer: 20

# What permission should be used to bypass combat tagging?
# Set this to "" to disable the bypass permission.
#
# Default: "combatlogx.bypass"
bypass-permission: "combatlogx.bypass"

# Should players be allowed to tag themselves using arrows?
#
# Default: false
self-combat: false

untag:
# Should players be removed from combat when they die?
#
# Default: true
on-self-death: true

# Should players be removed from combat when their enemy is killed?
#
# Default: false
on-enemy-death: true

punishments:
# Should players be punished when they quit the game?
#
# Default: true
on-quit: true

# Should players be punished if they are kicked from the game?
#
# Default: false
on-kick: false

# Which kick messages should be ignored for punishments?
# This option is ignored if `on-kick` is false
# The plugin uses a string contains check, so messages are case sensitive
on-kick-ignore-list:
- "kicked by SirBlobman"
- "troll"

# Should players be punished if the combat timer expires?
# You shouldn't need this option unless you're testing something
#
# Default: false
on-expire: false

# When should the player be killed by CombatLogX?
# Valid Options: QUIT, JOIN, NEVER
#
# Default: QUIT
kill-time: QUIT

# A random message is selected from this list when the player is killed by CombatLogX
# If you don't want custom death messages set this to an empty list
#
# Disabled: custom-death-messages: []
custom-death-messages:
- "{name} was killed for logging out during combat."
- "{name} instantly died due to logging out during combat."

# This is a list of commands that will be executed on the player that logged out.
# Set this to an empty list to not run any commands
# Commands will run in console if a prefix is not added
# Available Prefixes:
# [PLAYER] - run the command as the player that was tagged
# [OP] - run the command as the player that was tagged, but with "Server Operator" permissions (not recommended)
#
# Disabled: punish-command-list: []
punish-command-list: []
 
# Default Settings Configuration for CombatLogX
# Made by SirBlobman for v10.3.8.5

# Please DO NOT change this value or your config may be corrupted
generated-by-version: "10.3.8.5"

# What is the name of the language file for CombatLogX?
# If the file does not exist, the default will be used
# File Location: /plugins/CombatLogX/language/<choice>.yml
#
# Default: "en_us"
language: "en_us"

# This option only works correctly in Spigot 1.12.2+
# Should the plugin try to make the messages the same language that was selected by the player?
# (Unknown or undetectable languages will use the language configured above)
#
# Default: true
per-player-locale: true

# Should extra messages be printed for certain tasks?
# Only use this if you are having issues or you are asked to by SirBlobman
#
# Default: false
debug: false

# Should the plugin check for updates after it's enabled?
#
# Default: true
update-checker: false

broadcast:
# Should a message be broadcasted when the plugin is loaded by Bukkit?
#
# Default: true
on-load: false

# Should a message be broadcasted when the plugin is enabled?
#
# Default: true
on-enable: false

# Should a message be broadcasted when the plugin is disabled?
#
# Default: true
on-disable: false

# This is a list of worlds that CombatLogX will not tag players in
# World names are case sensitive. "world" is not the same as "WoRlD"
# Make sure you are not using the world aliases from Multiverse
disabled-worlds: []

# Set this to true to use the 'disabled-worlds' as a whitelist.
# Default: false
disabled-worlds-is-whitelist: false

# This is a list of commands that will be executed whenever a player is tagged.
# Commands will run in console by default
# Available Prefixes:
# [PLAYER] - run the command as the player that was tagged
# [OP] - run the command as the player that was tagged, but with "Server Operator" permissions (not recommended)
# Set this list to empty to disable the commands
# e.g. "combat-sudo-command-list: []"
combat-sudo-command-list: []

# This is a list of commands that will be executed whenever a player is untagged
# Commands will be run in console by default
# Available Prefixes:
# [PLAYER] - run the command as the player that was tagged
# [OP] - run the command as the player that was tagged, but with "Server Operator" permissions (not recommended)
# Set this list to empty to disable the commands
# e.g. "untag-sudo-command-list: []"
untag-sudo-command-list: []


# Set this to true to link wolves, cats, parrots, and other pets to the entity that owns them.
# This will only link the owner if the pet is the attacker
#
# Default: true
link-pets: true

# Set this to true to link arrows, potions, snowballs, eggs, and other projectiles that can be shot by entities.
# This will only link the shooter if they are the attacker
#
# Default: true
link-projectiles: true

combat:
# How long should players be tagged?
# The timer is in seconds.
#
# Default: 15
timer: 20

# What permission should be used to bypass combat tagging?
# Set this to "" to disable the bypass permission.
#
# Default: "combatlogx.bypass"
bypass-permission: "combatlogx.bypass"

# Should players be allowed to tag themselves using arrows?
#
# Default: false
self-combat: false

untag:
# Should players be removed from combat when they die?
#
# Default: true
on-self-death: true

# Should players be removed from combat when their enemy is killed?
#
# Default: false
on-enemy-death: true

punishments:
# Should players be punished when they quit the game?
#
# Default: true
on-quit: true

# Should players be punished if they are kicked from the game?
#
# Default: false
on-kick: false

# Which kick messages should be ignored for punishments?
# This option is ignored if `on-kick` is false
# The plugin uses a string contains check, so messages are case sensitive
on-kick-ignore-list:
- "kicked by SirBlobman"
- "troll"

# Should players be punished if the combat timer expires?
# You shouldn't need this option unless you're testing something
#
# Default: false
on-expire: false

# When should the player be killed by CombatLogX?
# Valid Options: QUIT, JOIN, NEVER
#
# Default: QUIT
kill-time: QUIT

# A random message is selected from this list when the player is killed by CombatLogX
# If you don't want custom death messages set this to an empty list
#
# Disabled: custom-death-messages: []
custom-death-messages:
- "{name} was killed for logging out during combat."
- "{name} instantly died due to logging out during combat."

# This is a list of commands that will be executed on the player that logged out.
# Set this to an empty list to not run any commands
# Commands will run in console if a prefix is not added
# Available Prefixes:
# [PLAYER] - run the command as the player that was tagged
# [OP] - run the command as the player that was tagged, but with "Server Operator" permissions (not recommended)
#
# Disabled: punish-command-list: []
punish-command-list: []
Değerli ziyaretçimiz, içeriği görebilmek için şimdi giriş yapın veya kayıt olun.

bütün ayarları survival sunucusu için yapıldı. expansions kısmın da mob-tagger klasöründe ki şeyi kapatırsan daha iyi olur unutmuşum.

En iyi cevap verirsen sevinirim.
 
Durum
Üzgünüz bu konu cevaplar için kapatılmıştır...

Hala Discord sunucumuza katılmadın mı?

Büyük bir topluluğun parçası ol, etkinliklere katıl ve özel hediyeler kazanma şansı yakala!

Şimdi Katıl
Üst