Adding and editing configurations

A configuration (from now on 'config') is a group of settings and preferences that will get applied to your developing environment.
This includes scripting directories, pre and post build commands, FTP and RCON credentials for instant plugin upload and load/reload, compiler flags, and more.

To access your configs, head to Configuration. You will find a list of all your available configs.
SPCode comes with a default config, with the (hopefully) latest SourcePawn compiler and set of includes to get you up and running out of the box.

Hitting Edit configurations leads you to the Configs window. Here you can add, edit or delete configs for you to use.

Adding and deleting configs

To add a config, press New at the top left corner to create a new config. Make sure to select it in the configs list box to edit it properly.
The same principle applies for deleting a config.

The inner parts explained

• Name: the name your config will have in the list on the left
• Scripting Directories: the list of the directories the editor will fetch and parse the includes from when writing and compiling
• Copy Directory: the place your compiled plugin will get copied to if you attempt to do it
• Server Executable: location of the server executable to run a local server
• Server-Start Arguments: the arguments to start the server with
• Pre-Build Commandline: any batch command you would like the editor to execute before compiling
• Post-Build Commandline: any batch command you would like the editor to execute after compiling
• Optimization Level: manages the optimization compiler switch
• Verbose Level: manages the verbose compiler switch
• Auto Copy after Compile: whether to automatically copy the plugin to the specified location after compiling it successfully
• Delete old .smx after copy: whether to automatically delete an existing plugin with the same name before copying it
• Upload .smx after Compile: whether to automatically upload the compiled plugin to the specified location through FTP
• Send RCON Commands after Compile: whether to automatically send the specified RCON commands after compiling
• FTP Host: the FTP host - must follow the ftp://(your-hostname-here)/ format
• FTP User: self-explanatory
• FTP Password: self-explanatory
• FTP Directory: the FTP directory your plugin will get uploaded to
• RCON Server Engine: select between Source and GoldSrc
• RCON Server IP: your server's IP - place localhost if you're working in your locally executed server
• RCON Server Port: your server's port
• RCON Password: your RCON password
• RCON Commands: the commands you would like the editor to send to the server

Some info and tips regarding configs

• In the pre/post commandlines and in RCON commands, you have a small dropdown text box with useful placeholders that will get replaced with the corresponding information. The list is read only, for now you must write them yourself
• The editor will attempt to output any information or issue for you to know regarding configs configuration in the logging box in the bottom right corner of the editor
• You are not able to exit the Configs window normally if you either have 2 configs or more with the same name, or any config with an empty name.
• You are not able to delete the default config that comes with SPCode. This is only doable by modifying the XML file that contains the configs structure (not advisable).
• If you use a config whose scripting directories are missing the SourcePawn compiler, the program will show an error when trying to compile a script.
• If you add a scripting directory SPCode has either limited or no access to, it will warn you about not being able to parse the includes from that directory, which translates to them not being part of autocomplete, or not being included for compilation (which will throw an error).