Server Setup Guide for [Divinity: Original Sin 2 (multiplayer)] Gamers

Embarking on the grand adventure of Divinity: Original Sin 2 with friends is an unparalleled experience, a tapestry woven with strategic combat, intricate narratives, and shared laughter. To truly savor this cooperative masterpiece, a robust and reliable server setup is paramount. This guide delves into the intricacies of hosting your own Divinity: Original Sin 2 server, offering a detailed roadmap from initial requirements to advanced optimization, ensuring your journey through Rivellon is as smooth as it is memorable.

Game Server Requirements

Understanding the fundamental hardware and software prerequisites for a Divinity: Original Sin 2 server is the cornerstone of a successful multiplayer experience. The demands placed upon a server are distinct from those of a client machine, focusing on consistent uptime, network bandwidth, and efficient processing of game logic for multiple connected players.

At its core, a Divinity: Original Sin 2 server requires a stable operating system. While Windows Server editions are often favored in professional hosting environments due to their robust management features and widespread compatibility ( Microsoft Windows Server Operating System ), a standard Windows 10 or 11 installation can suffice for smaller, private servers. Linux distributions, particularly those with strong community support and lightweight footprints like Ubuntu Server, also present a viable, often more resource-efficient, alternative for experienced users ( Linux Server Hacks ). The choice of operating system will influence the ease of setup and the availability of specific tools.

Processor power is a critical consideration. The game engine, while optimized, still benefits from a CPU with a high clock speed and a reasonable number of cores. For a small group of 2-4 players, a modern quad-core processor (e.g., Intel Core i5 or AMD Ryzen 5 equivalent) is generally sufficient. As the player count increases, or if numerous mods are introduced, a six-core or even eight-core processor becomes increasingly beneficial to handle the concurrent calculations and AI routines. The server's CPU is responsible for processing game state, player actions, and environmental interactions, making its performance directly impact latency and responsiveness.

Memory, or RAM, is another vital component. Divinity: Original Sin 2 can be memory-intensive, especially with larger parties and complex game states. A minimum of 8 GB of RAM is recommended for a basic server hosting 2-4 players. However, to ensure smooth operation and accommodate potential spikes in memory usage, particularly when loading new areas or during intense combat sequences, 16 GB of RAM is a more prudent choice ( Memory Systems: Cache, DRAM, Disk ). For servers intended to host more players or run extensive mod collections, 32 GB or more would provide a significant buffer against performance bottlenecks. Insufficient RAM can lead to frequent disk swapping, which severely degrades server performance and introduces noticeable lag.

Storage speed and capacity are also important. While the game itself doesn't occupy an exorbitant amount of space, the speed at which game assets can be accessed directly impacts loading times for all connected players. A Solid State Drive (SSD) is highly recommended for the operating system and the game installation. The rapid read/write speeds of an SSD significantly reduce the time it takes to load maps, character data, and other game resources, contributing to a smoother experience. A minimum of 100 GB of free space on an SSD is a reasonable starting point, allowing for the game, operating system, and potential future updates or mod installations. Traditional Hard Disk Drives (HDDs) can be used for less critical data, but their slower access times will invariably introduce delays.

Network bandwidth is perhaps the most overlooked yet crucial requirement for a multiplayer game server. Divinity: Original Sin 2 relies on a consistent and low-latency connection to synchronize game states among players. A minimum upload speed of 5-10 Mbps is generally advised for a small group of players, with higher speeds (20+ Mbps) being preferable for larger groups or to mitigate potential network congestion. It is important to distinguish between download and upload speeds; server performance is primarily limited by the upload capacity of the internet connection. A stable, wired Ethernet connection is always superior to Wi-Fi for server hosting, as it offers lower latency and greater reliability, minimizing packet loss and jitter. Furthermore, proper port forwarding on the router is essential to allow incoming connections to the server. The default port for Divinity: Original Sin 2 is typically 27015, though this can be configured.

