Gamer Hosting: Useful Software KiwamiServer Setup Guide for [Barotrauma] Gamers
Game Server Requirements
Setting up a dedicated server for Barotrauma necessitates a careful consideration of hardware and software specifications to ensure a stable and enjoyable multiplayer experience. The demands placed upon a server can fluctuate significantly based on the number of concurrent players, the complexity of the in-game environment, and the frequency of physics calculations. Unlike many other game genres, Barotrauma's intricate physics engine, which simulates water pressure, structural integrity, and object interactions within a submarine, places a unique burden on server resources.
At a foundational level, the central processing unit (CPU) is paramount. A multi-core processor with a high clock speed is generally recommended. While Barotrauma may not fully saturate all available cores, a strong single-core performance is often beneficial for game server applications, as many game logic operations are inherently sequential. For a modest server accommodating 4-8 players, a modern quad-core CPU (e.g., Intel i5 or AMD Ryzen 5 equivalent or better) is a reasonable starting point. As player counts increase, or if numerous mods are introduced, an upgrade to a six-core or even eight-core CPU becomes advisable to prevent bottlenecks and maintain smooth gameplay. The server's ability to process game state updates, player inputs, and environmental changes directly correlates with CPU power.
Random Access Memory (RAM) is another critical component. Barotrauma servers, especially those with custom content or larger player groups, can consume a significant amount of memory. A minimum of 8 GB of RAM is typically recommended for a small server. However, for a more robust setup supporting 10+ players or extensive mod usage, 16 GB or even 32 GB of RAM will provide ample headroom, preventing the server from resorting to slower disk-based virtual memory. Insufficient RAM can lead to frequent server freezes, desynchronization issues, and overall poor performance, as the server struggles to keep all necessary game data readily accessible.
Storage solutions also play a vital role in server responsiveness. While the core Barotrauma game files are not excessively large, the speed at which these files, as well as save data and log files, can be accessed directly impacts server startup times and the loading of new game rounds. Solid-State Drives (SSDs) are overwhelmingly preferred over traditional Hard Disk Drives (HDDs) due to their significantly faster read/write speeds. An NVMe SSD offers the highest performance, though a standard SATA SSD will still provide a substantial improvement over an HDD. A minimum of 100 GB of storage is generally sufficient for the operating system, game files, and a reasonable amount of save data, but allocating more space for future expansion and logging is prudent.
Network connectivity is arguably as crucial as computational power for any online game server. A stable, high-bandwidth internet connection with low latency is indispensable. Both upload and download speeds are important, but upload speed is particularly critical for a server, as it must transmit game state updates to all connected clients. A dedicated internet connection with a minimum symmetrical speed of 50 Mbps (megabits per second) is a good baseline for a small to medium-sized Barotrauma server. For larger communities or those expecting peak traffic, 100 Mbps or higher is highly recommended. Furthermore, a stable connection minimizes packet loss, which can lead to "rubberbanding" and other frustrating desynchronization issues for players. The server's physical proximity to the majority of its player base can also influence latency, making geographical location a factor in hosting decisions.
Finally, the operating system (OS) choice is typically between Windows Server editions and various Linux distributions. While Barotrauma can run on both, Linux distributions like Ubuntu Server or Debian are often favored in professional hosting environments due to their lower resource overhead, enhanced security features, and greater flexibility for command-line management. However, Windows Server offers a more familiar graphical user interface for those less comfortable with command-line operations. Regardless of the OS, it must be kept updated with the latest security patches and system drivers to ensure optimal performance and mitigate vulnerabilities. The server software itself, provided by the game developers, will dictate the specific OS compatibility.
In summary, a robust Barotrauma server requires a balanced allocation of CPU power, ample RAM, fast storage, and a reliable, high-speed internet connection. Overlooking any of these components can lead to a suboptimal experience for players, characterized by lag, desynchronization, and frequent disconnections.
Beginner's Guide
Embarking on the journey of hosting your own Barotrauma server can seem daunting at first, but with a structured approach, even novices can establish a functional and enjoyable multiplayer environment. This guide will walk you through the essential steps, from initial setup to basic configuration, ensuring a smooth launch for your Europa expeditions.
The very first step involves acquiring the Barotrauma dedicated server files. These are typically distributed through the Steam client. Navigate to your Steam library, and under the "Tools" category, you should find "Barotrauma Dedicated Server." Install this application just as you would any other game. This installation will place the necessary server executable and associated files onto your chosen drive. It is crucial to install this on the machine designated to be your server, whether it's a home PC or a rented virtual private server (VPS).
Once the server files are installed, the next critical phase is configuring the server. This is primarily done through a configuration file, often named serversettings.xml or similar, located within the server's installation directory. This XML file contains various parameters that dictate the server's behavior, such as the server name, maximum player count, game mode, and password ( XML in a Nutshell ). Open this file with a plain text editor (e.g., Notepad on Windows, Nano or Vim on Linux).
Key parameters to configure include:
After saving your serversettings.xml file, the next hurdle is network configuration, specifically "port forwarding." This step is essential if you are hosting the server on a machine behind a router in a home network. Port forwarding instructs your router to direct incoming connections on a specific port (e.g., 27015) to the internal IP address of your server machine. The exact steps for port forwarding vary significantly between router models, but the general process involves:
Accessing your router's administration interface (usually via a web browser, by typing your router's IP address, e.g., 192.168.1.1).
Logging in with your router's credentials.
Navigating to a section typically labeled "Port Forwarding," "NAT," or "Virtual Servers."
Creating a new rule that forwards TCP and UDP traffic on the Barotrauma server port (default 27015) to the internal IP address of your server machine.
Saving the changes and restarting your router if prompted.
It is crucial that your server machine has a static internal IP address, or that you configure a DHCP reservation on your router, to prevent its IP from changing, which would break the port forwarding rule. If you are using a hosting service, port forwarding is typically handled by the provider or is not necessary as the server is directly accessible on the internet.
With the configuration file saved and port forwarding established (if applicable), you can now launch the server. Navigate to the server's installation directory and execute the BarotraumaServer.exe (on Windows) or the equivalent executable (on Linux). A console window will appear, displaying server logs and status messages. If everything is configured correctly, you should see messages indicating the server starting up and listening for connections.
To verify that your server is accessible, launch the Barotrauma game client on a separate machine (or the same machine, though this is not ideal for performance). Go to the "Multiplayer" section and then "Join Server." You can try to find your server by its name in the server browser, or directly connect using your public IP address (which you can find by searching "what is my IP" on a search engine) followed by the port (e.g., your.public.ip.address:27015). If you can connect, congratulations, your server is operational!
For ongoing management, the server console window provides real-time feedback. You can issue commands directly into this console to manage players, change game settings, or perform administrative tasks. Familiarize yourself with common server commands, which are usually documented on the Barotrauma wiki or community forums. Regularly backing up your server's save files is also a highly recommended practice to prevent data loss. This beginner's guide provides the fundamental steps to get your Barotrauma server running, laying the groundwork for more advanced customization and community building.
Hosting Service Comparison and Recommendations
Selecting the optimal hosting service for your Barotrauma server is a pivotal decision that directly impacts performance, reliability, and overall cost. The landscape of game server hosting is diverse, ranging from shared hosting to dedicated servers, each with its own set of advantages and disadvantages. For Barotrauma, a game with intricate physics and a persistent campaign, the choice of host can significantly influence the player experience.
Shared Hosting (Game Server Providers - GSPs): These services are specifically tailored for game servers. Providers like Nitrado, GPORTAL, or Survival Servers offer pre-configured Barotrauma server instances.
Pros:
Ease of Use: GSPs typically provide a user-friendly web-based control panel (e.g., TCAdmin, Pterodactyl) for managing server settings, installing mods, and performing backups, requiring minimal technical expertise.
Instant Setup: Servers are often deployed almost instantly after purchase.
Optimized Infrastructure: GSPs often use hardware and network configurations optimized for gaming, including DDoS protection.
Support: Dedicated customer support is usually available to assist with server-related issues.
Cons:
Resource Sharing: The primary drawback is that your server shares resources (CPU, RAM, network bandwidth) with other customers on the same physical machine. This "noisy neighbor" effect can lead to performance degradation during peak times if other servers on the same host are resource-intensive.
Limited Customization: While control panels offer many options, direct access to the underlying operating system is usually restricted, limiting advanced customization or the installation of non-standard software.
Cost: While seemingly affordable for basic packages, the cost per resource unit can be higher than self-hosting on a VPS or dedicated server, especially for larger player counts.
Recommendations: Ideal for beginners, small friend groups (4-8 players), or those who prioritize convenience over absolute control and maximum performance. Look for providers with a good reputation for Barotrauma specifically, as some GSPs optimize better for certain games.
Virtual Private Servers (VPS): A VPS provides a virtualized slice of a physical server, offering dedicated resources (CPU cores, RAM, storage) within that virtual environment. Providers include DigitalOcean, Linode, Vultr, and OVHcloud.
Pros:
Dedicated Resources: Your VPS is allocated a specific amount of CPU, RAM, and storage, ensuring consistent performance without interference from other users on the same physical machine.
Root Access: Full root or administrator access allows for complete control over the operating system, enabling advanced customization, installation of any software, and fine-tuning of server parameters.
Scalability: Many VPS providers offer easy upgrades to higher resource tiers as your server's needs grow.
Cost-Effectiveness: Often more cost-effective than GSPs for servers with moderate resource requirements, especially if you are comfortable with server administration.
Cons:
Technical Expertise Required: Setting up and managing a VPS requires a solid understanding of Linux command-line interfaces (or Windows Server administration), network configuration, and security practices.
Self-Management: You are responsible for all aspects of server maintenance, including OS updates, security patches, and backups.
No Game-Specific Support: While the VPS provider supports the virtual machine, they do not offer support for Barotrauma itself.
Recommendations: Best for users with some technical proficiency, medium-sized communities (8-16 players), or those who desire greater control and flexibility. Look for VPS providers with good network uptime, low latency to your player base, and competitive pricing for CPU and RAM.
Dedicated Servers: A dedicated server provides an entire physical machine exclusively for your use. Providers are similar to VPS providers but offer bare metal machines.
Pros:
Maximum Performance: Unparalleled performance as all hardware resources are dedicated solely to your Barotrauma server.
Complete Control: Full control over hardware, operating system, and software stack.
High Player Counts: Ideal for very large communities or servers running numerous resource-intensive mods.
Cons:
Highest Cost: Significantly more expensive than VPS or shared hosting.
Advanced Technical Expertise: Requires advanced system administration skills to manage hardware, OS, and network.
Maintenance: You are responsible for all hardware and software maintenance.
Recommendations: Suitable for large communities (16+ players), professional esports teams, or those who demand the absolute highest performance and have the technical expertise and budget to manage it.
Self-Hosting (Home PC): Running the server on your personal computer or a spare machine at home.
Pros:
Free (Hardware Dependent): No recurring hosting fees if you already own the hardware.
Full Control: Complete control over the hardware and software.
Cons:
Reliability: Dependent on your home internet connection's stability and upload speed, which are often inferior to data center connections ( Computer Networks ).
Power Consumption: Your machine must run 24/7, incurring electricity costs.
Security Risks: Requires careful network configuration (port forwarding) and security measures to protect your home network.
Performance: Performance is limited by your home PC's hardware and network.
Recommendations: Only for very small, private groups of friends (2-4 players) or for testing purposes. Not recommended for public or large-scale servers due to reliability and performance limitations.
When making a decision, consider the following factors:
Budget: How much are you willing to spend monthly?
Technical Skill Level: Are you comfortable with command-line interfaces and server administration?
Player Count: How many players do you anticipate hosting concurrently?
Mod Usage: Will you be running many resource-intensive mods?
Geographical Location: Choose a data center geographically close to the majority of your player base to minimize latency.
Support: What level of support do you expect or require?
For most Barotrauma enthusiasts looking to host a community server, a well-provisioned VPS offers the best balance of performance, control, and cost-effectiveness. For those less technically inclined, a reputable GSP provides a hassle-free entry point.
Troubleshooting
Even the most meticulously configured Barotrauma server can encounter issues. Effective troubleshooting involves a systematic approach to identify, diagnose, and resolve problems, ensuring minimal downtime and a consistent player experience. This section outlines common server problems and their respective solutions.
1. Server Not Appearing in In-Game Browser: This is a frequent initial hurdle.
Diagnosis: The server starts successfully, but players cannot find it in the Barotrauma server list.
Potential Causes & Solutions:
Port Forwarding Issues: If self-hosting, verify that TCP and UDP ports (default 27015) are correctly forwarded on your router to the server's internal IP address. Use an online port checker tool to confirm the port is open to the internet.
Firewall Blockage: Ensure that the operating system's firewall (e.g., Windows Firewall, ufw on Linux) is not blocking incoming connections to the Barotrauma server executable. Create an inbound rule to allow traffic on the specified port.
Incorrect Public IP: Players might be trying to connect to an incorrect public IP address. Confirm your server's public IP.
Server Browser Lag: Sometimes, the in-game server browser can take time to refresh. Wait a few minutes and try again.
Server List Registration Failure: Check the server console logs for any errors related to registering with the Barotrauma master server. This could indicate a network issue or a problem with the server software itself.
2. Players Cannot Connect (Connection Timed Out/Failed): Players receive an error message indicating they cannot establish a connection.
Diagnosis: The server is running, but connection attempts fail.
Potential Causes & Solutions:
Firewall: Re-check both router port forwarding and OS firewall settings. This is the most common culprit.
Incorrect IP/Port: Players are using the wrong IP address or port. Double-check and communicate the correct details.
Server Not Running: Confirm the BarotraumaServer.exe process is actively running on the server machine.
Network Congestion: High network traffic on either the server's or the player's end can cause timeouts.
DDoS Attack: While less common for small servers, a Distributed Denial of Service attack can overwhelm the server's network capacity. Hosting providers often offer DDoS protection.
3. High Latency (Lag) and Desynchronization: Players experience "rubberbanding," delayed actions, or inconsistent game states.
Diagnosis: The game feels unresponsive, and actions don't register correctly.
Potential Causes & Solutions:
Insufficient Bandwidth: The server's upload speed is inadequate for the number of players. Upgrade your internet plan or consider a hosting service with higher bandwidth.
CPU Bottleneck: The server's CPU is struggling to process game logic and physics calculations. Monitor CPU usage; if consistently high, an upgrade or fewer players might be necessary.
RAM Exhaustion: The server is running out of RAM, forcing it to use slower disk-based virtual memory. Monitor RAM usage; if near capacity, increase RAM ( Computer Organization and Design: The Hardware/Software Interface ).
Geographical Distance: Players far from the server's physical location will naturally experience higher latency. There's no direct fix for this other than choosing a server location closer to the player base.
Mod Conflicts/Inefficiencies: Poorly optimized mods can significantly increase server load. Try disabling mods one by one to identify the culprit.
Network Issues: Packet loss or instability on the server's or player's network path. Use ping and traceroute commands to diagnose network path issues.
4. Server Crashes or Freezes: The server process unexpectedly terminates or becomes unresponsive.
Diagnosis: The server console closes, or the game becomes unplayable for all connected clients.
Potential Causes & Solutions:
Memory Leaks: Some mods or even the game itself can have memory leaks, gradually consuming more RAM until the system runs out. Regularly restart the server, especially after long uptime periods.
Software Bugs: Game updates or specific mod interactions can introduce bugs that cause crashes. Check official forums and bug trackers.
Hardware Failure: (For self-hosted or dedicated servers) Faulty RAM, an overheating CPU, or a failing storage drive can cause instability. Monitor hardware temperatures and health.
Corrupt Save Files: A corrupted campaign save can prevent the server from loading or cause crashes during gameplay. Try starting a new campaign to rule this out. Regularly back up save files.
Out-of-Date Software: Ensure the Barotrauma server software, operating system, and drivers are all up to date.
5. Mod-Related Issues: Problems arise after installing or updating mods.
Diagnosis: Server fails to start, crashes, or exhibits unexpected behavior after mod changes.
Potential Causes & Solutions:
Mod Conflicts: Two or more mods are incompatible and interfere with each other. Install mods incrementally, testing after each addition.
Outdated Mods: Mods not updated for the current Barotrauma version can cause issues. Ensure all mods are compatible.
Incorrect Installation: Mods might not be placed in the correct directory or enabled properly in the server configuration.
Resource Overload: Too many complex mods can push the server beyond its hardware limits.
Corrupt Mod Files: Re-download and reinstall problematic mods.
General Troubleshooting Best Practices:
Check Logs: The server console and log files (usually in a Logs directory) are invaluable resources. Error messages often provide direct clues.
Isolate the Problem: Change one variable at a time (e.g., disable one mod, change one setting) to pinpoint the cause.
Consult Community Resources: The official Barotrauma forums, Discord servers, and wikis are excellent places to find solutions to common problems.
Restart: A simple server restart can often resolve transient issues.
Backups: Always maintain regular backups of your server configuration and save files.
By systematically approaching troubleshooting with these guidelines, you can effectively diagnose and resolve most Barotrauma server issues, ensuring a smooth and enjoyable experience for your players.
Performance Optimization Tips
Achieving optimal performance for your Barotrauma server is crucial for a fluid and immersive multiplayer experience, especially given the game's demanding physics engine. Optimization involves a combination of hardware considerations, software configurations, and in-game management strategies. The goal is to minimize latency, prevent desynchronization, and maintain a high frame rate for the server's internal simulation.
1. Hardware & Infrastructure Optimization:
Prioritize CPU Clock Speed: While multi-core CPUs are common, Barotrauma's server logic often benefits significantly from higher single-core clock speeds. When selecting a CPU for a dedicated server or VPS, prioritize processors with strong per-core performance over simply having more cores, unless you are running multiple server instances.
Ample RAM: Ensure your server has sufficient RAM. Barotrauma can be memory-intensive, especially with larger submarines, more players, and numerous mods. Monitor RAM usage; if it consistently approaches 80-90% utilization, consider upgrading. Swapping to disk (using virtual memory) is a significant performance killer.
Fast Storage (SSD/NVMe): Always use Solid-State Drives (SSDs), preferably NVMe, for the operating system and Barotrauma server files. This drastically reduces load times for the game, saves, and mod assets, contributing to overall server responsiveness.
High-Bandwidth, Low-Latency Network: A stable, high-speed internet connection with low latency is paramount. For hosting services, choose a data center geographically close to your primary player base to minimize ping. Ensure your server's network interface card (NIC) is capable of handling the expected traffic.
Dedicated Resources: If using a VPS, ensure your provider guarantees dedicated CPU cores and RAM. Shared CPU models, while cheaper, can lead to inconsistent performance due to resource contention with other users.
2. Operating System & Server Software Configuration:
Choose a Lean OS: Linux distributions (e.g., Ubuntu Server, Debian) are generally preferred over Windows Server for game servers due to their lower resource overhead and greater efficiency. If using Windows, disable unnecessary services and graphical interfaces.
Keep OS and Drivers Updated: Regularly update your operating system and network drivers. These updates often include performance enhancements and bug fixes.
Firewall Configuration: Configure your firewall precisely to allow only necessary traffic. Overly broad rules or excessive firewall logging can introduce minor overhead.
Server Process Priority: On some operating systems, you can set the Barotrauma server process to a higher priority to ensure it receives preferential CPU time. Use with caution, as this can impact other processes on the server.
Disable Unnecessary Logging: While logs are crucial for troubleshooting, excessive logging can consume disk I/O and CPU cycles. Adjust logging levels in serversettings.xml if performance is critical and you're not actively debugging.
3. In-Game & Server Settings Optimization:
Max Players: Carefully consider your MaxPlayers setting. More players mean more physics calculations, network traffic, and AI processing. Start with a lower number and gradually increase it while monitoring performance.
Game Mode Choice: Campaign mode, with its persistent world and complex save states, can be more resource-intensive than simpler mission-based game modes.
Mod Management:
Curate Mods: Be selective with mods. Each mod adds overhead. Prioritize well-optimized, essential mods.
Test Mods: Thoroughly test new mods on a separate instance or during off-peak hours to identify performance impacts before deploying to your main server.
Remove Unused Mods: Regularly clean out any mods that are no longer in use.
Physics Settings (Advanced): Barotrauma's physics engine is a major performance factor. While direct server-side physics settings are not typically exposed in serversettings.xml for users, understanding its impact is key. High object counts, complex submarine designs, and numerous active creatures all contribute to physics load.
Garbage Collection (Lua/Scripting): If using mods that introduce custom scripting (e.g., Lua), inefficient scripts can cause performance spikes. Well-written scripts manage memory and resources effectively.
Regular Restarts: Schedule regular server restarts (e.g., daily or every 24-48 hours). This can help clear memory leaks, refresh game state, and ensure a clean slate, preventing gradual performance degradation over long uptime periods.
Save File Management: Large or corrupted save files can impact loading times and potentially server stability. Ensure regular backups and consider starting new campaigns periodically if old saves become excessively large.
Technical Q&A
This section addresses common technical questions that arise during the setup, configuration, and maintenance of a Barotrauma dedicated server. The answers draw upon established principles of networking, server administration, and game engine mechanics.
Q1: What is the difference between a dedicated server and hosting a game from the client? A1: When you host a game from the Barotrauma client, your game instance acts as both the client (your player) and the server. This means your computer's resources (CPU, RAM, network bandwidth) are split between running the game for yourself and managing the game state for other players. This often leads to higher latency for other players, potential performance drops for the host, and the server only runs as long as the host's game is active. A dedicated server, conversely, runs as a separate, headless application without a graphical interface. Its sole purpose is to manage the game world, player connections, and game logic. This dedicates all its resources to server operations, resulting in better performance, lower latency for all players (including the host if they join), and the ability to run 24/7 independently of any player's client.
Q2: How do I update my Barotrauma dedicated server? A2: The update process depends on how you installed the server.
SteamCMD (Linux/Windows): If you used SteamCMD, navigate to your SteamCMD directory and run steamcmd +login anonymous +force_install_dir /path/to/your/server +app_update 1026340 validate +quit. Replace /path/to/your/server with your actual server directory. This command will download and apply the latest updates.
Steam Client (Windows): If you installed the "Barotrauma Dedicated Server" tool via the Steam client, Steam will typically update it automatically. You can manually force an update by right-clicking the tool in your Steam library, going to "Properties," then "Local Files," and clicking "Verify integrity of tool files."
Hosting Providers: If you're using a Game Server Provider (GSP), they usually have a one-click update button in their control panel. Consult your provider's documentation. It is crucial to stop your server before initiating an update and restart it afterward.
Q3: Can I run multiple Barotrauma servers on a single machine/VPS? A3: Yes, it is technically possible to run multiple Barotrauma server instances on a single machine or VPS, provided the hardware has sufficient resources (CPU, RAM, network bandwidth) to handle the combined load. Each server instance will require its own dedicated set of files (a separate installation directory) and must be configured to use a unique network port (e.g., 27015, 27016, 27017) to avoid conflicts. You would launch each server executable independently. However, this approach can be complex to manage and monitor, and a single resource-intensive server could impact the performance of others. It's generally recommended to run separate VPS instances for distinct, high-traffic servers.
Q4: How do I add mods to my Barotrauma dedicated server? A4: Adding mods typically involves two main steps:
Server-Side Installation: Download the mod files (usually from the Steam Workshop or a modding site). For Steam Workshop mods, you'll often need to subscribe to them in the Steam client, then locate the downloaded files in your Steam Workshop directory (e.g., Steam\steamapps\workshop\content\602960\MOD_ID). Copy these mod folders into the Mods directory within your Barotrauma dedicated server installation.
Configuration: Edit your serversettings.xml file. Within the
Q5: My server is crashing frequently. How can I diagnose the cause? A5: Frequent crashes are often indicative of underlying issues.
Check Server Logs: The most important step is to examine the server's log files (usually in a Logs subdirectory within your server installation). Look for "Error," "Exception," or "Crash" messages. These often pinpoint the exact line of code or resource that caused the failure.
Resource Monitoring: Monitor your server's CPU, RAM, and disk usage. Spikes in resource consumption just before a crash can indicate a bottleneck or memory leak.
Mod Isolation: If crashes started after adding mods, disable them one by one to identify the problematic mod.
Verify Game Files: Corrupted server files can cause instability. Use SteamCMD's validate command or Steam client's "Verify integrity of tool files" option.
Out-of-Date Software: Ensure your Barotrauma server, OS, and drivers are all up to date.
Hardware Issues: (For self-hosted/dedicated) Check hardware temperatures and run diagnostic tools for RAM and storage.
Q6: How do I set up administrative commands and roles on my server? A6: Barotrauma servers allow for administrative roles to manage players and server settings.
serversettings.xml: You can define administrators in your serversettings.xml file. Look for sections like
In-Game Commands: Once an admin is defined, they can use in-game console commands (accessed by pressing F3 by default) to kick, ban, or manage other players. Common commands include kick [playername], ban [playername] [duration] [reason], setgamemode [gamemode], etc. A full list of commands is usually available on the Barotrauma wiki ( Steamworks Documentation ).
Permissions: Some server management tools or mods might offer more granular permission systems, allowing you to define different levels of administrative access.