github.com/Southclaws/sampctl
The Swiss Army Knife of SA:MP - vital tools for any server owner or library maintainer.
sampctl is a command-line development tool for developing SA:MP Pawn scripts. It includes a package manager, a build tool and a configuration manager.
If that sentence meant nothing to you, don't worry! You'll probably find use in sampctl if you do anything related to the Pawn language. Below are some explanations of what the terms in bold above mean.
.inc files from solidfiles...For a quick-start guide, click this link!
As mentioned above, sampctl is a command-line development tool so it has no graphical user interface. The videos below show sampctl being used with Visual Studio Code which is a light-weight text editor that works very well with sampctl to provide the perfect SA:MP/Pawn development environment.
Always have the libraries you need. Inspired by npm.
Use on the command-line or integrate with any editor.
Easily write and run tests for libraries or quickly run arbitrary code. Utilise the power of Docker to run on any platform!
Quickly bootstrap new packages.
server.cfgManage your server settings in JSON or YAML format
Run the server from sampctl and let it worry about restarting in case of
crashes.
Automatically download Windows/Linux server binaries and plugins when and where you need them.
Installation is simple and fast on all platforms so why not give sampctl a try?
For a list of commands, click here.
Or visit the Wiki site for documentation on each feature..
sampctl is designed for both development of gamemodes/libraries and management of live servers.
Below is a quick overview of the best features that will help you develop faster.
If you've used platforms like NodeJS, Python, Go, Ruby, etc you know how useful tools like npm, pip, gem are.
It's about time Pawn had the same tool.
sampctl provides a simple and intuitive way to declare what includes your project needs. After that you simply let sampctl take care of the downloading and building.
If you release scripts, you know it's awkward to test even simple code. You need to set up a server, compile the include into a gamemode, configure the server and run it.
Forget all that. Just make a
pawn.json/pawn.yaml
in your project directory with sampctl package init and use
sampctl package install to get the includes you need:
{
"entry": "test.pwn",
"output": "test.amx",
"dependencies": ["pawn-lang/samp-stdlib", "Southclaws/formatex"]
}
Write your quick test code:
#include <a_samp>
#include <formatex>
main() {
new str[128];
formatex(str, sizeof str, "My favourite vehicle is: '%v'!", 400); // should print "Landstalker"
print(str);
}
Build with sampctl package build and run it with sampctl package run!
sampctl package run
Server Plugins
--------------
Loaded 0 plugins.
Started server on port: 7777, with maxplayers: 50 lanmode is OFF.
Filterscripts
---------------
Loaded 0 filterscripts.
My favourite vehicle is: 'Landstalker'!
You get the compiler output and the server output without ever needing to:
See documentation for more info.
Use JSON or YAML to write your server config:
{
"gamemodes": ["rivershell"],
"plugins": ["maddinat0r/sscanf"],
"rcon_password": "test",
"port": 8080
}
It compiles to this:
gamemode0 rivershell
plugins sscanf.so
rcon_password test
port 8080
(... and the rest of the settings which have default values)
What also happens here is maddinat0r/sscanf tells sampctl to automatically get
the latest sscanf plugin and place the .so or .dll file into the plugins/
directory.
See documentation for more info.
sampctl1.10.0 - Southclaws hello@southcla.ws
The Swiss Army Knife of SA:MP - vital tools for any server owner or library maintainer.
sampctlUsage: sampctl <subcommand>
For managing servers and runtime configurations.
sampctl initUsage: sampctl init
Bootstrap a new SA:MP server and generates a samp.json/samp.yaml configuration based on user input. If gamemodes, filterscripts or plugins directories are present, you will be prompted to select relevant files.
--verbose: output all detailed information - useful for debugging--platform windows: manually specify the target platform for downloaded binaries to either windows, linux or darwin.--bare: skip all pre-run configuration--version value: the SA:MP server version to use (default: "0.3.7")--dir value: working directory for the server - by default, uses the current directory (default: ".")sampctl downloadUsage: sampctl download
Downloads the files necessary to run a SA:MP server to the current directory (unless --dir specified). Will download the latest stable (non RC) server version unless --version is specified.
--verbose: output all detailed information - useful for debugging--platform windows: manually specify the target platform for downloaded binaries to either windows, linux or darwin.--bare: skip all pre-run configuration--version value: the SA:MP server version to use (default: "0.3.7")--dir value: working directory for the server - by default, uses the current directory (default: ".")sampctl ensureUsage: sampctl ensure
Ensures the server environment is representative of the configuration specified in samp.json/samp.yaml - downloads server binaries and plugin files if necessary and generates a server.cfg file.
--verbose: output all detailed information - useful for debugging--platform windows: manually specify the target platform for downloaded binaries to either windows, linux or darwin.--bare: skip all pre-run configuration--dir value: working directory for the server - by default, uses the current directory (default: ".")--noCache --forceEnsure: forces download of plugins if --forceEnsure is setsampctl runUsage: sampctl run
Generates a server.cfg file based on the configuration inside samp.json/samp.yaml then executes the server process and automatically restarts it on crashes.
--verbose: output all detailed information - useful for debugging--platform windows: manually specify the target platform for downloaded binaries to either windows, linux or darwin.--bare: skip all pre-run configuration--dir value: working directory for the server - by default, uses the current directory (default: ".")--container: starts the server as a Linux container instead of running it in the current directory--mountCache --container: if --container is set, mounts the local cache directory inside the container--noCache: forces download of pluginssampctl packageUsage: sampctl package <subcommand>
For managing Pawn packages such as gamemodes and libraries.
sampctl package initUsage: sampctl package init
Helper tool to bootstrap a new package or turn an existing project into a package.
--verbose: output all detailed information - useful for debugging--platform windows: manually specify the target platform for downloaded binaries to either windows, linux or darwin.--bare: skip all pre-run configuration--dir value: working directory for the project - by default, uses the current directory (default: ".")sampctl package ensureUsage: sampctl package ensure
Ensures dependencies are up to date based on the dependencies field in pawn.json/pawn.yaml.
--verbose: output all detailed information - useful for debugging--platform windows: manually specify the target platform for downloaded binaries to either windows, linux or darwin.--bare: skip all pre-run configuration--dir value: working directory for the project - by default, uses the current directory (default: ".")--update: update cached dependencies to latest versionsampctl package installUsage: sampctl package install [package definition]
Installs a new package by adding it to the dependencies field in pawn.json/pawn.yaml and downloads the contents.
--verbose: output all detailed information - useful for debugging--platform windows: manually specify the target platform for downloaded binaries to either windows, linux or darwin.--bare: skip all pre-run configuration--dir value: working directory for the project - by default, uses the current directory (default: ".")--dev: for specifying dependencies only necessary for development or testing of the packagesampctl package uninstallUsage: sampctl package uninstall [package definition]
Uninstalls package by removing it from the dependencies field in pawn.json/pawn.yaml and deletes the contents.
--verbose: output all detailed information - useful for debugging--platform windows: manually specify the target platform for downloaded binaries to either windows, linux or darwin.--bare: skip all pre-run configuration--dir value: working directory for the project - by default, uses the current directory (default: ".")--dev: for specifying development dependenciessampctl package releaseUsage: sampctl package release
Creates a release version and tags the repository with the next version number, creates a GitHub release with archived package files.
--verbose: output all detailed information - useful for debugging--platform windows: manually specify the target platform for downloaded binaries to either windows, linux or darwin.--bare: skip all pre-run configuration--dir value: working directory for the project - by default, uses the current directory (default: ".")sampctl package getUsage: sampctl package get [package definition] (target path)
Clones a GitHub package to either a directory named after the repo or, if the cwd is empty, the cwd and then ensures the package.
--verbose: output all detailed information - useful for debugging--platform windows: manually specify the target platform for downloaded binaries to either windows, linux or darwin.--bare: skip all pre-run configurationsampctl package buildUsage: sampctl package build [build name]
Builds a package defined by a pawn.json/pawn.yaml file.
--verbose: output all detailed information - useful for debugging--platform windows: manually specify the target platform for downloaded binaries to either windows, linux or darwin.--bare: skip all pre-run configuration--dir value: working directory for the project - by default, uses the current directory (default: ".")--forceEnsure: forces dependency ensure before build--dryRun: does not run the build but outputs the command necessary to do so--watch: keeps sampctl running and triggers builds whenever source files change--buildFile value: declares a file to store the incrementing build number for easy versioning--relativePaths: force compiler output to use relative paths instead of absolutesampctl package runUsage: sampctl package run
Compiles and runs a package defined by a pawn.json/pawn.yaml file.
--verbose: output all detailed information - useful for debugging--platform windows: manually specify the target platform for downloaded binaries to either windows, linux or darwin.--bare: skip all pre-run configuration--dir value: working directory for the server - by default, uses the current directory (default: ".")--container: starts the server as a Linux container instead of running it in the current directory--build --forceBuild: build configuration to use if --forceBuild is set--forceBuild: forces a build to run before executing the server--forceEnsure --forceBuild: forces dependency ensure before build if --forceBuild is set--noCache --forceEnsure: forces download of plugins if --forceEnsure is set--watch: keeps sampctl running and triggers builds whenever source files change--buildFile value: declares a file to store the incrementing build number for easy versioning--relativePaths: force compiler output to use relative paths instead of absolutesampctl package templateUsage: sampctl package template <subcommand>
Provides commands for package templates
sampctl package template makeUsage: sampctl package template make [name]
Creates a template package from the current directory if it is a package.
--verbose: output all detailed information - useful for debugging--platform windows: manually specify the target platform for downloaded binaries to either windows, linux or darwin.--bare: skip all pre-run configuration--dir value: working directory for the package - by default, uses the current directory (default: ".")--update: update cached dependencies to latest versionsampctl package template buildUsage: sampctl package template build [template] [filename]
Builds the specified file in the context of the given template.
--verbose: output all detailed information - useful for debugging--platform windows: manually specify the target platform for downloaded binaries to either windows, linux or darwin.--bare: skip all pre-run configurationsampctl package template runUsage: sampctl package template run [template] [filename]
Builds and runs the specified file in the context of the given template.
--verbose: output all detailed information - useful for debugging--platform windows: manually specify the target platform for downloaded binaries to either windows, linux or darwin.--bare: skip all pre-run configuration--version value: the SA:MP server version to use (default: "0.3.7")--mode value: runtime mode, one of: server, main, y_testing (default: "main")sampctl versionShow version number - this is also the version of the container image that will be used for --container runtimes.
sampctl completionoutput bash autocomplete code
sampctl docsUsage: sampctl docs > documentation.md
Generate documentation in markdown format and print to standard out.
sampctl helpUsage: Shows a list of commands or help for one command
--verbose: output all detailed information - useful for debugging--platform windows: manually specify the target platform for downloaded binaries to either windows, linux or darwin.--bare: skip all pre-run configuration--help, -h: show help--appVersion, -V: sampctl versionFAQs
Unknown package
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Socket’s threat research team has detected six malicious npm packages typosquatting popular libraries to insert SSH backdoors.
Security News
MITRE's 2024 CWE Top 25 highlights critical software vulnerabilities like XSS, SQL Injection, and CSRF, reflecting shifts due to a refined ranking methodology.
Security News
In this segment of the Risky Business podcast, Feross Aboukhadijeh and Patrick Gray discuss the challenges of tracking malware discovered in open source softare.