Finally, a stable power supply and adequate cooling are often overlooked but critical for server longevity and reliability. Uninterrupted power supply (UPS) units can protect against power fluctuations and brief outages, preventing data corruption and server downtime. Proper ventilation and cooling systems are necessary to prevent hardware overheating, which can lead to performance throttling or even component failure.

Beginner's Guide

Setting up a Divinity: Original Sin 2 server for the first time can seem daunting, but by following a structured approach, even novices can establish a functional and enjoyable multiplayer environment. This guide breaks down the process into manageable steps, focusing on clarity and ease of execution.

The journey begins with acquiring the necessary game files. Divinity: Original Sin 2 does not offer a standalone dedicated server application in the traditional sense. Instead, the game client itself contains the server functionality. Therefore, the first step is to install the full game on the machine designated to be the server ( Divinity: Original Sin 2 Official Game Manual ). Ensure the game is fully updated to the latest version, as version mismatches between the server and client can prevent connections.

Once the game is installed, launching the server involves a specific sequence. Navigate to the game's installation directory. Within this directory, locate the bin folder. Inside bin, you will find EoCApp.exe. This executable is the primary game application. To launch it in server mode, you need to use command-line arguments. Open a command prompt (or PowerShell) and navigate to the bin directory. The command to launch the server is typically:

EoCApp.exe -server

This command instructs the game to start in server-only mode, without rendering the graphical user interface, thus conserving system resources. For more advanced configurations, additional arguments can be appended. For instance, to specify a particular save game to load, you might use:

EoCApp.exe -server -save "MyCampaignSave"

It is crucial to ensure that the save game file is present in the correct location within the server's game directory. The default save game location is usually within Documents\Larian Studios\Divinity Original Sin 2 Definitive Edition\PlayerProfiles\[YourProfileName]\Savegames\Story.

Network configuration is the next critical hurdle. For players outside your local network to connect, you must configure port forwarding on your router. This process involves instructing your router to direct incoming traffic on a specific port to the internal IP address of your server machine ( Networking for Dummies ). The default port for Divinity: Original Sin 2 is 27015 (TCP and UDP). The exact steps for port forwarding vary significantly between router manufacturers and models, so consulting your router's manual or the manufacturer's support website is highly recommended. Generally, you will log into your router's administration interface (often via a web browser at an address like 192.168.1.1 or 192.168.0.1), find a section labeled "Port Forwarding," "NAT," or "Virtual Servers," and create a new rule. This rule will specify the external port (27015), the internal port (27015), the protocol (TCP/UDP or Both), and the internal IP address of your server. It is also advisable to assign a static IP address to your server machine within your local network to prevent its IP from changing, which would break the port forwarding rule.

After configuring port forwarding, it's essential to verify that your server is accessible. Websites like "canyouseeme.org" can be used to check if a specific port on your public IP address is open. Enter your public IP address and the port number (27015), and the tool will attempt to connect. A successful connection indicates that port forwarding is correctly configured.

Finally, inviting players to your server. Once the server is running and accessible, players can connect by launching their Divinity: Original Sin 2 client, navigating to the "Multiplayer" section, and selecting "Direct Connect." They will then need to enter your public IP address and the server port (e.g., your.public.ip.address:27015). Alternatively, if you are using a hosting service, they will provide you with a hostname or IP address to share with your players. For players within the same local network, they can often connect directly via the server's local IP address or through the in-game LAN browser.

Remember to regularly back up your server's save game files. Game progress is precious, and unforeseen issues can arise. Copying the save game folder to an external drive or cloud storage periodically is a simple yet effective safeguard against data loss.

Hosting Service Comparison and Recommendations

Choosing the right hosting service for your Divinity: Original Sin 2 server is a pivotal decision that can significantly impact your multiplayer experience. The landscape of game server hosting is diverse, offering a spectrum of options from budget-friendly shared hosting to high-performance dedicated servers. This section will compare various hosting models and recommend suitable providers, keeping the unique demands of Divinity: Original Sin 2 and the gamer audience in mind.

The primary distinction in hosting services lies between shared hosting, Virtual Private Servers (VPS), and dedicated servers.

