combat log help

  • 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!

  • LOOKING FOR A VERSION OF SKRIPT?

    You can always check out skUnity Downloads for downloads and any other information about Skript!

Status
Not open for further replies.

David

Member
Jan 31, 2017
16
0
1
20
I'm looking to do a combatlog in the script but the "on command" doesn't work for script commands, what do I do?
 
http://en.njol.ch/projects/skript/doc/commands
Code:
command /commandname <arguments>: # arguments are explained below
    description: A description of what this command does
    usage: How to use the command, e.g. /commandname <arguments>  # If omitted this defaults to something similar to how the command was defined above.
    permission: required.permission.to.use.this.command  # If omitted this command can be used by everyone regardless of permissions.
    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"
    executable by: players/console/players and console  # If omitted this command can be executed by players and the console.
    aliases: /c, /comname. # a list of aliases of the command which are usually abbreviations of the command
    trigger:
        put conditions and effects here that will be checked/executed when the command is used.
 
  • Like
Reactions: David
http://en.njol.ch/projects/skript/doc/commands
Code:
command /commandname <arguments>: # arguments are explained below
    description: A description of what this command does
    usage: How to use the command, e.g. /commandname <arguments>  # If omitted this defaults to something similar to how the command was defined above.
    permission: required.permission.to.use.this.command  # If omitted this command can be used by everyone regardless of permissions.
    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"
    executable by: players/console/players and console  # If omitted this command can be executed by players and the console.
    aliases: /c, /comname. # a list of aliases of the command which are usually abbreviations of the command
    trigger:
        put conditions and effects here that will be checked/executed when the command is used.
so bro, I was talking about the "on command:" event and that it doesn't work for skript's own commands you know? :v
 
So.. this doesn't work?
Code:
on command "/skript help":
    wait 3 ticks
    send "&aInteresting... Is this the skript's help command?"
Pay attention it will only detect "/skript help" - not "/sk help"
 
So.. this doesn't work?
Code:
on command "/skript help":
    wait 3 ticks
    send "&aInteresting... Is this the skript's help command?"
Pay attention it will only detect "/skript help" - not "/sk help"
this event dont work for script commands, if a create one .sk the command of .sk dont is canceled in this event
 
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.
 
Status
Not open for further replies.