VT Logo

Fourms {{|Tickets / Bug Reports Share Scripts Video Examples Permissions About VT

Make your own plugin like features and more using VariableTriggers

This is a very powerful plugin that has unlimited potential. Create triggers that run lines of script when a player Clicks or Walks on a block (dirt, door, switch, trigger, torch, any block) or Create Event Triggers such as PlayerDeath , EntityDeath, BlockBreak, BlockPlaced, Join, Quit, Respawn, Interact and EntitySpawn that also run scripts. You can define Area Triggers and Command Triggers as well. You can use Dynamic Object variables and conditional IF and ELSE statements in the scripts. You can run any command that a player or OP can run and many speacial built-in commands to Teleport, Spawn Entities, Play Effects Visual or Sound, Set Blocks, Toggle Blocks, Check Players Heath and much more!. The scripts are executed on their own threads to take the strain off of the main server thread.

Arrow Vault

Arrow Script Commands

Arrow Triggers

Arrow Place Holders

Arrow Functional Place Holders

Arrow Dynamic Objects

Arrow Scripts

Arrow In-Game Commands

Arrow Notepad++ UDL


You must login to post a comment. Don't have an account? Register to get one!

  • Avatar of Lyoko_Firelyte Lyoko_Firelyte Sep 01, 2014 at 22:40 UTC - 0 likes

    Neo, you can cancel and then test for stuff and broadcast your own messages accordingly.

        - '@CANCEL true'
        - '@IF si <chatline> ?= $<this>.word'
        - '@PLAYER You said test'
        - '@ELSE'
        - '@BROADCAST <playerdisplayname>: <chatline>'


  • Avatar of neomatamune neomatamune Sep 01, 2014 at 17:09 UTC - 0 likes

    @KyadCK: Go

    Then what is the use of it ? If we can't test if we want to cancel the event or not ?

    Because I thought that canceling an event when we don't want it to happen is great, but if we have to cancel it every time just for some conditions... it's not that usefull...

  • Avatar of KyadCK KyadCK Sep 01, 2014 at 17:06 UTC - 0 likes

    @neomatamune: Go

    @CANCEL only works if it is the very first line in the event.

  • Avatar of neomatamune neomatamune Sep 01, 2014 at 16:45 UTC - 0 likes

    Does anyone know on which events the @CANCEL command works ? Because I tried to use it to cancel Chat events so I can blacklist some words or just force people t write passwords without giving them to other people, but it doesn't want to work :s

    - '@SETSTR $<this>.word test'

    - '@IF s <chatline> ?= $<this>.word'

    - '@CANCEL true'

    - '@PLAYER &6You said test didn''t you ?'

    - '@ENDIF'

  • Avatar of AncientTom AncientTom Sep 01, 2014 at 01:00 UTC - 0 likes

    @JoelMinister: Go

    You are quite right. I'll start a thread in the forums tomorrow and post a link here.

    The reason I started posting my issues here is that no one hardly goes to the forums. There are postings in the forums and tickets submitted there that are over a year old without acknowledgement let alone being answered. That's why I started posting my issues here. Everyone lands on this page and most take interest as to what's being posted. Even a bad response is better than no response at all.

    Last edited Sep 01, 2014 by AncientTom
  • Avatar of JoelMinister JoelMinister Aug 31, 2014 at 23:18 UTC - 0 likes

    @AncientTom: Go

    I think we're spamming up the comment page here :P maybe start a thread and post a link to it on here and we'll carry on there?

  • Avatar of AncientTom AncientTom Aug 31, 2014 at 22:19 UTC - 0 likes

    I have just stumbled onto, again, the problem of using a variable to set an integer paramiter.
    @SETBLOCK $Door.Int1:$Door.Int2 <var:$Door.Location> I get must be integer message.
    @SETBLOCK <var:$Door.Int1>:<var:$Door.Int2> <var:$Door.Location> No error messages and no block modified by @SETBLOCK. This only works with hard codded integers.

    The last time I used @SETBLOCK for automating doors I had to create an eighty-three line subroutine to replace 4 lines of script to open and close a door because @SETBLOCK will not accept varibles. It would be nice if we could use variables here to.

    Last edited Aug 31, 2014 by AncientTom
  • Avatar of AncientTom AncientTom Aug 31, 2014 at 18:30 UTC - 0 likes

    @JoelMinister: Go

    I am beginning to feel like the boy who cried wolf with all the problems I have been having with VT. Some of them have been caused by assumptions and over sites on my part. When I start blogging for answers, it's only after I have exhausted all possibilities that I can think of. Sometimes there are things that I overlook, but that's why I come crying for help.

    My assessment, as it stands now, after a full day of trying every conceivable syntax variation, I have concluded in my mind that <signtext::> will not work using variables. Variables within <signtext::> do not get evaluated unless they are contained within a <var:> placeholder. The placeholder requires a space to be present before <var:>. <signtext::> does not allow spaces in the coordinates argument. Therefore the only way I have been successful in reading a sign is to hard code the statement, <signtext:-124,41,-579:3>. <signtext: -124, 41, -579:3> will not work. :(

    This is a very important addition to VT's arsenal if there were any way to use variables to pass arguments into it. Either removing the "space before" requirement for <var:>, have <signtext::> allow spaces in it's arguments, <signtext::> be able to evaluate the coords from a string variable, or get <signtext to accept variables without the need of wrapping them in a <var:> placeholder would fix this.

    Last edited Aug 31, 2014 by AncientTom
  • Avatar of AncientTom AncientTom Aug 31, 2014 at 17:55 UTC - 0 likes

    @JoelMinister: Go

    I have tried that several times and the only way I can get VT to evaluate the integers inside the variables is to wrap them in a <var:> placeholder and add a space before each <var:>. The problem is, that <signtext::> will not accept any spaces in the coordinates argument. Besides, you are feeding it a string and <signtext::> demands comma seperated integers.

    Last edited Aug 31, 2014 by AncientTom
  • Avatar of JoelMinister JoelMinister Aug 31, 2014 at 17:39 UTC - 0 likes

    @AncientTom: Go

    Im guessing you accidently look over at the last bit of my reply :P

    Instead of:
    - '@PLAYER Sign text = <signtext:$doors.SignX,$doors.SignY,$Doors.SignZ:3>'

    You'd have:
    - '@SETSTR $doors.SignCord $doors.SignX'
    - '@ADDSTR $doors.SignCord ,'
    - '@ADDSTR $doors.SignCord $doors.SignY'
    - '@ADDSTR $doors.SignCord ,'
    - '@ADDSTR $doors.SignCord $doors.SignZ'
    - '@PLAYER Sign text = <signtext:<var:$doors.SignCord>:3>'

    You may not need the <var:> surrounding the $doors.SignCord but give it a go :)


Date created
May 27, 2012
Last update
Aug 05, 2014
Development stage
  • enUS
All Rights Reserved
Curse link
Recent files