Shared hosting environments, while often the most economical, are generally not recommended for Divinity: Original Sin 2. In shared hosting, multiple users' applications and servers run on the same physical hardware, sharing CPU, RAM, and network resources. This resource contention can lead to inconsistent performance, "noisy neighbor" issues where another user's activity impacts your server, and limited control over the server environment. For a game like Divinity: Original Sin 2 that benefits from stable performance, shared hosting introduces too many variables.

Virtual Private Servers (VPS) offer a significant step up. A VPS provides a virtualized environment that mimics a dedicated server, giving you root access and dedicated allocations of CPU, RAM, and storage, all running on a shared physical machine. This isolation ensures more consistent performance than shared hosting. VPS solutions are highly scalable, allowing you to upgrade resources as your needs grow. They offer a balance between cost and performance, making them a popular choice for Divinity: Original Sin 2 servers, especially for groups of 4-8 players. When selecting a VPS, prioritize providers that offer high-frequency CPUs, ample RAM (16GB+ recommended), and SSD storage. Look for data centers geographically close to the majority of your players to minimize latency.

Dedicated servers represent the pinnacle of hosting performance and control. With a dedicated server, you lease an entire physical machine, granting you exclusive access to all its resources ( Data Center Handbook ). This eliminates any "noisy neighbor" issues and provides maximum performance, stability, and customization options. Dedicated servers are ideal for larger Divinity: Original Sin 2 communities, servers running extensive mod packs, or those who demand the absolute best performance without compromise. The trade-off is a higher cost and the requirement for more technical expertise to manage the server operating system and software.

When evaluating specific hosting providers, several key factors should guide your decision:

Performance Specifications: As detailed in the "Game Server Requirements" section, prioritize providers offering modern CPUs (high clock speed), sufficient RAM (16GB+), and SSD storage.

Network Latency and Bandwidth: Choose a provider with data centers strategically located to minimize ping times for your player base. Inquire about their network infrastructure and guaranteed bandwidth. Low latency is paramount for a responsive gaming experience.

Uptime Guarantees: Reputable hosts offer Service Level Agreements (SLAs) guaranteeing a certain percentage of uptime (e.g., 99.9%). Consistent availability is crucial for a persistent game world.

Customer Support: Even experienced users encounter issues. Responsive and knowledgeable 24/7 customer support can be invaluable, especially for troubleshooting complex server problems.

Ease of Use/Management Panel: Some providers offer custom control panels (e.g., Pterodactyl, TCAdmin) that simplify server management, making it easier to install games, manage files, and configure settings. For Divinity: Original Sin 2, which doesn't have a dedicated server application in the traditional sense, a robust file manager and console access are particularly useful.

Cost: While not the sole determinant, cost is a practical consideration. Compare pricing models (monthly, quarterly, annual) and ensure there are no hidden fees.

Recommended Hosting Providers (General Categories):

For VPS Hosting (Excellent balance for most Divinity: Original Sin 2 groups):

DigitalOcean: Known for its developer-friendly interface, robust SSD-backed droplets, and excellent network performance. Offers various data center locations. Requires some command-line familiarity.

Linode: Similar to DigitalOcean, Linode provides high-performance VPS instances with competitive pricing and a strong focus on developer tools.

Vultr: Offers a wide range of server locations and competitive pricing, often with high-frequency CPU options that benefit game servers.

For Dedicated Server Hosting (For large communities or maximum performance):

OVHcloud: A global leader in dedicated servers, offering a vast array of configurations at competitive prices. Requires significant technical expertise.

Hetzner Online: Renowned for its powerful dedicated servers and excellent price-to-performance ratio, particularly in Europe.

ServerMania: Offers a range of dedicated server options with good network connectivity and customer support.

When making your final decision, consider starting with a monthly plan to test the service's performance with your specific Divinity: Original Sin 2 setup before committing to a longer contract. Always read reviews and community feedback, but remember that individual experiences can vary.

Troubleshooting

