Hi, I have not checked out most of the skript but already I can see a very bad practice, not only did you constantly use else, you also used "else if" with the condition that is negative to the condition you are reversing, for example on the line:
`
else if {warps::%arg-1%} is set:
`
You do not need to put the condition "if {warps::%arg-1%} is set:" because you are already confirming it is true by declaring else, this takes up server data, a little bit but most importantly it is a TERRIBLE practice
Also, another thing, I would recommend to change your code from "else" to using stop, for example:
before:
`
command /createwarp <string>:
permission: {@warp_create}
trigger:
if arg-1 is set:
if {warps::%arg-1%} is not set:
set {warps::%arg-1%} to location of player
send "{@prefix}&a Successfully created %arg-1% warp."
else if {warps::%arg-1%} is set:
send "{@prefix}&c This warp already exist!"
if arg-1 is not set:
send "{@prefix} &cUsage: /createwarp <warp>"
`
After
`
command /createwarp <string>:
permission: {@warp_create}
trigger:
if arg-1 is set:
if {warps::%arg-1%} is set:
send "{@prefix}&c This warp already exist!"
stop
set {warps::%arg-1%} to location of player
send "{@prefix}&a Successfully created %arg-1% warp."
stop
send "{@prefix} &cUsage: /createwarp <warp>"
`
As you can see, both of the code variants do the exact same thing, except one is much more cleaner, a bit practice in general, and takes less server power.
Keep in mind I am not making fun of you, I just want you to improve, I am just making a note of this in case you think so.
If you wish to stop using else and switch to "stop" you may contact me on my discord Bassouli#0069 and I would be happy to help you
About the rest of the skript, I do not have time to see that yet so I will view it later, have a good day!