Alambik Script User Guide
Alambik Script Editor
|Alambik Script User Guide|
We have worked hard to make the Alambik Script User Guide as practical and useful as possible. Should you encounter any problems, please report them on the relevant forum of the official Alambik Club board:
GENERAL TOPICS/User Guide for general comments, questions
Alternatively, you may contact us at the following email address: firstname.lastname@example.org
|Alambik Script Editor.|
Should you have any questions about the Alambik Editor, we invite you to share them with other Alambik scripters on the official Alambik Club board:
To report a bug, please select [Help]>[Create bug report] to assist
us in solving your problem. You need only fill out the bug report user
information once. All information can be modified later.
Although Alambik® Script is a natural scripting language, you may end up sooner or later scratching your head, wondering what went wrong with your coding. Should this happen, by all means don't panic! Keep your cool, take a deep breath, and follow these easy steps:
If your script succeeds in being "interpreted," this means it's syntax error-free. Of course, being free of errors doesn't mean that your script can't be further optimized! The interpreter cannot check for runtime errors such as "file not found" or "out of array." Click here for a complete list of Error Messages.
If you need information to aid in your debugging, you can use the following
instructions to display any strings or values in the output buffer of
Share your work with others:
Another great way to improve your script is to share it with other Alambik scripters. The Alambik community exchanges scripts (and other info) on the official Alambik Club board, as well as on many unofficial boards opening throughout the world (in the USA, Turkey, etc).
Here's a breakdown of the official Alambik Club board's main topics: