Chore: Rename Eluna to ALE (#344)

docs/IMPL_DETAILS.md

@@ -45,7 +45,7 @@ ALE settings are located in the AzerothCore server configuration file.
 Reload scripts during development with:
 
 ```
-.reload eluna
+.reload ale
 ```
 
 > [!CAUTION]
@@ -160,7 +160,7 @@ end
 #### Safe to Store
 
 These userdata objects are Lua-managed and safe to store:
-- Query results (`ElunaQuery`)
+- Query results (`ALEQuery`)
 - World packets (`WorldPacket`)
 - 64-bit numbers (`uint64`, `int64`)
 
@@ -384,7 +384,7 @@ Check these locations for errors:
 
 Enable traceback in the server config for detailed error information:
 ```
-Eluna.TraceBack = 1
+ALE.TraceBack = 1
 ```
 
 This adds call stack information to errors.
@@ -394,7 +394,7 @@ This adds call stack information to errors.
 1. **Start Small**: Test basic functionality first
 2. **Add Gradually**: Implement features one at a time
 3. **Test Each Step**: Verify each addition works before moving on
-4. **Use Reload**: Use `.reload eluna` for quick iteration (dev only)
+4. **Use Reload**: Use `.reload ale` for quick iteration (dev only)
 5. **Full Restart**: Always do final testing with a server restart
 
 ### Common Issues

docs/INSTALL.md

@@ -127,23 +127,23 @@ cmake --build . --config Release
 The compilation process generates updated config files with ALE settings. Without these, ALE may not function correctly (no error messages, logging issues, etc.).
 
 **Location of config files:**
-- Usually in your server's `etc/` or `configs/` directory
-- Look for files like `worldserver.conf`
+- Usually in your server's `etc/modules` or `configs/modules` directory
+- Look for files like `mod-ale.conf`
 
 Copy the new `.conf.dist` files:
 
 ```bash
 # Example - adjust paths as needed
-cp worldserver.conf.dist worldserver.conf
+cp mod-ale.conf.dist mod-ale.conf
 ```
 
 Then edit `worldserver.conf` and configure ALE settings (see [Configuration](#-configuration) below).
 
 ## ⚙️ Configuration
 
-### ALE Settings in worldserver.conf
+### ALE Settings in mod-ale.conf
 
-After installation, configure ALE by editing your `worldserver.conf` file:
+After installation, configure ALE by editing your `mod-ale.conf` file:
 
 ```ini
 ###################################################################################################
@@ -152,24 +152,16 @@ After installation, configure ALE by editing your `worldserver.conf` file:
 
 # Enable or disable ALE
 # Default: 1 (enabled)
-Eluna.Enabled = 1
+ALE.Enabled = 1
 
 # Enable traceback for detailed error information
 # Useful for debugging but has performance overhead
 # Default: 1 (enabled)
-Eluna.TraceBack = 1
+ALE.TraceBack = 1
 
 # Script folder location (relative to server binary)
 # Default: "lua_scripts"
-Eluna.ScriptPath = "lua_scripts"
-
-# Logging level
-# 0 = Disabled
-# 1 = Errors only
-# 2 = Errors and warnings
-# 3 = All messages (debug)
-# Default: 2
-Eluna.LogLevel = 2
+ALE.ScriptPath = "lua_scripts"
 ```
 
 ### Creating the Scripts Folder
@@ -234,7 +226,7 @@ cmake --build . --config Release
 **Check these things:**
 
 1. **Config file**: Ensure you're using the new `worldserver.conf` generated after compilation
-2. **Enabled setting**: Verify `Eluna.Enabled = 1` in config
+2. **Enabled setting**: Verify `ALE.Enabled = 1` in config
 3. **Script path**: Ensure `lua_scripts` folder exists in the correct location
 4. **Logs**: Check server logs for error messages
 

docs/USAGE.md

@@ -236,11 +236,11 @@ end
 For quick testing during development, you can reload scripts without restarting:
 
 ```
-.reload eluna
+.reload ale
 ```
 
 > [!WARNING]
-> **Development Only:** Use `.reload eluna` only for development. For production or if experiencing issues, always restart the server.
+> **Development Only:** Use `.reload ale` only for development. For production or if experiencing issues, always restart the server.
 
 **Important Limitations:**
 - Reloading doesn't trigger events like login for already-connected players