Search the Community
Showing results for tags 'manager'.
Found 2 results
AtlasServerUpdateUtility (ASUU) Latest version: v2.0.1 (2019-08-28) - Setup Wizard.. Easily transition your Atlas server to this utility! - Safe to try! Makes no direct changes to your Atlas files (unless Grid Configurator is used), so you can easily switch back to former launcher with ease. Please report bugs to my Discord or forum pages. Thank you! - Now with Blackwood map Support! (v1.9.9) - Works with up to 400 grids (20x20). - Works with multiple server / machine / computer systems. - Easy setup! Use Wizard or manually edit config. Imports almost all data from ServerGrid.json & GameServerUser.ini files (if enabled). - Setup Wizard: Use existing server or automatically download and install a new Atlas Dedicated Server. Requires a working map (ServerGrid.json). - Optionally start selected grid servers only. - Send RCON commands/messages to select or all servers. - Use custom command lines PER GRID during server startup. - Event Scheduler: Send RCON commands to All or Local grids or run any file at scheduled times. - Grid Configurator: Add or remove settings in GameUserSettings.ini, Game.ini, Engine.ini, ServerGrid.json across all grids with ease. Also view current grid settings with 1 click per grid. - Back Up: Backs up Atlas save & redis folders and ServerGrid files on a schedule. - Mod Updater: Keeps your mods up-to-date. Includes Discord, In-Game, and Twitch announcements. Restarts servers. - Updater: Automatically keeps server, mods, and itself updated if desired. - Announcements: Announces server updates and/or restarts in game, on Discord and Twitch. - Discord: Announce server status and crashes on any of 3 Discord Webhooks. - KeepServerAlive: Detects server crashes (checks for AtlasGame.exe via PID) and will restart the server. - Crash Watchdog: Monitors RCON response & restarts if crashed. Disables if crashes too many times. - Daily Restarts: User-defined scheduled reboots. - Remote Restart: (restart all grids with announcements) via web browser, including your phone. - Send RCON commands to all servers via web browser, including from your phone. - Run multiple instances of AtlasServerUpdateUtility to manage multiple servers. - Clean Shutdown: Your server(s) safely close via RCON "DoExit". If that fails, Clicks "X" (close) which both force a SaveGame. Also monitors save file to ensure saves started and completed. - Adjustable Startup and Shutdown delays. - Starts Freeport grids first. - Run files (your custom batch files) during any of 7 events, including server updates, mod updates, scheduled restarts, remote restart, when first restart notice is announced. - Duplicate Port Checker: Analyzes your ServerGrid.json for duplicate port entries. - DestroyWildDinos scheduler. Latest Stable Version: http://www.phoenix125.com/share/atlas/AtlasServerUpdateUtility.zip Latest BETA version: http://www.phoenix125.com/share/atlas/AtlasServerUpdateUtilityBeta.zip Previous Versions: http://www.phoenix125.com/share/atlas/atlashistory/ Readme.txt: http://www.phoenix125.com/share/atlas/readme.txt Website: http://www.phoenix125.com/AtlasServerUpdateUtil.html Forum: https://phoenix125.createaforum.com/general-discussion-26/ Source (GitHub): https://github.com/phoenix125/AtlasServerUpdateUtility Images: http://www.phoenix125.com/share/atlas/v1.9.4.png http://www.phoenix125.com/share/atlas/v1.9.4grid.png
OK not sure if this is posted already or even possible but hear me out. A server manager that shuts down grids not in use that way you can have a huge map on your local machine and still be able to play with just you or a few friends. Now this idea becomes less effective the more people you have. Basically have it set up that once all the grids are loaded they get put in "hibernation" (like suspended in ram or a paging file) and they stay that way until the server manager "pings" that grid which would bring it out of "hibernation" (the paging file) and resume the grid like normal. Now for example say you select a free port to spawn on, well when you click spawn the server manager would ping that grid and wake it up for you to use. Another example could be that once a player gets close to one or 2 grid walls then the server manager pings those grids and wakes them up so they are ready for you to pass over them by the time you get to the wall. And when the server sees that a gird is empty and no players are around it then it can close those grids. And the same situation could work for sleeping. Once you log out it checks the grid and surrounding grids and if all is good it will hibernate until needed.