Server Setup Guide for [World of Warcraft (private servers - older expansions)] Gamers

Game Server Requirements

Establishing a private World of Warcraft server for older expansions, such as Vanilla, The Burning Crusade, or Wrath of the Lich King, necessitates a careful consideration of hardware and software specifications. The demands placed upon a server are directly proportional to the number of concurrent players, the complexity of the game world, and the specific expansion being emulated. While the core game client for these older versions is relatively lightweight compared to modern titles, the server-side emulation requires substantial resources to maintain a stable and responsive environment.

At the foundational level, the Central Processing Unit (CPU) is paramount. A multi-core processor with high clock speeds is highly recommended. For a small server catering to a few dozen players, a modern quad-core CPU with a base clock of 3.0 GHz or higher might suffice. However, as player counts escalate into the hundreds or thousands, an octa-core or even a 12-core CPU, ideally with excellent single-thread performance, becomes essential. The game server software, particularly the world server component, often relies heavily on single-threaded operations, making clock speed a critical factor. Intel's Xeon series or AMD's EPYC processors are frequently chosen for their robust multi-core performance and reliability in server environments.

Memory, or Random Access Memory (RAM), is another critical component. The server software, operating system, and database all consume RAM. For a modest server, 8 GB of DDR4 RAM might be a starting point. However, to accommodate a growing player base and prevent performance bottlenecks, 16 GB, 32 GB, or even 64 GB of RAM is often necessary. The database, which stores character data, item information, and world state, can be particularly memory-intensive, especially with a large number of entries and frequent queries ( Database System Concepts ). Error-Correcting Code (ECC) RAM is highly recommended for server environments, as it can detect and correct memory errors, enhancing stability and preventing data corruption.

Storage solutions directly impact loading times and overall responsiveness. Solid State Drives (SSDs) are unequivocally superior to traditional Hard Disk Drives (HDDs) for game server applications. The high Input/Output Operations Per Second (IOPS) of SSDs significantly reduce latency when the server accesses game data, character profiles, or database entries. A Non-Volatile Memory Express (NVMe) SSD offers even greater performance, leveraging the PCIe interface for faster data transfer rates. A minimum of 250 GB for the operating system and server files is a reasonable starting point, but 500 GB or 1 TB is preferable to accommodate future expansion, logs, and backups ( Storage Systems: Organization, Performance, Data Integrity, and Power ). Redundant Array of Independent Disks (RAID) configurations, such as RAID 1 for mirroring or RAID 10 for performance and redundancy, are often employed to protect against data loss and improve read/write speeds.

Network connectivity is the lifeline of any online game server. A stable and high-bandwidth internet connection is non-negotiable. For a private server, a dedicated gigabit Ethernet port is the minimum expectation. The server's uplink speed is particularly important, as it dictates how quickly data can be sent to connected clients. While download speed is also relevant, the server's primary role is to upload game state information to players. A symmetrical connection, where upload and download speeds are equal, is ideal. Low latency is also crucial for a smooth gaming experience, as high ping can lead to noticeable delays and rubber-banding for players. Distributed Denial of Service (DDoS) protection is also a significant consideration, as private servers can be targets of malicious attacks.

The operating system (OS) choice typically falls between Linux distributions and Windows Server. Linux, particularly distributions like Ubuntu Server or CentOS, is often favored for its stability, security, and lower resource overhead. Many World of Warcraft private server emulators are developed and optimized for Linux environments. Windows Server offers a more familiar graphical user interface for some administrators but generally consumes more resources and may require additional licensing costs. Regardless of the OS, it should be a 64-bit version to fully utilize available RAM.

Finally, the specific World of Warcraft emulator software itself has its own requirements. Emulators like MaNGOS, TrinityCore, or AzerothCore are open-source projects that replicate the server-side logic of the game. These emulators often require specific versions of compilers (e.g., GCC for Linux, Visual Studio for Windows), database systems (MySQL or MariaDB are common), and various libraries. Consulting the documentation for the chosen emulator is paramount to ensure all software dependencies are met.

