ziet iemand hier een fout in?

Discussion in 'Spigot Plugin Development' started by NickGamesYT, Apr 13, 2017.

Thread Status:
Not open for further replies.
  1. ik heb een skript plugin gemaakt maar er zitten alleen 18 fouten in volgens skript,
    kan iemand hem nakijken en kijken of er fouten in zitten?
    ik kan zelf geen fouten meer vinden
    het is een kingdom plugin
    dit is de code:
    options:
    LOGO: [<aqua>KINGDOM&3]

    on rightclick on sign:
    line 2 of event-block is "Kingdom 1":
    add player to {Kingdom1.spelers::*}
    add player to {Kingdom.spelers::*}
    execute console command "manuadd %name of player% Kingdom1"
    broadcast "{@LOGO}%name of player% heeft Kingdom 1 gejoind!"
    teleport player to {Kingdom1.spawn}
    command /kingdom <text> [<text>]:
    trigger:
    arg-1 is "setspawn":
    arg-2 is "Kingdom1"
    set {Kingdom1.spawn} to location of player
    message "<aqua> Kingdom 1 spawn gezet!" to player
    line 2 of event-block is "Kingdom 2":
    add player to {Kingdom2.spelers::*}
    add player to {Kingdom.spelers::*}
    execute console command "manuadd %name of player% Kingdom2"
    broadcast "{@LOGO}%name of player% heeft Kingdom 2 gejoind!"
    teleport player to {Kingdom2.spawn}
    command /kingdom <text> [<text>]:
    trigger:
    arg-1 is "setspawn":
    arg-2 is "Kingdom2"
    set {Kingdom2.spawn} to location of player
    message "<aqua> Kingdom 2 spawn gezet!" to player
    line 2 of event-block is "Kingdom 3":
    add player to {Kingdom3.spelers::*}
    add player to {Kingdom.spelers::*}
    execute console command "manuadd %name of player% Kingdom3"
    broadcast "{@LOGO}%name of player% heeft Kingdom 3 gejoind!"
    teleport player to {Kingdom3.spawn}
    command /kingdom <text> [<text>]:
    trigger:
    arg-1 is "setspawn":
    arg-2 is "Kingdom3"
    set {Kingdom3.spawn} to location of player
    message "<aqua> kingdom 3 spawn gezet!" to player
    on break of sign:
    line 2 is "Kingdom 1" OR "Kingdom 2" OR "Kingdom 3":
    cancel event
     
    #1 NickGamesYT, Apr 13, 2017
    Last edited: Apr 13, 2017
  2. This is an English forum, therefor you should talk English, and not Dutch.
     
    • Informative Informative x 2
  3. You should also format your code Like
    Code (Text):
    This
    Cuz rn its unreadable
    And its in the wrong section :p
     
  4. Yes, i am incluted That
     
  5. maldahleh

    Wiki Team

    • Informative Informative x 1
  6. I can't see them?
     
  7. i cand copy the text
     
  8. and screen shot not works
     
  9. error's:

    14:30:47 buh Client thread info [CHAT] Empty configuration section! You might want to indent one or more of the subsequent lines to make them belong to this section or remove the colon at the end of the line if you don't want this line to start a section. (kingdom.sk, line 5: line 2 of event-block is "Kingdom 1":')
    14:30:47 buh Client thread info [CHAT] indentation error: expected 2 tabs, but found '->____' [-> = tab, _ = space, ? = other whitespace] (kingdom.sk, line 12: trigger:')
    14:30:47 buh Client thread info [CHAT] indentation error: expected 2 tabs, but found '->->____' [-> = tab, _ = space, ? = other whitespace] (kingdom.sk, line 13: arg-1 is "setspawn":')
    14:30:47 buh Client thread info [CHAT] indentation error: expected 2 tabs, but found '->->->____' [-> = tab, _ = space, ? = other whitespace] (kingdom.sk, line 14: arg-2 is "Kingdom1"')
    14:30:47 buh Client thread info [CHAT] indentation error: expected 2 tabs, but found '->->->->____' [-> = tab, _ = space, ? = other whitespace] (kingdom.sk, line 15: set {Kingdom1.spawn} to location of player')
    14:30:47 buh Client thread info [CHAT] indentation error: expected 2 tabs, but found 5 tabs (kingdom.sk, line 16: message "<aqua> Kingdom 1 spawn gezet!" to player')
    14:30:47 buh Client thread info [CHAT] Empty configuration section! You might want to indent one or more of the subsequent lines to make them belong to this section or remove the colon at the end of the line if you don't want this line to start a section. (kingdom.sk, line 11: command /kingdom <text> [<text>]:')
    14:30:47 buh Client thread info [CHAT] Empty configuration section! You might want to indent one or more of the subsequent lines to make them belong to this section or remove the colon at the end of the line if you don't want this line to start a section. (kingdom.sk, line 17: line 2 of event-block is "Kingdom 2":')
    14:30:47 buh Client thread info [CHAT] indentation error: expected 2 tabs, but found '->____' [-> = tab, _ = space, ? = other whitespace] (kingdom.sk, line 24: trigger:')
    14:30:47 buh Client thread info [CHAT] indentation error: expected 2 tabs, but found '->->____' [-> = tab, _ = space, ? = other whitespace] (kingdom.sk, line 25: arg-1 is "setspawn":')
    14:30:47 buh Client thread info [CHAT] indentation error: expected 2 tabs, but found '->->->____' [-> = tab, _ = space, ? = other whitespace] (kingdom.sk, line 26: arg-2 is "Kingdom2"')
    14:30:47 buh Client thread info [CHAT] indentation error: expected 2 tabs, but found '->->->->____' [-> = tab, _ = space, ? = other whitespace] (kingdom.sk, line 27: set {Kingdom2.spawn} to location of player')
    14:30:47 buh Client thread info [CHAT] indentation error: expected 2 tabs, but found 5 tabs (kingdom.sk, line 28: message "<aqua> Kingdom 2 spawn gezet!" to player')
    14:30:47 buh Client thread info [CHAT] Empty configuration section! You might want to indent one or more of the subsequent lines to make them belong to this section or remove the colon at the end of the line if you don't want this line to start a section. (kingdom.sk, line 23: command /kingdom <text> [<text>]:')
    14:30:47 buh Client thread info [CHAT] Empty configuration section! You might want to indent one or more of the subsequent lines to make them belong to this section or remove the colon at the end of the line if you don't want this line to start a section. (kingdom.sk, line 29: line 2 of event-block is "Kingdom 3":')
    14:30:47 buh Client thread info [CHAT] indentation error: expected 2 tabs, but found '->____' [-> = tab, _ = space, ? = other whitespace] (kingdom.sk, line 36: trigger:')
    14:30:47 buh Client thread info [CHAT] indentation error: expected 2 tabs, but found '->->____' [-> = tab, _ = space, ? = other whitespace] (kingdom.sk, line 37: arg-1 is "setspawn":')
    14:30:47 buh Client thread info [CHAT] indentation error: expected 2 tabs, but found '->->->____' [-> = tab, _ = space, ? = other whitespace] (kingdom.sk, line 38: arg-2 is "Kingdom3"')
    14:30:47 buh Client thread info [CHAT] indentation error: expected 2 tabs, but found '->->->->____' [-> = tab, _ = space, ? = other whitespace] (kingdom.sk, line 39: set {Kingdom3.spawn} to location of player')
    14:30:47 buh Client thread info [CHAT] indentation error: expected 2 tabs, but found 5 tabs (kingdom.sk, line 40: message "<aqua> kingdom 3 spawn gezet!" to player')
    14:30:47 buh Client thread info [CHAT] Empty configuration section! You might want to indent one or more of the subsequent lines to make them belong to this section or remove the colon at the end of the line if you don't want this line to start a section. (kingdom.sk, line 35: command /kingdom <text> [<text>]:')
    14:30:47 buh Client thread info [CHAT] Empty configuration section! You might want to indent one or more of the subsequent lines to make them belong to this section or remove the colon at the end of the line if you don't want this line to start a section. (kingdom.sk, line 42: line 2 is "Kingdom 1" OR "Kingdom 2" OR "Kingdom 3":')
    14:30:48 buh Client thread info [CHAT] 'command /kingdom' is not an entity type (kingdom.sk, line 11: command /kingdom <text> [<text>]:')
    14:30:48 buh Client thread info [CHAT] 'command /kingdom' is not an entity type (kingdom.sk, line 23: command /kingdom <text> [<text>]:')
    14:30:48 buh Client thread info [CHAT] 'command /kingdom' is not an entity type (kingdom.sk, line 35: command /kingdom <text> [<text>]:')
    14:30:48 buh Client thread info [CHAT] [Skript] Encountered 18 errors while reloading kingdom.sk!
     
  10. {code}
    {/code}
    instead of {} use []

    so you get this
    Code (Text):

    easy
        to read
        and format
            wont break
     
     
  11. thanks for the information
     
  12. No problem :)
     
  13. Moeilijk hé, lezen? :)
     
  14. weet ik niet. jou mening...
     
  15. Please continue in English, this is an english forum. I've already told you what to do in dutch, so please do so.
     
  16. yes yes yes....
     
  17. Look at your pm's i will help you further.
     
Thread Status:
Not open for further replies.