Even the most meticulously planned server setup can encounter unforeseen issues. Effective troubleshooting is a critical skill for any server administrator, ensuring minimal downtime and a smooth gaming experience for all players. This section outlines common problems encountered with Divinity: Original Sin 2 servers and provides systematic approaches to diagnose and resolve them.

One of the most frequent issues is players being unable to connect to the server. This often manifests as "Connection Failed" or "Server Not Responding" messages. The first step in diagnosing this is to verify the server's operational status. Check the server console (if running headless) or the game window (if running with a GUI) for any error messages or indications that the server has crashed or stopped. If the server appears to be running, the problem likely lies in network accessibility.

Port Forwarding: Re-verify that port 27015 (or your chosen port) is correctly forwarded on your router to the server's internal IP address. Use an external port checker tool (e.g., canyouseeme.org) to confirm the port is open to the internet. Ensure the server's internal IP address is static to prevent it from changing and invalidating the port forwarding rule ( TCP/IP Illustrated, Volume 1: The Protocols ).

Firewall: Both the server's operating system firewall (e.g., Windows Defender Firewall, ufw on Linux) and any hardware firewalls (often integrated into routers) can block incoming connections. Create an inbound rule to allow traffic on port 27015 for both TCP and UDP protocols ( Network Security Essentials: Applications and Standards ). Temporarily disabling the firewall (with caution) can help isolate if it's the culprit, but always re-enable it with the correct rules for security.

Public IP Address: Ensure players are using the correct public IP address of your server. If your ISP assigns a dynamic public IP, it might change periodically. Consider using a Dynamic DNS (DDNS) service to map a static hostname to your dynamic IP, making it easier for players to connect without needing to constantly update the IP address ( DNS and BIND ).

ISP Restrictions: Some Internet Service Providers (ISPs) block certain ports or restrict incoming connections, particularly on residential internet plans. If all other troubleshooting steps fail, contact your ISP to inquire about any such restrictions.

Server performance issues, such as lag, stuttering, or slow loading times, are another common complaint. These can stem from various sources:

Resource Bottlenecks: Monitor the server's CPU, RAM, and disk I/O usage. Task Manager on Windows or tools like htop and iostat on Linux can provide real-time insights ( Linux System Programming ). If any resource is consistently at 90-100% utilization, it indicates a bottleneck.

CPU: High CPU usage might necessitate upgrading to a faster processor or one with more cores, especially if many players or complex mods are active.

RAM: If RAM usage is consistently high, leading to disk swapping, increasing the server's RAM is essential.

Disk I/O: Slow disk I/O, often indicated by high disk queue lengths, points to a need for faster storage, ideally an SSD.

Network Congestion: High ping times or packet loss can indicate network issues. Check the server's internet connection speed, particularly upload bandwidth. If other devices on the network are consuming significant bandwidth, this can impact server performance. Prioritize server traffic if your router supports Quality of Service (QoS).

Game-Specific Issues: Certain areas in Divinity: Original Sin 2 or specific spell effects can be more resource-intensive. If lag is localized to particular game events, it might be a game engine limitation rather than a server hardware issue.

Mods: Heavily modded servers can introduce performance overhead. Test the server with a vanilla installation to rule out mod conflicts or poorly optimized mods as the cause. Gradually reintroduce mods to identify problematic ones.

Server crashes or instability can be particularly frustrating.

Error Logs: The first place to look is the server's log files. Divinity: Original Sin 2 typically generates logs in the Documents\Larian Studios\Divinity Original Sin 2 Definitive Edition\PlayerProfiles\[YourProfileName]\Log directory. These logs often contain valuable information about the cause of a crash, such as memory access violations or script errors ( Software Engineering: A Practitioner's Approach ).

Corrupted Save Games: A corrupted save file can lead to crashes upon loading. Attempt to load an older, known-good save game to determine if the issue is save-game specific. Regularly backing up save games is crucial.

Mod Conflicts: As with performance, mods can introduce instability. Disable all mods and test the server. If stable, re-enable mods one by one to identify the conflicting or buggy mod.