Beginner's Guide

Embarking on the journey of setting up a World of Warcraft private server for older expansions can seem daunting, but with a structured approach, it's an achievable and rewarding endeavor. This guide will walk you through the fundamental steps, from conceptualization to your first login.

The very first step is to choose your desired World of Warcraft expansion. Do you yearn for the classic days of Vanilla, the Outland adventures of The Burning Crusade, or the frozen wastes of Wrath of the Lich King? This decision is crucial as it dictates which emulator software you will need. Each expansion has dedicated emulator projects that meticulously recreate its specific game mechanics, quests, and content. Research the active development communities for each expansion; popular choices include AzerothCore for Vanilla and TBC, and TrinityCore for WotLK.

Once you've selected your expansion, the next critical decision is your hosting environment. For beginners, two primary paths emerge: self-hosting or utilizing a Virtual Private Server (VPS) or dedicated server from a hosting provider. Self-hosting, while cost-effective, requires a robust home internet connection, a dedicated computer, and a significant understanding of network configuration, including port forwarding and firewall rules. A VPS or dedicated server, on the other hand, offers professional infrastructure, better bandwidth, and often DDoS protection, albeit at a recurring cost. For a smoother initial experience, especially if you anticipate more than a handful of players, a VPS is often the recommended starting point.

With your hosting environment in place, the next phase involves setting up the operating system. As discussed in the "Game Server Requirements" section, Linux distributions like Ubuntu Server are frequently preferred due to their efficiency and compatibility with most emulator projects. If you're using a VPS, the provider will typically offer a choice of pre-installed operating systems. For self-hosting, you'll need to install your chosen OS onto your server machine. Familiarize yourself with basic command-line operations if you opt for a headless Linux server, as this will be your primary interface.

The core of your private server is the emulator software. This is where the magic happens, translating player actions into game world events. Download the source code for your chosen emulator from its official repository (e.g., GitHub). The emulator's documentation will provide detailed instructions on how to compile the source code. This process typically involves installing development tools, libraries, and a C++ compiler. Compilation transforms the human-readable source code into an executable program that your server can run.

Alongside the emulator, you'll need a database system. MySQL or MariaDB are the most common choices. These relational databases store all persistent game data: character information, item properties, quest progress, and more. Install your chosen database server and create a new database specifically for your World of Warcraft server. The emulator project will usually provide SQL scripts to populate this database with the initial game world data, including maps, creatures, and quests.

Configuring the emulator is a crucial step. The emulator typically comes with configuration files (often .conf or .ini files) where you define various server settings. This includes database connection details, server name, maximum player capacity, experience rates, drop rates, and various game mechanics adjustments. Carefully review these files and modify them according to your desired server experience. Incorrect configurations can lead to server instability or unexpected game behavior.

Finally, you'll need the World of Warcraft client files for the specific expansion you're emulating. Players will connect to your server using this client. Ensure that your client version matches the emulator's version. You'll also need to modify the realmlist.wtf file within the client's data folder to point to your server's IP address or domain name. This tells the game client where to find your private server.

Once all components are installed and configured, you can start the emulator. Typically, this involves running specific executable files for the world server and authentication server. Monitor the server console for any errors during startup. If everything is configured correctly, you should see messages indicating that the server is online and ready for connections. From your game client, attempt to log in using an account you've created on your server (often through a web-based account creation panel or a command within the server console). Congratulations, you've brought a piece of Azeroth back to life!

Hosting Service Comparison and Recommendations

Selecting the optimal hosting service for a World of Warcraft private server, particularly for older expansions, is a pivotal decision that directly impacts performance, stability, and the overall player experience. The landscape of hosting providers is vast, offering a spectrum of services from shared hosting to dedicated servers. For the specific demands of a game server, certain types of hosting are far more suitable than others.

