To add a SConnector to the system, you must have either system-wide SC privileges or admin privileges on an SC. When you add a new SConnector, that SConnector will be available to every user who adds or edits an application within SCInterface. The following table describes the meaning of each field used in adding a SConnector.
| Field | Description |
| SConnector Name | The name used to identify the SConnector within SCInterface. |
| Version | The version number you would like to give this SConnector. You may choose to have the version number correspond with the game server's version number. |
| Default Executable | The name of the target executable for this program (assumed to be in the application's home directory). The SConnector start script will use this value to start the server. On a per-application basis you may specify the absolute path to the executable, if it differs from this standard. |
| Category | The category of the SConnector (GameServers, WebServices, Servers, etc). |
| Default Port | The default port that new applications of this type should listen on. This may be changed on the application level if desired. |
| Platform | The platform on which programs of this type will run. |
| Parent | The SConnector from which to inherit macros, config tokens, startup parameters, and alter configs. |
| Optional Fields |
| Scan Port | |
| Scan Command | The qstat command to run for applications of this SConnector type. |
| Private Pattern | String to look for in the output of qstat to see if the server is private. In most cases, this will include "password=" |