Hardware Failure: While less common, faulty RAM, an unstable power supply, or an overheating CPU can cause intermittent crashes. Run hardware diagnostics if software troubleshooting yields no results.

Save game issues, such as inability to save or corrupted saves, require careful attention.

Disk Space: Ensure the server has sufficient free disk space for save games.

Permissions: Verify that the user account running the server has appropriate write permissions to the save game directory.

Cloud Sync Conflicts: If cloud save synchronization (e.g., Steam Cloud) is enabled on the server, it can sometimes conflict with local server saves. Consider disabling cloud sync for the server instance.

When troubleshooting, adopt a systematic approach: change one variable at a time, test the change, and document your steps. This methodical process helps isolate the root cause of the problem efficiently. Consulting online forums, the official Larian Studios forums, and community wikis can also provide solutions to known issues.

Performance Optimization Tips

Optimizing your Divinity: Original Sin 2 server goes beyond merely meeting the minimum requirements; it's about fine-tuning the environment to deliver the smoothest, most responsive multiplayer experience possible. This section provides actionable strategies to enhance server performance, focusing on both hardware and software configurations.

Hardware-Level Optimizations:

Prioritize SSDs: As previously mentioned, an SSD for the operating system and game installation is non-negotiable for optimal performance. The rapid read/write speeds significantly reduce loading times and improve overall responsiveness, especially during intense game moments or when many players are interacting with the game world ( Storage Systems: Organization, Performance, and Dependability ).

Ample RAM: Ensure your server has more RAM than the bare minimum. While 8GB might run the server, 16GB or 32GB provides a substantial buffer, preventing the system from resorting to slower disk-based virtual memory (swapping). This is particularly important for Divinity: Original Sin 2 due to its detailed world and complex game state.

High Clock Speed CPU: Divinity: Original Sin 2, like many game engines, benefits significantly from high single-core CPU clock speeds. While multiple cores are useful for handling concurrent tasks, the core game logic often relies on a single thread. Prioritize CPUs with strong single-threaded performance ( Computer Organization and Design RISC-V Edition ).

Stable Network Connection: A wired Ethernet connection is always superior to Wi-Fi for server hosting. Ensure the network cable is of good quality and the network interface card (NIC) is functioning optimally. Minimize other network traffic on the server machine.

Operating System and Software Optimizations:

Dedicated Server Machine: Ideally, the Divinity: Original Sin 2 server should run on a machine dedicated solely to this task. Running other demanding applications (web browsers with many tabs, video streaming, other games) on the same machine will inevitably compete for resources and degrade server performance.

Minimal OS Installation: For dedicated servers, consider a minimal installation of your chosen operating system. This reduces background processes, frees up RAM, and minimizes potential conflicts. For Windows, disable unnecessary services and visual effects. For Linux, a server-focused distribution with a minimal desktop environment or no GUI is ideal ( Linux Administration Handbook ).

Update Drivers and OS: Keep your operating system, network drivers, and any relevant hardware drivers up to date. Manufacturers often release updates that improve performance, stability, and security.

Firewall Configuration: While necessary for security, an overly aggressive or misconfigured firewall can introduce latency. Ensure your firewall rules are precise, allowing only the necessary ports (27015 TCP/UDP) for Divinity: Original Sin 2 and blocking everything else. Avoid running multiple firewall solutions simultaneously.

Antivirus Exclusions: Antivirus software, while crucial for security, can sometimes interfere with game server performance by scanning game files during access. Configure your antivirus to exclude the Divinity: Original Sin 2 server directory from real-time scanning. Exercise caution and ensure your system remains otherwise protected.

Power Management Settings: On Windows, ensure the server's power plan is set to "High Performance." This prevents the CPU from throttling its clock speed to save power, ensuring it always operates at its maximum potential ( Windows 10: The Missing Manual ). On Linux, ensure CPU frequency scaling governors are set to "performance."

