Problem with warning system

[Ryan Meikle]

Hello,
I'm currently trying to make a warning system in skript.

But for some odd reason the command refuses to send.

No errors on reload: http://prntscr.com/efzc5c

The console does log the command http://prntscr.com/efzcdl

Any suggestions to this?

Code:

command /warn [<player>] [<text>]:
 permission: edgemc.warn
 permission message: {@noperm}
 trigger:
  if player has permission "edgemc.warn":
   if arg 1 is not set:
    if arg 2 is not set:
     send "{@prefix} You did not specify a player and a reason."
     stop
   if arg 1 is set:
    if arg 2 is not set:
     send "{@prefix} You did not specify a reason"
     stop
   if arg 1 is set:
    if arg 2 is set:
     if {warning1::%uuid of arg 1%} is false:
      set {warning1::%uuid of arg 1%} to true
      send "{@prefix} You received your first warning. Reason below"
      send "{@prefix} %arg 2%"
      stop
     if {warning1::%uuid of arg 1%} is true:
      if {warning2::%uuid of arg 1%} is false:
       set {warning2::%uuid of arg 1%} to true
       send "{@prefix} You received your second warning."
       send "{@prefix} Third warning will be a kick and a cleared inventory."
       send "{@prefix} Reason: %arg 2%"
       stop
     if {warning1::%uuid of arg 1%} is true:
      if {warning2::%uuid of arg 1%} is true:
       if {warning3::%uuid of arg 1%} is false:
        set {warning3::%uuid of arg 1%} to true
        clear the inventory of arg 1
        stop
  else:
   send "{@noperm}"
   stop

 

[Deleted member 5254]

This code is very weird. You have "if arg 1 is set" twice, and you're not using else statements properly. When programming, if you want something to happen if an "if" statement DOESN'T go through, you can use "else" instead of just putting the opposite. So instead of doing this:

if arg 1 is set:
    <code>
if arg 1 is not set:
    <code>

You should do

if arg 1 is set:
    <code>
else:
    <code>

If you update your code to be like that, it will make it smaller and more readable, and help you track down errors better.

 

[Deleted member 5254]

This code is very weird. You have "if arg 1 is set" twice, and you're not using else statements properly. When programming, if you want something to happen if an "if" statement DOESN'T go through, you can use "else" instead of just putting the opposite. So instead of doing this:

if arg 1 is set:
    <code>
if arg 1 is not set:
    <code>

You should do

if arg 1 is set:
    <code>
else:
    <code>

If you update your code to be like that, it will make it smaller and more readable, and help you track down errors better.

Would you be willing to help me?
I happen not to understand this. You can call me stupid for that.

I'm pretty new to this. And i'm experimenting a lot but didn't get it to work yet.