Shared hosting, while inexpensive, is generally unsuitable for World of Warcraft private servers. Resources like CPU, RAM, and bandwidth are shared among numerous users, leading to unpredictable performance and frequent bottlenecks. The intensive nature of a game server, with its constant database queries and real-time data synchronization, quickly overwhelms shared environments.

Virtual Private Servers (VPS) represent a significant step up. A VPS provides a virtualized slice of a physical server, offering dedicated resources (CPU cores, RAM, storage) that are not shared with other users. This isolation ensures more consistent performance. VPS solutions are highly scalable, allowing administrators to upgrade resources as their player base grows. They offer root access, granting full control over the operating system and software installations, which is essential for installing and configuring World of Warcraft emulators and databases. When evaluating VPS providers, prioritize those offering high-frequency CPUs, ample RAM, and NVMe SSD storage. Look for providers with data centers geographically close to your target player base to minimize latency. Reputable providers often include DDoS protection as a standard feature, a crucial consideration for game servers.

Dedicated servers offer the pinnacle of performance and control. With a dedicated server, you lease an entire physical machine, meaning all its resources are exclusively yours. This eliminates the "noisy neighbor" problem sometimes encountered even on VPS platforms. Dedicated servers are ideal for large private servers anticipating hundreds or thousands of concurrent players. They provide maximum flexibility for hardware customization, allowing you to choose specific CPU models, RAM configurations, and storage arrays. However, dedicated servers come with a higher price tag and require a greater degree of technical expertise for management. For a World of Warcraft private server, a dedicated server with a powerful multi-core CPU (e.g., Intel Xeon E3/E5 or AMD EPYC), 32 GB or more of ECC RAM, and NVMe SSDs in a RAID configuration would provide an exceptional foundation.

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