Disable Unnecessary Services: Review the list of running services on your server's operating system and disable any that are not essential for the server's operation. This frees up RAM and CPU cycles.

Regular Maintenance: Periodically restart the server machine and the Divinity: Original Sin 2 server application. This can clear out memory leaks, refresh network connections, and resolve minor software glitches. Keep the game itself updated to the latest version, as Larian Studios often releases performance patches.

Game-Specific Optimizations:

Mod Management: While mods enhance the Divinity: Original Sin 2 experience, they can also be a significant source of performance issues.

Curate Mods Carefully: Only install mods from reputable sources and those known to be stable and well-optimized.

Test Mods Incrementally: Add mods one by one and test server stability and performance after each addition.

Avoid Over-Modding: A server with hundreds of complex mods will almost certainly struggle. Prioritize quality over quantity.

Check for Conflicts: Use mod managers or community tools to identify and resolve potential mod conflicts.

Save Game Management: Large and numerous save game files can sometimes impact loading times. While not a direct performance bottleneck during gameplay, keeping your save game directory tidy and periodically archiving older, unused saves can contribute to overall system health.

Server Launch Parameters: Experiment with additional command-line arguments when launching the server. While -server is essential, other undocumented or community-discovered parameters might exist that can fine-tune performance. Always research and test these thoroughly.

By implementing these optimization tips, you can significantly enhance the stability, responsiveness, and overall performance of your Divinity: Original Sin 2 server, providing an exceptional multiplayer experience for you and your fellow adventurers.

Technical Q&A

This section addresses common technical questions that arise during the setup, maintenance, and optimization of a Divinity: Original Sin 2 multiplayer server. The answers draw upon established networking principles, operating system functionalities, and game-specific knowledge.

Q1: What is the difference between hosting a server directly from my game client and using a dedicated server machine?

A1: When you host directly from your game client, your gaming machine simultaneously runs both the game client (rendering graphics, processing input) and the server logic. This places a significant burden on your system's resources (CPU, RAM, GPU, network bandwidth), potentially leading to reduced frame rates, increased latency, and overall instability for both you and your connected players ( Game Engine Architecture ). A dedicated server machine, conversely, runs only the server application, often in a headless (no graphical interface) mode. This allows all its resources to be solely focused on processing game logic, synchronizing player actions, and managing the game world. The result is a more stable, performant, and reliable experience for all players, as the server's performance is not impacted by the host's client-side activities.

Q2: How do I ensure my server's IP address doesn't change, which would break port forwarding?

A2: There are two primary methods to address a dynamic IP address. First, within your local network, you should assign a static internal IP address to your server machine. This is typically done through your router's DHCP reservation settings, where you bind a specific IP address to your server's MAC address ( Networking All-in-One For Dummies ). This ensures the server's internal IP never changes, maintaining the integrity of your port forwarding rules. Second, for your public IP address, which is assigned by your Internet Service Provider (ISP) and can change, you can use a Dynamic DNS (DDNS) service. DDNS services (e.g., No-IP, DynDNS) allow you to associate a static hostname (e.g., mydivinityserver.ddns.net) with your dynamic public IP. A small client application on your server or a feature in your router periodically updates the DDNS service with your current public IP, ensuring the hostname always points to your server. Players can then connect using this static hostname instead of a potentially changing IP address.

Q3: Can I run multiple Divinity: Original Sin 2 servers on a single machine?

A3: Technically, yes, it is possible to run multiple instances of the Divinity: Original Sin 2 server application on a single machine. However, this is generally not recommended unless the machine has exceptionally robust hardware (high core count CPU, abundant RAM, fast SSDs) and you are an experienced server administrator. Each server instance will consume its own set of resources (CPU cycles, RAM, network bandwidth). You would also need to configure unique port forwarding rules for each instance (e.g., 27015, 27016, 27017) and ensure each instance loads a different save game or profile to avoid conflicts. Resource contention between multiple server instances on the same machine can lead to degraded performance for all hosted games ( Operating System Concepts ). It is usually more efficient and stable to host one dedicated server per physical or virtual machine.

