Script Manager
Open the Script Manager with Scripts on the toolbar, or by typing /scripts. It contains:
- a list of your scripts with their state,
- a code editor,
- a Console tab showing
swizzin.logoutput and errors.
Working with scripts
Section titled “Working with scripts”| Action | What it does |
|---|---|
| Examples | Adds the sample scripts. They start off |
| New… | Starts a script from a template. It starts off |
| Save | Saves the script’s text |
| On / Off | Starts or stops the script |
| Approve and allow | Approves the permissions the script asks for and runs it |
| Revoke | Removes every approval and stops the script |
States
Section titled “States”- Off: not running. Every new, imported and example script starts here.
- On: running with the permissions you approved.
- Needs approval: the script asks for more than you approved, for example after an edit. It stays stopped until you approve again. A script that asks for less keeps working.
- Stopped (unresponsive): the script was busy for too long and was shut down; see Debugging.
Nothing runs when a file is opened, imported or previewed.
Console
Section titled “Console”The Console is separate from chat windows. Output is capped at 50 lines per callback, 1000 lines are kept, and values that look like passwords are masked. Notifications raised by a script always show the script’s name.
mIRC-style scripts
Section titled “mIRC-style scripts”Files ending in .mrc are translated to SwizzScript when loaded, and the editor lists any problems with line numbers as you edit. See mIRC compatibility.
Starting with every script off
Section titled “Starting with every script off”Start SwizzinIRC with --no-scripts, or set SWIZZIN_NO_SCRIPTS=1. See Starting with scripts disabled.