#Help with combat log no action bar

1 messages · Page 1 of 1 (latest)

mellow laurel
#

Why have 2 vars

#

Instead of a boolean check if the timer is set, and delete it after 0

#

Use :: not .

#

Use uuids

#

Why have 2 lines for the action bar, just send it once

plucky crater
#

you need another percent sign in the red circled areas

#

before the first {, after last }

wet vapor
#

@mellow laurel Can you please explain your suggestions I am pretty new to this 🙂

mellow laurel
wet vapor
#

So should I add those percentages?

mellow laurel
# wet vapor <@418899084557156362> Can you please explain your suggestions I am pretty new to...

List variables are much more versatile, no reason to not use them. Separate sections in your variables with :: not . ({balance.%player%} -> {balance::%player%})

UUID stands for unique user ID, basically a serial number for your minecraft account. Using this prevents the variables from being ‘lost’ when someone changes their username.
{balance::%player%} = {balance::bob} if the player changes their username from Bob to Alice, their balance will then be saved as {balance::alice}, and they will ‘lose’ the previous value stored under their old name. {balance::%player’s uuid%} = {balance::1234} no matter what username.

Instead of on quit: if {inCombat::%player’s uuid%} = true: broadcast “%victim% disconnected during combat”, use on quit: if {combatLogTimer::%player’s uuid%} is set: broadcast “%victim% disconnected during combat”

instead of send action bar “%{number}%” to player if a = b: add 1 to {number} send action bar “%{number}%” to playeruse if a = b: add 1 to {number} send action bar “%{number}%” to player