-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow the [CombatTag] prefix for messages to be disabled #3
Comments
Are you going to provide a description of your error? |
That's the point, there is no error :) |
So you want to disable tag messages? |
I want it so if I set a message (Test123) it'll show up as [CombatTag] Test123 and I just want it to be Test123 |
So you want to make the combat tag prefix optional. |
Ye |
Found a solution? |
Yes, but this is very low on my priority list. |
Well, so you can adjust the message like you said in your plugin description |
You can adjust the message, just not the prefix. |
Well, nvm I guess.. Ugh |
I can change it, I just want to know why you want to. |
Tag message damaged is bugged I think, if I fill nothing in it will still say [CombatTag] Ignore the ->
Tue Mar 31 13:59:34 EDT 2015
npcDieAfterTime=false
-> tagMessageDamaged=
blockEditWhileTagged=true
blockCreativeTagging=true
Enable-Debugging=true
dontSpawnInWG=false
onlyDamagerTagged=false
Version=6.3.2-SNAPSHOT
commandMessageTagged=&2[&aServer&2]&e You cannot log out for [time] seconds.
npcDespawnTime=-1
commandMessageNotTagged=&2[&aServer&2] &eYou can log out.
disabledCommands=[]
InstaKill=true
npcName=PvpLogger
sendMessageWhenTagged=true
blockTeleport=false
Tag-Duration=10
disabledWorlds=[exampleWorld,exampleWorld2]
mobTag=false
tagMessageDamager=You have hit [player]. Type /ct to check your remaining tag time.
blockEnderPearl=false
blockFlying=false
DropTagOnKick=true
playerTag=true
The text was updated successfully, but these errors were encountered: