Things you probably didn't know were available in vanilla Skript

[Migins]

So I saw this skUnity thread and I thought it was really interesting so I thought I'd share it.

https://forums.skunity.com/threads/things-you-probably-didnt-know-were-available-in-vanilla-skript.8085/

Some cool stuff I got from it was:

Do If (Conditional Effects): Similar to the ternary, the do if effect allows you to execute an effect only if a condition passes. Note that this can be used to entirely replace if statements which only execute one line of code. Example: give a diamond to the player if {honor::%player's uuid%} > 50

Default Value: You can now in one line provide an alternative default value if the first value isn't set. Example: broadcast {score::%player's uuid%} otherwise "%player% has no score!". This only sends their score if their variable is set, otherwise sending the 2nd message.

Scripts: You can check if a specific script is loaded.

 

Continue: You can now use continue in a loop to skip to the next loop value.

Filters (skQuery Lambdas): Vanilla Skript supports filter statements just like skQuery's lambda which allow you to filter objects based on a condition. Some simple examples are send "congrats on being staff!" to all players where [player input has permission "staff"] or loop players in radius 10 of player where [player input isn't player].

Inventories: Skript has much more inventory support now (from many add-ons). You can:

• Detect inventory open, close, and click.
• Create inventories of any types which can be stored in variables (set {_inv} to a new chest inventory with 3 rows named "Shop" then open {_inv} to the player).
• Inventory click events let you get the type of click the user did (click type or click action), the action it will perform (inventory action), and the clicked slot and clicked inventory.
•  You can get the player's cursor slot, the player's current hotbar slot, get a slot by its index, and get the player's top-side (open) inventory

Note: There are probably other posts like these that are more recent, I just felt like sharing this one :).

 

[fewfrgy54]

This thread is quite old. Please consider starting a new thread rather than reviving this one.

 

[AgentGamerPro]

7 hours ago, fewfrgy54 said:

This thread is quite old. Please consider starting a new thread rather than reviving this one.

 

correct

[JoeShuvinsky]

This thread is quite old. Please consider starting a new thread rather than reviving this one.

[AgentGamerPro]

3 hours ago, JoeShuvinsky said:

This thread is quite old. Please consider starting a new thread rather than reviving this one.

w h y