Solved List Variables in No Permission Messages

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

    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.

CormanYT

Active Member
Jan 6, 2018
122
5
18
I use a Skript Adddon (skript-yaml) to generate a YAML config. Then I converted those YML values to variables, like this one:
code_language.skript:
    set {iEssentials::config::no-permission-message} to yaml value "no-permission-message" from "config"
And then I have the variable called {iEssentials::config::no-permission-message}.

Now I want to be able to use it in this code:
code_language.skript:
    permission message: {iEssentials::config::no-permission-message}
Remember permission message in the config is &cYou do not have permission for this command!, and I want the permission message to be &cYou do not have permission for this command!.

My results:
{iEssentials::config::no-permission-message}
Results supposed to be:
&cYou do not have permission for this command!

If you don't understand I'll explain in more detail
 
Hmm I don't think it's a glitch. I just think it's something I need to fix.
 
1. If you use variables for that it defeats the whole purpose of the addon, just get the values directly.
2. Description, usage and permission message of a command doesn't support expressions in them, not now at least. I'll see if I can get it added for the next release of Skript.
 
1. If you use variables for that it defeats the whole purpose of the addon, just get the values directly.
2. Description, usage and permission message of a command doesn't support expressions in them, not now at least. I'll see if I can get it added for the next release of Skript.
That's incorrect, I use variables to save the yaml values so I can use them in other parts of the Skript easily.
[doublepost=1517683763,1517662925][/doublepost]Well, I guess I'll try an alternate way for permission message. Solved.
 
Status
Not open for further replies.