Performance Specifications: Scrutinize CPU clock speed and core count, available RAM (and whether it's ECC), and storage type (NVMe SSDs are preferred).

Network Connectivity: Look for providers offering gigabit or 10-gigabit uplinks and low-latency connections. Inquire about their network infrastructure and peering agreements.

DDoS Protection: This is non-negotiable for game servers. Ensure the provider offers robust, always-on DDoS mitigation.

Location of Data Centers: Choose a data center geographically close to the majority of your anticipated players to minimize ping.

Customer Support: Responsive and knowledgeable technical support is invaluable, especially when troubleshooting server issues.

Pricing and Scalability: Compare pricing models (monthly, annual) and assess the ease with which you can upgrade or downgrade resources.

Operating System Options: Ensure the provider supports your preferred OS (e.g., Ubuntu Server, CentOS).

Recommendations for Hosting Providers (General Categories):

For Small to Medium Servers (10-100 players): A high-performance VPS is often the sweet spot. Providers like DigitalOcean, Linode, Vultr, or OVHcloud offer competitive VPS plans with good performance and network infrastructure. They typically provide easy-to-use control panels and a variety of OS templates.

For Medium to Large Servers (100+ players): Consider upgrading to a more powerful VPS or a budget-friendly dedicated server. Providers like Hetzner, OVHcloud, or Kimsufi (a subsidiary of OVHcloud) offer excellent value for dedicated hardware. These often require more hands-on management but deliver superior performance.

For Very Large or Professional-Grade Servers (500+ players): A high-end dedicated server from providers like Leaseweb, ServerMania, or even custom solutions from larger data centers would be appropriate. These offer maximum customization and robust infrastructure but come with a premium price.

Ultimately, the "best" hosting service is subjective and depends on your specific needs, budget, and technical comfort level. Start with a plan that meets your initial requirements and allows for easy scaling as your server grows.

Troubleshooting

Even with meticulous planning and execution, issues are an inevitable part of managing a World of Warcraft private server. Effective troubleshooting requires a systematic approach, keen observation, and an understanding of the various components involved. This section outlines common problems and strategies for resolving them.

1. Server Fails to Start or Crashes Immediately: This is often the first hurdle.

Check Logs: The most crucial step. Emulator software (worldserver, authserver) and database systems (MySQL/MariaDB) generate log files. These logs contain error messages, warnings, and diagnostic information that pinpoint the exact cause of the failure. Look for keywords like "ERROR," "FATAL," or "CRITICAL."

Configuration Errors: Incorrect entries in worldserver.conf or authserver.conf are common culprits. Double-check database connection strings, IP addresses, port numbers, and file paths. Even a single typo can prevent startup.

Missing Dependencies: Ensure all required libraries, compilers, and database client tools are installed and correctly configured for your operating system.

Database Issues: The database might not be running, or the emulator might lack the necessary permissions to connect to it. Verify the database server's status and user credentials. Corrupted database tables can also cause startup failures; check the database logs for integrity issues.

Port Conflicts: Ensure that the ports the emulator attempts to use (e.g., 3724 for authentication, 8085 for world server) are not already in use by another application on your server. Use netstat -tulnp on Linux to check open ports.

2. Players Cannot Connect to the Server: The server appears to be running, but players can't log in.

Firewall: This is a very frequent cause. The server's firewall (e.g., ufw on Linux, Windows Firewall) must have rules allowing inbound connections on the ports used by your authserver and worldserver.

Port Forwarding (Self-Hosting): If you are self-hosting behind a router, you must configure port forwarding to direct incoming traffic on the server's ports to the internal IP address of your server machine.

realmlist.wtf: Players must have their realmlist.wtf file correctly pointing to your server's public IP address or domain name. Verify this with your players.

Network Connectivity: Ensure the server itself has a stable internet connection. Test with ping or traceroute to external websites.

DDoS Protection: If you're using a hosting provider with DDoS protection, sometimes legitimate connections can be inadvertently blocked. Check with your provider.

3. Lag and Performance Issues: The server is running, but players experience delays, disconnects, or slow responses.

Resource Utilization: Monitor CPU, RAM, and disk I/O usage on your server. High CPU usage (consistently above 80-90%) or RAM exhaustion (swapping to disk) are clear indicators of resource bottlenecks. Use tools like htop (Linux) or Task Manager (Windows).

Network Latency: High ping from players to your server indicates network issues. This could be on the player's end, your server's internet connection, or an issue with the hosting provider's network. Use ping and traceroute from various locations.

Database Performance: Slow database queries can significantly impact game performance. Optimize database indexes, ensure sufficient RAM for the database cache, and review slow query logs.

Emulator Configuration: Certain emulator settings, such as high spawn rates, complex AI, or excessive script execution, can strain server resources. Review and adjust these settings.

Software Updates: Ensure your operating system, database, and emulator are running stable, up-to-date versions. Bug fixes often include performance improvements.

4. In-Game Bugs and Glitches: Quests not working, spells not casting correctly, or NPCs behaving erratically.

Emulator Version: Ensure you are using a stable and well-maintained version of the emulator. Development versions might contain new bugs.

Database Content: Many in-game elements are defined in the database. Incorrect or missing entries can cause bugs. Verify the integrity of your database and consider re-importing the core SQL data if necessary.

Custom Scripts: If you've added custom scripts or modifications, these are a common source of bugs. Test them thoroughly and isolate them if problems arise.

Community Resources: The communities around World of Warcraft emulators are vast. Search their forums, bug trackers, and Discord channels for similar issues. Chances are, someone else has encountered and solved the problem.

5. Data Loss or Corruption: Character data disappears, items vanish, or the world state resets.

Backups: Implement a robust backup strategy immediately. Regularly back up your entire database and server configuration files. Store backups off-site.

Hardware Failure: While rare with professional hosting, hardware failures can occur. RAID configurations mitigate disk failures, but backups are the ultimate safeguard.

Database Integrity: Regularly run database integrity checks and repairs.

Graceful Shutdowns: Always shut down your server gracefully using the emulator's commands (e.g., shutdown in the console) rather than abruptly terminating processes. This ensures data is properly saved.

When troubleshooting, always change one variable at a time and test the result. Document your steps and observations. This systematic approach will help you isolate the root cause of issues more efficiently.

Performance Optimization Tips

Achieving a smooth, responsive, and stable World of Warcraft private server experience, especially for older expansions, hinges significantly on effective performance optimization. This involves fine-tuning various components, from the underlying operating system to the emulator's specific configurations. The goal is to maximize resource utilization and minimize latency.

1. Operating System Optimization:

Minimal Installation: Install a minimal version of your chosen Linux distribution (e.g., Ubuntu Server, CentOS Stream) to reduce unnecessary background processes and resource consumption. Avoid installing a graphical user interface (GUI) unless absolutely necessary.

Kernel Tuning: For advanced users, adjusting kernel parameters can yield benefits. For instance, increasing file descriptor limits (fs.file-max) and network buffer sizes (net.core.rmem_max, net.core.wmem_max) can improve network performance.

Disable Unnecessary Services: Stop and disable any services not required for your game server (e.g., print spoolers, desktop environments, unnecessary daemons).

Swap Space: While ample RAM is preferred, ensure you have adequate swap space configured as a fallback, though excessive swapping indicates a RAM bottleneck.

Update Regularly: Keep your OS and all installed packages up to date to benefit from performance improvements and security patches.

2. Database Optimization (MySQL/MariaDB): The database is often the bottleneck in game servers due to frequent read/write operations.

InnoDB Engine: Ensure your tables are using the InnoDB storage engine, which offers better performance, crash recovery, and row-level locking compared to MyISAM.

my.cnf Tuning: The my.cnf (or my.ini for Windows) configuration file is critical.

innodb_buffer_pool_size: Allocate a significant portion of your available RAM (e.g., 50-70%) to this parameter. It caches frequently accessed data and indexes, drastically reducing disk I/O.

query_cache_size: For older MySQL versions, a small query cache can help, but for newer versions (MySQL 5.7+ and MariaDB 10.1+), it's often deprecated or less effective due to concurrency issues.

max_connections: Set this appropriately for your expected player count, but don't make it excessively high.

key_buffer_size: Relevant for MyISAM tables, but less so for InnoDB.

log_slow_queries / slow_query_log: Enable this to identify and optimize inefficient SQL queries.

Indexing: Ensure all frequently queried columns (e.g., guid, name, account) have appropriate indexes. Indexes speed up data retrieval but add overhead to writes.

Table Optimization: Periodically run OPTIMIZE TABLE on your database tables to defragment them and reclaim space, though this is less critical with InnoDB.

SSD/NVMe Storage: As mentioned in requirements, using SSDs or NVMe drives for your database files is paramount for I/O performance.

3. Emulator Configuration and Scripting: The emulator itself offers numerous levers for performance.

worldserver.conf / authserver.conf:

Rate Limiting: Adjust rates for experience, drops, and gold carefully. Very high rates can lead to excessive database writes.

AI Complexity: Reduce the complexity of NPC AI if it's causing CPU spikes, especially in densely populated areas.

Spawn Rates: While tempting to have a lively world, very high spawn rates for creatures and objects can consume significant CPU and memory.

Save Interval: Increase the interval at which character data is saved to the database. While this slightly increases the risk of data loss during a crash, it reduces database write load.

Logging Level: Set logging to a reasonable level (e.g., INFO or WARNING) rather than DEBUG in production, as excessive logging consumes disk I/O and CPU.

Custom Scripts: If you're using custom C++ or Lua scripts, ensure they are optimized for performance. Inefficient loops, excessive database calls, or memory leaks in scripts can severely degrade server performance. Profile your scripts if possible.

Module Management: Only enable modules or features that you actively use. Each enabled module consumes resources.

4. Network Optimization:

High-Quality Hosting: A hosting provider with a robust network infrastructure, low latency, and high bandwidth is fundamental.

DDoS Protection: While primarily for security, effective DDoS mitigation prevents network saturation that would otherwise cripple performance.

Server Location: Place your server in a data center geographically central to your player base to minimize ping.

TCP/IP Tuning: For very high player counts, advanced TCP/IP stack tuning on the OS level can sometimes offer marginal gains, but this is typically handled effectively by modern kernels.

5. Hardware Upgrades: Ultimately, if software optimizations aren't enough, hardware upgrades are necessary.

CPU: Upgrade to a CPU with higher clock speeds and more cores, especially if worldserver is consistently maxing out a single core or overall CPU usage is high.

RAM: Add more RAM, particularly if your database buffer pool is constrained or the OS is heavily swapping.

Storage: Upgrade from SATA SSDs to NVMe SSDs for superior I/O performance.

Regular monitoring of your server's resource usage (CPU, RAM, disk I/O, network) is key to identifying bottlenecks and guiding your optimization efforts. Tools like htop, atop, iotop, iftop (Linux) or performance monitor (Windows) are invaluable for this purpose.

Technical Q&A

This section addresses common technical questions that arise during the setup, maintenance, and operation of a World of Warcraft private server for older expansions.

Q1: What is the difference between authserver and worldserver? A1: The authserver (authentication server) is responsible for handling player logins. When a player launches their World of Warcraft client and attempts to connect, the client first communicates with the authserver. This server verifies the player's account credentials (username and password) against the database. If the credentials are valid, the authserver then directs the client to the appropriate worldserver instance. The worldserver is the core component that manages the actual game world. It handles all in-game logic, including player movement, spell casting, NPC behavior, quest progression, item interactions, and synchronization of game state among all connected players. In essence, authserver is the gatekeeper, and worldserver is the entire world within.

Q2: Can I run multiple worldserver instances on a single machine? A2: Yes, it is technically possible to run multiple worldserver instances on a single powerful machine. This is often done to host different realms (e.g., a PvP realm and a PvE realm) or to distribute the load of a very large server across multiple processes, each managing a specific zone or continent. However, each worldserver instance will consume its own set of CPU, RAM, and database connection resources. You would need to configure each worldserver to listen on a different port and ensure they are correctly linked to the authserver and the shared database. This approach requires careful resource management and advanced configuration.

Q3: How do I update my emulator without losing player data? A3: Updating your emulator (e.g., moving from one version of TrinityCore to a newer one) requires a careful process to preserve player data.

Backup Everything: Before starting, create a full backup of your entire database (all world, characters, auth databases) and your emulator's configuration files. This is non-negotiable.

Stop Servers: Gracefully shut down both your worldserver and authserver.

Update Source Code: Download the latest source code for your emulator.

Compile: Compile the new source code.

Database Migrations: The most critical step. Newer emulator versions often come with SQL migration scripts (e.g., updates/world/, updates/characters/) that modify your existing database schema to be compatible with the new emulator version. You must run these scripts in the correct order against your existing databases. Failure to do so will result in data corruption or server startup failures.

Review Configuration: Check for any new or changed configuration options in the updated emulator's *.conf files.

Start Servers: Start the authserver and worldserver and monitor logs for errors. It's highly recommended to test the update process on a staging server or a local copy of your database first ( Database System Concepts ).

Q4: What is the realmlist.wtf file and why is it important? A4: The realmlist.wtf file is a small text file located in the Data/enUS (or equivalent locale) folder of your World of Warcraft client installation. It contains a single line that specifies the IP address or domain name of the authentication server (authserver) that your client should connect to. For a private server, you must edit this file to point to your server's public IP address or domain name. For example, set realmlist 192.168.1.100 or set realmlist mywowserver.com. Without the correct realmlist.wtf entry, your client will attempt to connect to the official Blizzard servers or a default address, preventing you from accessing your private server.

Q5: How can I protect my server from DDoS attacks? A5: Distributed Denial of Service (DDoS) attacks are a significant threat to private game servers.

Hosting Provider DDoS Protection: The most effective first line of defense is to choose a hosting provider that offers robust, always-on DDoS mitigation as part of their service. These providers have specialized hardware and software to detect and filter malicious traffic before it reaches your server.

Firewall Rules: Configure your server's firewall (e.g., iptables on Linux) to only allow necessary ports (e.g., 3724, 8085) and to rate-limit connections from suspicious IP addresses.

CDN/Proxy Services: For web-facing components (like account creation websites), using a Content Delivery Network (CDN) or a reverse proxy service (like Cloudflare) can help absorb and filter some types of DDoS attacks.

IP Blacklisting: If you identify specific IP addresses launching attacks, you can temporarily or permanently blacklist them using firewall rules.

Monitoring: Implement network monitoring to detect unusual traffic patterns that might indicate an impending or ongoing attack.

Q6: What are GM commands and how do I use them? A6: GM (Game Master) commands are special in-game commands that allow administrators to perform various actions, such as spawning items or creatures, teleporting players, modifying character stats, or resolving player issues. These commands are typically entered into the in-game chat window, prefixed with a special character (e.g., .command or /command). To use GM commands, your in-game account must be assigned a specific GM level or rank in the server's database. The available commands and their syntax vary slightly between emulators, but common ones include .tele, .additem, .go xyz, .character level, etc. Emulator documentation or community wikis provide comprehensive lists of available GM commands.

Q7: My server is crashing with "out of memory" errors. What should I do? A7: "Out of memory" errors indicate that your server has exhausted its available RAM.

Increase RAM: The most direct solution is to upgrade your server's RAM.

Optimize Database: Ensure your database's innodb_buffer_pool_size is not set excessively high, leaving insufficient RAM for the operating system and emulator processes. Conversely, if it's too low, the database might be constantly reading from disk, leading to performance issues that can indirectly cause memory pressure.

Reduce Player Cap: Temporarily lower the maximum number of concurrent players allowed on your server.

Review Emulator Configuration: Reduce resource-intensive settings like high spawn rates, complex AI, or excessive logging.

Check for Memory Leaks: While less common in stable emulator releases, custom scripts or modules could have memory leaks. Monitor memory usage over time to see if it steadily increases without releasing.

Swap Space: Ensure you have adequate swap space configured as a safety net, though relying on swap heavily will degrade performance.

Q8: How do I backup my server? A8: A robust backup strategy is essential.

Database Backup: This is paramount. Use mysqldump (for MySQL/MariaDB) to create logical backups of your auth, characters, and world databases.

mysqldump -u [username] -p[password] --databases auth characters world > /path/to/backup/wow_backup_$(date +%Y%m%d%H%M%S).sql

Automate this with cron jobs.

Configuration Files: Back up your worldserver.conf, authserver.conf, and any other custom configuration files.

Emulator Binaries/Scripts: Back up your compiled emulator binaries and any custom scripts or modules.

Off-site Storage: Store backups on a separate machine, cloud storage (e.g., S3, Google Drive), or an external drive. Never keep all backups on the same server as the live data.

Test Restores: Periodically test your backups by attempting a full restore to a separate machine to ensure their integrity.

Q9: Can I change the experience rates or drop rates on my server? A9: Yes, most World of Warcraft emulators provide configuration options to adjust various game rates. These settings are typically found in the worldserver.conf file. Look for parameters like Rate.XP.Kill, Rate.XP.Quest, Rate.Drop.Item, Rate.Drop.Money, etc. You can modify these values to create a "blizzlike" (official server-like), "funserver" (high rates), or any custom experience you desire. Remember to restart your worldserver after making changes to the configuration file for them to take effect.

Q10: What is the best way to manage my server remotely? A10:

SSH (Secure Shell): For Linux servers, SSH is the primary and most secure method for remote management. It provides a command-line interface. Use an SSH client like PuTTY (Windows) or the built-in terminal (Linux/macOS).

SFTP/SCP: For transferring files securely, use SFTP (SSH File Transfer Protocol) or SCP (Secure Copy Protocol). Tools like WinSCP (Windows) or scp command (Linux/macOS) are excellent for this.

Screen/Tmux: For running server processes in the background and detaching from your SSH session, use screen or tmux. This allows your server to continue running even if your SSH connection drops.