-
-
Notifications
You must be signed in to change notification settings - Fork 407
Description
Description
Sorry if somebody already suggested this. I looked but could not find a similar one.
A global options file, placed in the main Skript directory, named something like global-options.sk
.
This file would be parsed before all others and could only contain options.
I like to separate out skripts quite a bit in order to keep them organised, and this defeats the point of "options" to some extent, given that I then have to change something six times rather than just one.
I propose that global options be written in a {!name}
format to use them.
Since the file would only be used for options, they could be written in the following format without the option tag.
While this feature isn't what I would call "necessary", it would be incredibly useful for changing static values quickly when you have a large number of skripts. It would also help to keep track of stuff.
If I wanted to change the "sample colours" of help messages across all my scripts, this would probably require individual edits (even a regex find and replace would be useless here). But if I had a global option set up for this, I could do it easily.
While lots of stuff can be done using variables, this is not always appropriate, and there are many situations where I would rather use options.
Sorts of things that global options would be great for:
- The server name
- Website link
- A certain variable that gets used a lot
- [for skript-mirror users] the NMS version for imports
- A very long static line that you use a lot
- A particular number/value that will be used a lot (such as version number, multiplication value, or a particular equation)
Just an Example
The following is an example of how somebody could use a global options file.
Their file layout:
server-name: SomethingCraft
message-color: §b
message-prefix: §6§l[Prefix]
balance-variable: {balance::%uuid of player%}
gamemode: Town Survival
member-permission: servername.member
my-version: 1.1.4
Some examples of usage in scripts:
send message "Welcome to {!server-name}'s {!gamemode} server." to player
message "Current game: {!gamemode}."
set {version} to {!my-version}
command /something:
permission: {!member-permission}
trigger:
add 6 to {!balance-variable}
send message "{!message-prefix}{!message-color} You have done this command!" to player