Skip to main content

Write a permission-limited Skript command and reload one script

Use a small information command to learn Skript before adding purchases, inventory edits or scheduled world changes. This example sends text to its caller. You can remove it without changing player balances, locations or stored items.

Check the language and server versions

These instructions concern the SkriptLang Bukkit plugin on a supported server, rather than a client mod or an unrelated scripting engine. Read the release notes for the exact Minecraft, Java and server requirements. Documentation for a newer Skript release can include syntax that your installed release cannot parse. Record the versions from startup output before diagnosing a script.

Keep a copy of existing scripts and Skript data before editing. Choose a command name that no installed plugin uses. The example permission is a new node for this script; it does not grant access to any other plugin.

Add one script

  1. Open the panel file manager and find plugins/Skript/scripts/. Create community-info.sk, ensuring the editor does not append .txt.
  2. Paste the example below. Keep indentation consistent and preserve the colon after each structure.
  3. Save, then run skript reload community-info in the server console. In Minecraft chat, add a leading slash. Reload this file rather than the entire script collection.
  4. Read the complete reload result. Resolve the first reported line before treating later errors as separate problems.
command /communityinfo:
    permission: community.info
    permission message: You cannot use this command.
    trigger:
        send "Community information: ask staff for the rules link." to sender

Test the permission boundary

Use a normal, non-operator account. Run the command before granting the node and confirm denial. Give only the test group community.info through your permissions manager, repeat the command, and confirm the message reaches its caller. Remove the test grant afterwards if that group should not retain access. Do not grant skript.* to players: script-management access has a different purpose from using this command.

If the command appears unknown, check the filename, reload result and any duplicate command registration. If it runs with the wrong message, search your own scripts for the same command name. A successful parse confirms syntax, but the permission test confirms the behaviour players receive. Keep console access while testing, so a mistaken permission edit cannot lock you out.

Change or retire it

Edit only the message first and reload the same file. Check that a normal player sees the new wording. Keep commands that run as console, file operations and repeating loops out of this first script; they need a separate review of privileges and workload.

To retire the command, stop the server, move this script outside the active scripts directory, and start again. Preserve a copy for comparison. If an update causes parsing failures, restore the previous script and compatible plugin build from your saved set during a maintenance window. Avoid downloading random addons to silence an error without understanding which syntax the script requires.

back up the server files · review LuckPerms groups and inheritance

Official references

No comments to display