well first of all you're*
Also it's not necessarily cleaner because it makes the code longer and can sometimes be harder to understand if the viewer isn't very skilled, plus it's unoptimistic.
you could've just not used optional arguments, have put `usage: &c/forcechat (player) (message)` before the trigger and made it use a player argument instead of an offlineplayer argument
You could also do this:
on walk on barrier:
set {nd::%player's uuid%} to (unix timestamp of now) + 10
on damage:
if damage cause is fall:
if unix timestamp of now >= {nd::%player's uuid%}:
cancel event
delete {nd::%player's uuid%} # save variable storage :)
options:
item: stick named "&cnerd"
command: command
on join:
give player {@item}
on right click:
execute console command "{@command}" if player's tool is {@item}
on skript load:
if {done} is not set:
loop all blocks:
set {random::%loop-block%} to random item out of all items
set {done} to true
command reset:
permission: admin.reset
trigger:
loop all blocks:
set {random::%loop-block%} to random item out of all items
on break:
clear drops
drop {random::%event-block%} at event-block's location
im late to the show but hey optimization
command dupe:
trigger:
set item amount of player's tool to 64
https://parser.skunity.com/db1b1e28
No addons required!
command stack:
trigger:
give player 64 of player's tool
Use this instead, optimized and has more features.
command dupe <int=1>:
trigger:
give (arg-int * item amount of player's tool) of player's tool to player
The original creator abandoned it, it's deprecated(?, I'm fairly sure it is), LimeGlass's fork hasn't been updated in 4 months, it's better to just use Skellett, etc.