Script errors

Open Scripts and look at the Console tab. Errors are written there with the script name and line number.

A script does nothing

• It may be Off. Every new, imported and example script starts off.
• It may show Needs approval. It asks for more permissions than you approved. Choose Approve and allow.
• It may have been stopped after 10 failures in a row. Fix the error and turn it on again.
• SwizzinIRC may have been started with --no-scripts. See Starting with scripts disabled.

Errors you may see

Problem	Cause
A script written for a newer API is refused	The api value in the header is higher than this build supports
A callback is aborted	It ran longer than 250 ms or exceeded the 16 MB memory limit
The script’s top level is aborted	Loading took longer than 1 second. Move work into handlers
An unknown event name is an error	swizzin.on lists the valid event names in the message
A command cannot be registered	The name is a built-in command, one of theme, channels, scripts, script, or is already provided by another script
An action is refused	The permission was not approved, there was no network context, the text was empty, too long or multi-line, it looked like an authentication command, or the send rate limit was exceeded
Events are being dropped	The script is too slow to keep up with its 256-event queue. The Script Manager shows the count
Stopped (unresponsive)	The script stayed busy for 4 seconds

Imported .mrc scripts

Problems are listed with line numbers (up to 20). Unsupported features are refused rather than ignored. See mIRC compatibility.

A command does not run the script’s version

An enabled alias of the same name takes precedence over a script command, and built-in commands cannot be replaced. The Script Manager shows when an alias shadows a script command. Use /!name to run the built-in.