Skript How to Add a Var to a Mob and Access It Again

Dismiss Notice

This site uses cookies. Past continuing to use this site, you lot are like-minded to our utilise of cookies. Learn More.

General Skript Tutorial

• A very helpful tutorial to learn Skript. This was all written by Demon on the DBO forums before they got removed. LimeGlass modified some of it to be more grammatically right or to update to nowadays methods.

  Hello and welcome to Skript! Here yous can detect everything y'all need to become coding and brainstorm your first script!

  Downloads:
  1.7
  Skript 2.1.2 past Njol is the latest version that supports 1.vii https://dev.bukkit.org/projects/skript
  1.8
  Recommended (Mirreski 2.2, fixes v8b): Works, but not supported https://github.com/Mirreski/Skript
  1.9+
  Recommended (Bensku Fork, dev37c): Latest Bensku: http://github.com/bensku/skript/releases
  Actress Info
  Note that all versions of Skript not past Njol are unofficial and their problems should exist reported to their respective issue trackers.

  The original goal of Skript was to make a uncomplicated mode for non-programmers to make their own mini plugins (chosen scripts). I feel that this purpose has been lost due to the lack of understanding of how to script. This tutorial will teach even the newest person to Skript, how to make this wonderful plugin work on his or her server.

  Footstep i: Read over the documentation
  Njolbrim's website and skUnity have all of the expressions, atmospheric condition, furnishings and events that you will ever need on your server. I am non here to get over every unmarried one of these but I will reference them in talking about Commands and Variables. It is as well very helpful when yous are programing on your ain, so that you know the limitations of what you can exercise, every bit well as the syntax needed to get your task accomplished. Links can exist plant beneath;

  http://njol.ch/projects/skript/doctor

  https://bensku.github.io/Skript/ (updated Fork of Skript)

  http://skUnity.com/ (Recommended)

  Variables, Loops, Commands, Conditionals and Events
  During your time scripting for your server, you will undoubtedly employ at least one, if not all, of the 5 types mentioned in a higher place. Below I have outlined what each can do, equally well as how and when to employ them.

  Events
  Events are chosen when something happens. So when a player clicks on something, takes harm, dies, when a mob does something, or even when the environment does something else completely independent of entity interaction. This will allow you to make something happen when something else happens. For instance:

  
  Annotation the spacing. Every time there is a colon, then next line downwardly is indented one more. You lot can either use a tab or (four or viii) spaces. Y'all cannot use tabs and spaces to indent different lines of a script. I prefer to use the tab cardinal because I only need to hit it once per indent. The actual consequence in the code is pretty simple. When an explosion happens, it gets cancelled. This would be useful if you don't desire TNT, creepers, or even the enderdragon to destroy stuff on your server. Continue in listen that this cancels the actual explosion result, pregnant that players will not get hurt either. So this script is very uncomplicated when an explosion happens, it stops it from happening. You can easily alter the effect to be whatever you desire. Another example could be as dramatic as killing all players on the server.

  Conditionals
  Conditionals are an essential part of any script. They are pieces of code that cheque to see if a condition is met before executing the rest of the script/trigger. An example with permissions is below:

  2. role player has permission "Skript.blast"
  3.        create explosion with force 3 at targeted block
  6. if player has permission "Skript.smash":
  7.            create explosion with strength 3 at targeted block

  
  This will create an explosion that is slightly smaller than TNT, but information technology will only do and then if the player has the correct permission. Conditionals can besides be used to check things like if the histrion has an item in his/her inventory, or what a line on a sign says. You can fifty-fifty use multiple conditionals and so that an event has to encounter all of them earlier moving on.

  3.        line 1 of sign is "[Store]"
  4. histrion has permission "Skript.shop"
  5. histrion has 2 gilt nuggets
  6. remove 2 gilt nuggets from thespian
  8. message "<light green>You bought a staff of life."

  
  In this script the player must right click on a sign with the first line of "[Shop]", take the correct permission, and two gilt nuggets. So the furnishings occur. In this case the player will loose 2 gold nuggets and receive some bread. To learn more than visit the website above.

  Commands
  Every server admin knows about Commands, its the way you run your server. Skript allows yous to make your ain custom Commands. These Commands are very similar to events, except that you become to ascertain the event. The unproblematic version of this is that the event is activated whenever a role player types in the command that you define on the event line. To get a meliorate idea of what I'm talking about, look to the example beneath:

  
  This simple command sends a message to the histrion who typed the command. The kickoff line is the "event" line. Commencement we say that we want to define a command. then nosotros say what that command is. And so we requite it things like a permission and usage. Finally, we add together the trigger, which is what we want the control to practice assuming the player has permission to exercise then. You can check the website mentioned to a higher place for more info on defining parts of a command like the usage. Yous can also make more circuitous Commands that tin can get information, similar who yous want this control to bear on and then along. Expect to the example below to see what I hateful:This command will send the same bulletin equally before, but this time allows the player typing the command to send it to someone else as well. The reason we use the send consequence this time is because the message result only sends the message to the player in the result, i.e. the player who typed the control. With the send issue nosotros tin can send a message to someone. The argument is whatsoever was entered in the command. So if you typed "/how-do-you-do demon_penguin" and then the effect would be replaced with "ship "hi" to demon_penguin" thus sending the "howdy" message to me. Once again you can expect to the website to find out more about Commands.

  Loops
  Loops can be used to complete repetitive tasks that would otherwise be much more than complicated. For example if y'all wanted to run into if in that location was a breast near y'all, you would need to check every block in a sure altitude to run across if information technology was a breast. This can exist done very easily using a loop:

  3. loop blocks in radius 3 around histrion:
  5. message "In that location is a chest at %location of loop-cake%"

  The percent signs betoken that there is a value that will replace that role of the text. In this case there volition be an x, y, and z value instead of %location of loop-cake% The "loop-block" role of the code refers to whatever block the loop is checking. The loop will expect at every block inside a 3 block radius of the player and and so run the code we have indented under it. And because we are using a command to trigger the loop, nosotros can add together arguments and permit the player to choose how far the loop will search.

  1. command /chest < integer=3 >:
  3. loop cakes in radius statement effectually player:
  5. message "There is a chest at %location of loop-block%"

  Here we also set a default value for the command, just in case the player didn't enter one. In the loop expression we encounter the number has been replaced with "argument" This means that whatever number yous typed in the control will exist put here instead. If a number was non entered in this command, so three volition be used considering it was set up to be the default value. If you would like to see exactly how far a radius value is, then y'all can utilize this script to make a sphere out of blocks so you tin can visibly see the size.

  1. command /sphere < integer=iii >:
  3. loop blocks in radius argument around player:
  6. set { clear . cake } to location of thespian
  7. set { clear .radius} to argument
  11. loop blocks in radius { articulate .radius} effectually { clear . block }:

  The /clear command is and then that y'all can easily delete the sphere that you fabricated. As well considering you lot will be at the center of the sphere, y'all will need a way to teleport yourself out. These Commands may cause a minor amount of damage to your server if used close to the footing. Please utilize them while flying to get the full outcome. The parts of code with the curly brackets {} are called Variables. Y'all will learn nigh them in the side by side section. If yous desire to learn more than virtually Loops yous can check the website that was mentioned above.

  Variables
  Variables are used to store information under a name. Think of it like a box with a characterization on information technology. When you want to get the info yous put in that box, y'all just go look for the one with the correct characterization on it. Skript does the same thing with Variables, which are the computers equivalent of a box. You save information like this:

  set {variable.name.goes.here} to true

  Values for Variables can exist true/imitation, a location (x,y,z) or a plain old number. The reason for this is then that we can get this information afterward. So maybe nosotros want to check if a command was performed by this player before. Nosotros would practice information technology like so:

  3. set {home} to location of player
  7.                teleport actor to {home}

  Every fourth dimension a variable is used in a script you must must put it in curly brackets {} to tell Skript that you lot are using a variable. Above is a very simple abode script. We store the location of the actor in a box chosen {home} When the player types a unlike command similar "/dwelling" we go back to that variable to become the location out and so we know where to teleport the player likewise. This does non clear the value out of the box, it's more similar reading information technology, so putting it dorsum. When programming, you always need to think about what the user/role player could do incorrect. For example the player though that they sethome back in their base of operations, simply forgot to exercise then. What happens if they try and utilise /home and there is no where to teleport them to? That is when y'all use an if statement. This argument checks if something is the style it is supposed to be, and if it'due south not, then it will do something different than the rest of the script. At that place is no default mistake messages that volition be sent to the player, and so you will need to make your own.

  3. ready {home} to location of player
  8. bulletin "<red>You need to set a home commencement!"
  10.                teleport player to {home}

  Now if a player tries to do /home they will go an fault message and and so the rest of the trigger volition cease. If y'all forget to stop the trigger, then the rest of the events not indented under the if statement volition continue every bit normal. Also if the if statement is false, then none of the code indented under it will be read and the player volition not get an error message. The main problem with our current Skript is that if one person sets their home location under the {dwelling} variable, and so anyone who uses /home will exist sent to that persons home, and if someone sets their home after another player, it will override the other location and but save the newest one. The way to fix this is use expressions. These are things that volition exist inserted depending on who is triggering the consequence. In the instance of the command event, it is whomever typed the command. And so in lodge to ready a unlike home per player we can actually put the thespian'southward name in the variable itself. It looks like this:

  3. prepare {dwelling house.% actor % } to location of histrion
  7. if {home.% player % } is not set:
  8. message "<red>You need to prepare a home first!"
  10.                teleport player to {home.% thespian % }

  Now the player's name who set their home is in the variable. So when it checks if the variable is set, information technology will check {home.demon_penguin} for me and {home.whateveryouruseernameis} for everyone else. With this script every player will have their own home location.

  Closing Notes:
  Call up that all of the stuff y'all learned nether command section nigh if statements and stuff like that can be used in whatever trigger. This includes any result. And as a final reminder if you lot wan to learn more nigh what effects y'all tin can do and things like that, bank check out the documentation website higher up.

  If you have any questions virtually what I take said here, or have whatsoever kind of issue with a script, to ask on the help forum. http://dev.bukkit.org/server-mods/skript/forum/aid/

  - Demon

  Variables are picayune names we requite to store some data in. Recall solving for 'x' in your math class? Variables are simply like that, but the calculator does the solving!

  I like to think of Variables as boxes with a label. Then I'1000 going to put the number 5 in a box labeled {box} When I await at the contents of the box later, I'thou going to find the number v. I don't need to remember what is inside, as the calculator does all of that. All I need to practise is say what to do depending on the value of the variable (otherwise known as the contents of the box). For example I could say "If the contents of {box} is v and then kill all the players"

  Now that you know what Variables in general are, permit's talk almost what they tin do in Skript!

  Variables in Skript
  In well-nigh programming languages, Variables need to be declared, and can only be one type. (ie just a number or text ect) In Skript y'all tin can utilize a variable proper noun anywhere yous want, and if it doesn't exist, Skript volition create one of the blazon needed.

  All Variables in Skript have curly brackets around them "{}" And so on the inside yous put any you desire to phone call the variable (again its the aforementioned every bit putting a label on a box). Usually you will put a dot betwixt the proper name as such {this.is.a.variable.proper noun} However it is not required and you could employ spaces or whatever you would like except for '%' They accept their own special purpose.

  Nest Variables
  Nest Variables are when you put the value of an expression inside the variable name. An example could be :

  {variable.%player%}

  When Skript reads the variable, information technology will replace %player% with the name of the player. If you lot were to look in the Variables.csv file (You should probably never look in there only in case something gets messed up, but for the sake of the example, I'm going to tell you what you might observe) you would see

  {variable.Demon_Penguin}

  Skript would fill in the name of the player. In this case it was Demon_Penguin. This volition substantially make a separate variable per player, which is used in most scripts. Yous can also put the value of some other variable within a variable proper name similar this:

  {favorite.%{colour}%}

  If {color} was set to green, so yous would see {favorite.green}.

  There may also be situations where you need multiple expressions to refer to the same histrion. For case, in a loop, y'all may need to refer to loop-player to become the right player for a variable.

  Local Variables
  Local Variables are used when you but want to use a variable for a little bit and don't want/demand to save it. There can too exist multiple local Variables of the aforementioned name at the same time. This is useful for things similar log in events. While the code is executing for one player, some other thespian may log in and need their own variable. In order to tell Skript you want this variable to exist a local variable all y'all need to do is prefix the variable name with an _ Looks like this {_local} (Notation that you may see information technology used as '*' in older posts, nonetheless in newer versions of Skript the underscore _ is used)

  Selection Variables
  Choice Variables are a bit different from other Variables. Whatsoever time they are used in code, they are replaced past their value. They also cannot be modified by the lawmaking in any manner. Selection variable (unlike other Variables in Skript) demand to be declared. There is a section you tin can add (unremarkably at the pinnacle of the script) that declares the options and what their values are. They work almost similar a piddling config file, which is what most scripters use them for.

  In order to tell Skript that you lot are using an option variable (outside of the options section) you prefix the proper noun with the @ symbol. Looks similar this {@Name}

  List Variables
  List Variables are very special and complicated Variables. They tin hold an entire listing of values, and not all of them need to be the same type. Their usage ordinarily looks similar {list::*}

  Following my box instance, I will compare a list variable to a room full of boxes. The room is chosen by the name of the list variable, and the name of a box in the room is the stuff after the two colons. Whenever yous utilize the base proper noun of the variable (for example {list::*}) you are referencing the whole room. The different parts of list Variables are explained below:

  Alphabetize
  Warning: List Variables are by far the most complicated of all the variable types. But attempt using them if you lot feel y'all take a good agreement of the other variable types.

  Listing Variables take two parts to them: Their name (The name of the room) and the Index (The proper noun of a box in that room). All listing Variables (rooms) start off empty. And then lets start by learning how to put a box in that room.

  add the player to {list::*}

  What this does is creates a box that holds the player in the outcome. You may detect that we didn't tell Skript what to proper noun the box. All we told it to do was put it in the room we call {list::*}. Skript names these boxes by numbers. It starts at 1 and works its fashion upwards to infinity. And so the bodily name of the variable that is holding our player is "{list::1}" This works well when we really don't care what the box is called, but only the fact that it is in the room. For case, if nosotros had a variable that held all of the mods on the server, it doesn't affair if they are mod 1 or mod 2, just that they are on the moderator list. However, in many cases, yous will desire to be able to name every box in the room and so we know correct where to get information technology when we want to access it.

  All y'all need to do is set the name (The role after the colons) in the variable. You tin write it out, or you tin even utilise expressions to set up information technology for you:

  2. set {list::% player % } to true

  Find that nosotros no longer apply the 'add together' effect? This is because we are non only adding a box to the room (Which would give us the default number arrangement), but we are adding a box with a specific name. So we need to set that box's name to something, and give it a value. You lot can also use this method to access a specific box in the room (1 value out of a list variable) at any time in your code. This makes them work very similar to nested Variables.

  This technique allows for the quick deletion of a list of Variables. Rather than setting nested Variables to a value, you lot can do the same matter with a list variable, only it will exist prepare in such a way to be able to hands delete the unabridged list:

  ready {mod.%player%} to true # Old method
  set {mod.listing::%player%} to true #New method

  delete {mod.list::*} #When y'all use the * as the index it refers to the entire room, rather than a specific box

  Looping
  To commencement a loop of a list variable you start it off with:

  loop {listing::*}:

  What this does is check all the different boxes in that room, i past one.

  Now you take a few values to bargain with.

  • The loop-value is the value of the variable. Whatever is in that box.
  • The loop-alphabetize is what ever is after the colons for this particular box (ie the name of that box)

  Then you can deal with each value one by one every bit it Loops through each box.

  If you lot need help of any kind you should search through the help forum. If you lot can't find what you are looking for, then experience gratuitous to make your ain postal service.

  - Demon

  Syntax is the way that lawmaking is read. Skript will expect for certain things to figure out how to read the code. It is important that you lot know how this works so that all of your scripts volition piece of work the manner they are supposed to. Different aspects of Skript'south syntax are bear witness beneath.

  Indenting

  3.        line 1 of clicked block is "[Checkpoint]"
  4. set {checkpoint .% histrion % } to location of player
  5. message "Progress saved!"
  8. if {checkpoint .% player % } is not set up:
  11.        teleport player to {checkpoint .% player % }

  All indents tell Skript when to do something. 'On rightclick:' is an event that triggers when a role player right clicks, and and so runs all the code indented under it. An indent is either one tab or a stock-still amount of spaces. Yous tin only use one or the other for the unabridged script. You can however use tabs in i script and spaces in another, they just have to exist different files. I prefer to use tabs, considering they are quicker and just require 1 tap of the key per indent. Also annotation that when you copy paste scripts information technology volition paste them as spaces. And then if you copy part of your script and typed te rest with tabs, you volition accept to modify them to all tabs or spaces. Examples of when to indent and how many in that location should be are beneath:

  Commands

  1. command /commandname <args>:
  2.        description: This is an case control
  4.        usage: /commandname <args>
  6.                furnishings and conditionals go hither

  When y'all start whatever event, yous showtime with no indents. Every time afterward that you will ordinarily indent every time afterwards you use a colon. Commands are the simply exception. At the end of your command and arguments you lot put in a colon to signify that you are done with that line and can continue on. You indent after the colon like normal. And then yous add together things like description, permission and usage to the command. Fifty-fifty though these have a colon after them, you exercise not indent. When you accept added all that you would like to your Commands hither and are ready to add its effects, you type "trigger:" Now you are past the only irregularity and tin indent after each colon, which includes the one you just put after 'trigger'. Now you lot can add together furnishings and conditionals.

  Conditionals
  Any time you utilise a conditional you tin put a colon at the end of information technology. This will require yous to indent, just allow you to carve up out the effects. An example is shown below:

  3. if histrion has permission "Skript.case":
  4.                strike lightning at targeted block
  6.                strike lightning effect at targeted cake

  If the role player has the correct permission, the code under the conditional will be executed, in this case, striking lighting at the block the role player is looking at. The else, ways that if the previous conditional that used a colon was false, then do this instead. NOTE: Yous can have conditionals inside of other conditionals indenting one more than each time.

  When you are done with a section then indent one less to render to the previous grouping.

  Remember if you accept any questions, to search the aid forum as information technology may have already been answered!

  - Demon

  
  Specific Tutorials: These will give a more than in depth understanding of more specific parts of Skript:
  

  Creating Custom Commands
  Custom Commands tin can be some of the trickiest things to create. They tin can also be some of the most powerful. In this tutorial I am going to testify everything about Commands, and how to use them. Let'south start by defining what nosotros want the user to type when they execute this command:

  command /examination:

  We at present have fix a command called /test. But what if we desire the user to enter in more information? Things like a histrion name or a number. That is where we use arguments. Arguments are a lot like Variables, but but accept one value that changes each fourth dimension a command is executed. They are completely dependent on what the player types in. In order to add them to a command you enclose the type of statement with < and >

  control /test <player>:
  #And for multiple arguments
  command /exam <player> <number> <text>:

  Yous may also desire to brand an argument optional. That way the user doesn't have to type it in if they don't want or demand that argument for the control. For example, if you made a command that teleported you lot to spawn 1, spawn two, or spawn 3, and the user only wanted to type in /spawn to get them to spawn i. Rather than making them type /spawn i yous can merely go far optional, and default to i. Here's an example of what I'm talking about

  command /spawn [<number=1>]:

  The [ and ] around the argument get in optional (the user doesn't take to type it in) and and so we also requite information technology a default value so that we know what to do if the user doesn't type it in. Too know that if you lot use an optional text argument, that the default value should be in "

  command /test [<text="Example">]:

  This first line of defining a control ends with a : Because of that (and because it acts every bit our event) all subsequent lines need to be indented. The adjacent few lines are all about the options that our command will have. Things like a description, permission, and usage bulletin.

  2.    description: Description of what the command does
  3.    usage: The bulletin that comes upwards if the user types the command in incorrect
  4.    permission: The permission required to use this command
  5.    permission message: The message that appears if the user doesn't have the right permission
  6.    executable past: Who tin can apply this control? Players, console, or both?
  7.    aliases: Other names or shortcuts to this command

  If you read the tutorial on indentation, then you volition know that I mentioned that the only exception to the indent after colon rule was Commands. Well here it is. Each of these options ends with a colon, but only the trigger gets an indent. The only one of these options that is required is the trigger (it holds what the command actually does) The rest aren't necessary, merely can be useful in controlling aspects of the control. Now let's go one by ane, and get into more detail on each of these options

  - Description

  What does this control exercise? What is information technology's purpose? It is mostly for in code documentation, but it'southward adept to add anyhow

  - Usage

  How should the command look? This message will come up when someone types a command in incorrect. For instance, if the command wanted a number, but the user typed in "Rabbit" this message would come up. Information technology defaults to the arguments that you defined on the first line. It is used to brand the command a little bit more than readable. Instead of "/pay <role player> <number>" y'all could put "/pay <player> <amount>"

  - Permission

  This allows y'all to define a permission for the command. Past default in that location is no permission for these Commands, and then anyone tin can use them.

  - Permission bulletin

  Here you define what the message should be if the user doesn't have the permission you set earlier. There is a default message that will show if you don't include this option

  - Executable by

  Who can apply this command? The options are "players" "console" "console and players" Defaults to panel and players

  - Aliases

  Make some shortcuts to your Commands! You lot can add multiple aliases by separating them with commas "/h, /help, /helpmeout"

  - Trigger

  The most important part of any command, and the only pick here that is required. Nothing else goes on this line, only all the next lines need to exist indented once again. This block of lawmaking will define what the command should do when executed. Here is a completed example:

  1. command /help [ < number=one > ]:
  2.    clarification: Shows the help menus
  4.    permission: help.permission
  5.    permission message: &cYou don't take the help permission!
  6.    executable by: role playersouthward and console
  7.    aliases: /h, /helpmerightnow
  9. message "This is a help command!"

  Arguments
  At present nosotros know how to set a control, and where to add together the furnishings, but how do nosotros utilize the arguments (the data that the player entered in) in the trigger? If there is only i type of an argument you can reference information technology by using "arg <type>"

  arg player
  arg number
  arg text

  Alternatively you can apply the number of the argument. This is adamant by what lodge the arguments come in the command.

  1. command /test < number > < player > <text>:

  This command will display the arguments in gild one, 2, and so 3. The number, the histrion, then the text. Next is a list of all the argument types and a bit about how they are used

  • biome - Things similar SWAMPLAND or Forest. Note that when entering this into a command the biome names will need to be in all caps +
  • block - Dirt, sand, cobblestone. Any type of cake alias or ID will piece of work here +
  • boolean - true/on/yes or imitation/off/no
  • colour - Any of the colors you can use in Minecraft. Can also exist able to be spelled color
  • enchantment - Protection, sharpness, unbreaking Whatever of the enchantments in Minecraft +
  • enchantment type - Works the same every bit enchantment, merely has a level (sharpness 3) +
  • entity - Creeper, zombie, player Anything that moves/walks around
  • game mode - Survival/creative/adventure +
  • integer - A number without a decimal such as 1, 3, or 87
  • item - Any detail in the game. Could as well be a block in item form (Yous can also use 'cloth' instead of 'particular')
  • living entity - Aforementioned every bit entity but without projectiles and primed tnt. Something living
  • money - Some amount of money. Notation that the name of the currency must be included when executing this command (You should probably use number instead for this)
  • number - A number with a decimal like 2.v
  • offlineplayer - A role player that is maybe offline. Requires the player'southward verbal name
  • player - A player that is online. Requires only part of the player's proper name to be valid (similar using 'demon' instead of 'demon_penguin')
  • potion issue blazon - Any kind of potion upshot. Strength, slowness, haste, ect. +
  • projectile - Pointer, snowball, or thrown potion +
  • text - Any kind of text. The exactness of whatever the histrion typed in. Could exist annihilation
  • time - The Minecraft time. Anywhere between 00:00 to 23:59 +
  • timperiod - Aforementioned as time, simply tin utilize 'nighttime' 'day' 'dusk' and 'dawn' +
  • timespan - Some corporeality of time similar "iii seconds" "eight ticks" or "5 hours" Note that the unit must be typed when executing the control
  • treetype - Any type of tree or behemothic mushroom "giant red mushroom" "redwood tree" +
  • weather condition type - The type of weather "clear/sun/sunny, rain/rainy/raining, and thunder/thundering/thunderstorm" +
  • world - The name of a globe

  + ways that it is a valid blazon, simply I have non tested to brand sure that it works equally a command argument. If anyone has tested some of these you lot can pm me and I'll update the listing

  Post in the assistance forum with whatsoever questions, and on the tutorials forum if you have any improvements or suggestions for this tutorial

  - Demon

  Introduction
  This tutorial is mostly for those of you who do not exercise whatsoever programming outside of Skript. It explains the concept of Loops, likewise every bit examples of how the syntax looks in Skript.

  What Loops Are
  A loop is a chip of code that keeps repeating itself (aka looping) until a certain status is faux. Encounter this image For a visual representation of how this works.

  The status isn't very obvious in most of the Loops Skript provides.

  loop 10 times:
  broadcast "Hi"

  This code just runs (or Loops) 10 times. Then where'southward the condition? At that place is an expression called loop-number that holds the number of times the loop has run (starts with 1) The condition is: if loop-number is greater than ten. After the loop runs for the tenth time, loop-number becomes 11 and the condition becomes fake, and so the code moves on past the loop.

  Loops simply echo the lawmaking they are given. However, there can be slight differences each time. For instance, the loop-number expression is a different number each iteration (an iteration is one fourth dimension of running the loop code. The previous example would have 10 iterations). So what would happen if we broadcasted that number?

  loop x times:
  broadcast "%loop-number%"

  The output would be:

  1
  2
  iii
  4
  5
  6
  7
  8
  ix
  x

  As you can see, the loop did something slightly different in each of it's iterations. Now allow's have an case with players:

  loop all players:
  if {var.%loop-player%} is true:
  transport "You are true!" to loop-player
  else:
  send "You are non true!" to loop-player

  For this example, allow's say there are iii players: player1, player2, and player3. The loop starts with player1, checks the variable, and sends a message depending on the event. And so it does the same with player2 and player3. Now the loop is out of players, and continues on with whatever lawmaking subsequently the loop. If {var.player1} was true and {var.player2} was false, player1 would become the true message and player2 would get the simulated message. This is the principal advantage of Loops. They permit you to handle each object separately instead of all exactly the same.

  Looping List Variables
  List Variables accept the capability to agree many values. This means that y'all can loop through them! This is explained a bit more above in the Variable explanation.

  While Loops
  While Loops look much closer to that diagram I posted in a higher place. While other kinds of Loops go through a specified amount of objects before running out, a while loop could potentially run on forever. Just like other Loops, this will keep iterating until the condition is false. Make sure to add a wait 1 tick into the lawmaking or else the server will crash from the constant while loop.

  2.    strike lightning at histrion

  In this case the loop will proceed running and hitting the player with lightning with only a 10% adventure of stopping each fourth dimension. Any condition y'all tin can use with an if statement, you lot can utilize for a while loop.

  Hopefully this clears up some of the defoliation effectually Loops in Skript. Yous can send me a PM (LimeGlass) if you take any questions, or need some more explanation about Loops.

  - Demon

  
  Video tutorial at
  

  If you lot have whatever questions you tin can PM LimeGlass about anything.

larkincreent.blogspot.com

Source: https://forums.skunity.com/wiki/general-skript-tutorial/

Share this post