Q4: What are the security implications of running a game server, and how can I mitigate risks?

A4: Running any server connected to the internet introduces security risks. The primary concerns include unauthorized access, denial-of-service (DoS) attacks, and potential exploitation of software vulnerabilities. To mitigate these risks:

Strong Passwords: Use complex, unique passwords for your server's operating system and any administrative accounts.

Firewall: Maintain a properly configured firewall that only allows necessary incoming connections (port 27015 for Divinity: Original Sin 2) and blocks all others.

Software Updates: Keep your operating system, game server application, and all other software on the server updated with the latest security patches.

Antivirus/Anti-Malware: Install and regularly update reputable antivirus/anti-malware software on your server. Configure it to exclude game directories from real-time scanning to avoid performance impact, but ensure regular full scans.

Principle of Least Privilege: Run the game server application with the minimum necessary user privileges. Avoid running it as an administrator or root user unless absolutely required.

Backups: Regularly back up your server's save games and critical configuration files to an off-site location. This protects against data loss due to hardware failure, corruption, or malicious activity.

Monitoring: Implement basic monitoring to detect unusual activity or resource spikes that might indicate a security incident.

Q5: My server is experiencing high ping for players, but my internet speed test shows good results. What could be the cause?

A5: High ping, even with good internet speed test results, often points to issues beyond raw bandwidth.

Upload vs. Download: Speed tests typically emphasize download speeds. Game servers are heavily reliant on upload speed to send game state updates to players. Ensure your upload bandwidth is sufficient and stable.

Network Congestion (Local): Other devices on your local network (streaming video, large downloads, other online games) can consume significant bandwidth, especially upload, leading to congestion for your server. Implement Quality of Service (QoS) on your router if available to prioritize server traffic.

Network Congestion (ISP/Internet Backbone): Even if your local connection is fine, congestion can occur at your ISP's network or further along the internet backbone between your server and players. This is harder to diagnose and resolve, but using a hosting provider with robust network infrastructure and strategically located data centers can mitigate this.

Geographic Distance: The physical distance between your server and players directly impacts latency. Data takes time to travel. If players are geographically dispersed, some will naturally experience higher ping.

Server Hardware Bottlenecks: While less direct, if your server's CPU or RAM is overloaded, it can struggle to process game logic and send updates efficiently, leading to perceived lag and higher ping.

Firewall/Router Overhead: Some older or less powerful routers/firewalls can introduce latency due to their processing overhead, especially when handling many concurrent connections or complex rules.

Q6: How do I manage mods on my Divinity: Original Sin 2 server?

A6: Managing mods on a Divinity: Original Sin 2 server requires a bit of manual effort, as there isn't a built-in server-side mod manager.

Client-Side Installation: First, ensure all desired mods are installed and working correctly on your client machine (the one you use to play the game). This typically involves subscribing to them on the Steam Workshop or placing them in the game's Mods folder.

Copy Mod Files: Locate the .pak files for the mods. For Steam Workshop mods, these are usually found in Steam\steamapps\workshop\content\435150. Copy the .pak files of the mods you want to use to the server's game installation directory, specifically into the Data\Mods folder (e.g., C:\Program Files (x86)\Steam\steamapps\common\Divinity Original Sin 2\Data\Mods).

Mod Order: The order in which mods are loaded can be crucial to prevent conflicts. On your client machine, launch the game, go to the "Mods" section, and arrange the mods in the desired load order. This order is saved in a file called modsettings.lsx (or similar) within your player profile (Documents\Larian Studios\Divinity Original Sin 2 Definitive Edition\PlayerProfiles\[YourProfileName]\modsettings.lsx).

Transfer Mod Order: Copy this modsettings.lsx file from your client's player profile to the server's player profile directory. Ensure the server is using the same player profile name.

Verify: Launch the server. When players connect, their clients will automatically attempt to download and enable the mods specified by the server's modsettings.lsx file. If a player is missing a mod or has a different version, they will typically be prompted to download it or will be unable to connect.