-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integrate arma-manager module #1
Comments
Found a game queryer to solve all our problems: https://www.npmjs.com/package/gamedig |
So, this game query-er doesn't do anything except return information on the game server instance. I should have guessed from the name... Good for the |
Updated the feature list of commands |
For the servers to run independently of this driver, I need to add a pull request to add {
detached: true,
stdio: 'ignore'
} to https://github.com/Dahlgren/node-arma-server/blob/e1f1e75888491c4fcb330f25b61818ae7397609f/src/server.js#L112 and https://github.com/Dahlgren/node-arma-server/blob/e1f1e75888491c4fcb330f25b61818ae7397609f/src/headless.js#L71 |
Created our fork of arma-server for this: https://github.com/2bnb/node-arma-server |
What ================= Fixed: All the functions (start, stop and isAlive) to work properly. Issue ID: #1
What ================= Added: `status` command for Arma servers to be added to the list of servers displayed when the command is used, in addition to the image showing the server banner. Added: `updatePointers` command to add new arma server instances that were started from an unknown source, and remove instances that are no longer active. Issue ID: #1
What ================= Added: ArmaManager required configs to `config.json.sample`. Changed: arma-server npm package from the original to our own fork of the original. We may make a pull request to add in an option for detached spawning at some point. Why ================= We're using our own fork of arma-server because the original doesn't have a detached option: https://github.com/2bnb/node-arma-server. Issue ID: #1
I'm now changing the implementation from Dahlgren's ArmaManager to use the commandlines that FASTER outputs for use with it's profiles and mods. |
What ================= Changed the `arma-manager.js` implementation which wasn't working properly on the server for some reason, to now use the commandline exports that we get from FASTER. FASTER manages the server profiles and mod downloads for us, and whenever we start a server, it adds the commandline used to start the server to the clipboard. I've also managed to make the index.js code is completely independent of the module used. This means, that all functions that are used are able to be shared amongst these different modules without having to change the index.js code at all. This means I can treat the modules that are used to manage game servers as "drivers", which do the implementation specific logic, and exposes certain functionality under certain keywords: - start - stop Issue ID: #1
What ================= Improved: the logging and response messages on Discord for the commands that interact with the driver. Fixed: `stop()` command not finding the processes by PID before. Also, the profile specific kill commands now work properly. Issue ID: #1
Dahlgren implemented functionality that allowed easy starting of an arma 3 server (https://github.com/Dahlgren/node-arma-server). He doesn't necessarily allows stopping it, but it is supposed to return the PID of the executable! We can use that to stop and check if the process is running.
Otherwise, checking the port listener and then grabbing the PID related there is another option.
Controls to implement:
#restart
add_mod - Adds a mod to the start parameters of a particular serverremove_mod - Removes a mod from the start parameters of a particular serveradd_server_modremove_server_modThe text was updated successfully, but these errors were encountered: