1. Welcome to skUnity!

    Welcome to skUnity! This is a forum where members of the Skript community can communicate and interact. Skript Resource Creators can post their Resources for all to see and use.

    If you haven't done so already, feel free to join our official Discord server to expand your level of interaction with the comminuty!

    Now, what are you waiting for? Join the community now!

  2. LOOKING FOR A VERSION OF SKRIPT?

    You can always check out our Wiki for downloads and any other information about Skript!

Dismiss Notice
This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

combat log help

Discussion in 'Skript' started by David, Aug 22, 2020.

Thread Status:
Not open for further replies.
  1. David

    David Member

    Joined:
    Jan 31, 2017
    Messages:
    16
    Likes Received:
    0
    I'm looking to do a combatlog in the script but the "on command" doesn't work for script commands, what do I do?
     
  2. Nikd0

    Nikd0 Active Member

    Joined:
    May 30, 2020
    Messages:
    204
    Likes Received:
    19
    http://en.njol.ch/projects/skript/doc/commands
    Code (Text):
    1. command /commandname <arguments>: # arguments are explained below
    2.     description: A description of what this command does
    3.     usage: How to use the command, e.g. /commandname <arguments>  # If omitted this defaults to something similar to how the command was defined above.
    4.     permission: required.permission.to.use.this.command  # If omitted this command can be used by everyone regardless of permissions.
    5.     permission message: Message to send if the player doesn't have the required permission to use this command  # If omitted this defaults to "You don't have the required permission to use this command"
    6.     executable by: players/console/players and console  # If omitted this command can be executed by players and the console.
    7.     aliases: /c, /comname. # a list of aliases of the command which are usually abbreviations of the command
    8.     trigger:
    9.         put conditions and effects here that will be checked/executed when the command is used.
     
    • Like Like x 1
  3. David

    David Member

    Joined:
    Jan 31, 2017
    Messages:
    16
    Likes Received:
    0
    so bro, I was talking about the "on command:" event and that it doesn't work for skript's own commands you know? :v
     
  4. Nikd0

    Nikd0 Active Member

    Joined:
    May 30, 2020
    Messages:
    204
    Likes Received:
    19
    So.. this doesn't work?
    Code (Text):
    1. on command "/skript help":
    2.     wait 3 ticks
    3.     send "&aInteresting... Is this the skript's help command?"
    Pay attention it will only detect "/skript help" - not "/sk help"
     
  5. David

    David Member

    Joined:
    Jan 31, 2017
    Messages:
    16
    Likes Received:
    0
    this event dont work for script commands, if a create one .sk the command of .sk dont is canceled in this event
     
  6. Nikd0

    Nikd0 Active Member

    Joined:
    May 30, 2020
    Messages:
    204
    Likes Received:
    19
    Yes, those commands probably can't be canceled, because you could cancel /sk reload command and then you'll be no longer able to reload plugins.
     
Thread Status:
Not open for further replies.

Share This Page

Loading...