Hytale new guides & tweaks

docs/hytale-commands.md

@@ -0,0 +1,131 @@
+---
+id: hytale-commands
+title: "Hytale: Commands List"
+description: "Overview of available console and in-game commands for Hytale servers → Learn more now"
+sidebar_label: Commands List
+services:
+- gameserver-hytale
+---
+
+import InlineVoucher from '@site/src/components/InlineVoucher';
+
+## Introduction
+
+Hytale servers provide a wide range of commands that allow administrators to manage gameplay, players, worlds, and server configuration. These commands can be executed either through the live server console or directly in-game, provided the required permissions are available.
+
+![](https://screensaver01.zap-hosting.com/index.php/s/2yJ6G3AWCDfAHMj/download)
+
+This page provides an overview of commonly used and officially documented Hytale server commands.
+
+<InlineVoucher />
+
+
+
+## Authentication
+
+Authentication commands are required to authorize the server so it can accept player connections and interact with Hytale online services.
+
+| Command               | Description                                                  |
+| --------------------- | ------------------------------------------------------------ |
+| `/auth login device`  | Starts the device-based authentication flow. The server outputs a URL and device code that must be confirmed using a Hytale account. |
+| `/auth login browser` | Starts a browser-based authentication flow. Requires a graphical environment on the server. |
+| `/auth status`        | Displays the current authentication status of the server.    |
+| `/auth logout`        | Logs the server out and removes the active authentication session. |
+
+
+
+## Player & Permission
+
+These commands control administrative access and fine-grained permission assignment for users and groups.
+
+| Command                                   | Description                                             |
+| ----- | - |
+| `/op add <PlayerName>`                    | Grants operator privileges to the specified player.     |
+| `/op remove <PlayerName>`                 | Revokes operator privileges from the specified player.  |
+| `/perm user list <uuid>`                  | Displays all permissions directly assigned to the user. |
+| `/perm user add <uuid> <permission>`      | Assigns one or more permissions directly to the user.   |
+| `/perm user remove <uuid> <permission>`   | Removes specific permissions from the user.             |
+| `/perm user group list <uuid>`            | Shows all permission groups the user is assigned to.    |
+| `/perm user group add <uuid> <group>`     | Adds the user to the specified permission group.        |
+| `/perm user group remove <uuid> <group>`  | Removes the user from the specified permission group.   |
+| `/perm group list <group>`                | Lists all permissions assigned to a group.              |
+| `/perm group add <group> <permission>`    | Adds permissions to a group.                            |
+| `/perm group remove <group> <permission>` | Removes permissions from a group.                       |
+
+
+
+## Whitelist
+
+Whitelist commands restrict server access to approved players only.
+
+| Command                          | Description                                      |
+| -------------------------------- | ------------------------------------------------ |
+| `/whitelist add <playername>`    | Adds the specified player to the whitelist.      |
+| `/whitelist remove <playername>` | Removes the specified player from the whitelist. |
+| `/whitelist list`                | Displays all currently whitelisted players.      |
+| `/whitelist enable`              | Enables whitelist enforcement.                   |
+| `/whitelist disable`             | Disables the whitelist.                          |
+| `/whitelist status`              | Displays the current whitelist status.           |
+
+
+
+## World management
+
+World commands control creation, loading, unloading, and deletion of worlds.
+
+| Command                    | Description                                        |
+| -- | -- |
+| `/world create <name>`     | Creates a new world with the specified name.       |
+| `/world load <name>`       | Loads an existing world and makes it active.       |
+| `/world unload <name>`     | Unloads a world without deleting its data.         |
+| `/world remove <name>`     | Deletes a world and all associated data.           |
+| `/world setdefault <name>` | Sets the default world that loads on server start. |
+
+
+
+## Gameplay and environment
+
+These commands directly affect gameplay rules and world behavior.
+
+| Command                    | Description                                 |
+| -------------------------- | ------------------------------------------- |
+| `/list`                    | Displays all currently connected players.   |
+| `/tp <player> <target>`    | Teleports one player to another player.     |
+| `/tp <player> <x> <y> <z>` | Teleports a player to specific coordinates. |
+
+
+
+## Teleport & Positioning
+
+Commands used to manage player positions and visibility.
+
+| Command                    | Description                                 |
+| -- | - |
+| `/list`                    | Displays all currently connected players.   |
+| `/tp <player> <target>`    | Teleports one player to another player.     |
+| `/tp <player> <x> <y> <z>` | Teleports a player to specific coordinates. |
+
+
+
+## Utility and help
+
+Utility commands provide help and server information.
+
+| Command           | Description                                          |
+| ----- | ---- |
+| `/help`           | Displays a list of available commands.               |
+| `/help <command>` | Displays detailed help for a specific command.       |
+| `/status`         | Shows current server status and runtime information. |
+
+
+
+## Conclusion
+
+The Hytale command system provides powerful tools for managing servers, players, and gameplay behavior.  By understanding and using the available commands, administrators can efficiently operate and customize their Hytale server environment.
+
+ For further questions or assistance, please don't hesitate to contact our support team, which is available daily to assist you! 🙂
+
+
+
+<InlineVoucher />
+

docs/hytale-death-penalty.md

@@ -0,0 +1,117 @@
+---
+id: hytale-death-penalty
+title: "Hytale: Change Death Penalty"
+description: "Discover how death penalties work on your Hytale server → Learn more now"
+sidebar_label: Change Death Penalty
+services:
+- gameserver-hytale
+---
+
+import InlineVoucher from '@site/src/components/InlineVoucher';
+
+
+
+## Introduction
+
+On a Hytale server the **death penalty** determines how players are affected when they die.  This setting controls the extent to which player progress, items, durability, or other gameplay consequences are applied after a death event. 
+
+:::info Early Access Notice
+
+Hytale released on January 13th, 2026 and is currently available in Early Access. As the game is still in an active development phase, server software, configuration files, modding support, and installation workflows may continue to change over time.
+
+:::
+
+<InlineVoucher />
+
+
+## Available Death Penalty Settings
+The death penalty settings control how player deaths affect inventory contents and item durability. These options allow you to define whether items are kept, partially lost, or fully dropped, as well as how much wear items receive upon death.
+
+The following configuration options are available:
+
+**ItemsLossMode**
+ This setting defines the overall behavior of item loss when a player dies.
+ It supports the following values:
+
+- `None` – Players keep their entire inventory after death
+- `All` – All items are dropped on death
+- `Configured` – Item loss is determined by percentage-based settings
+
+**ItemsAmountLossPercentage**
+ This value is only applied when `ItemsLossMode` is set to `Configured`.
+ It defines how much of each item stack is removed upon death, expressed as a percentage.
+ For example, a value of `50.0` means that half of each stack is lost.
+
+**ItemsDurabilityLossPercentage**
+ This setting controls how much durability items lose when a player dies.
+ The value is defined as a percentage of the item’s current durability and allows death to have consequences without fully removing items.
+
+Together, these settings provide fine-grained control over how forgiving or punishing death should be on the server.
+ Careful adjustment ensures a balanced experience that aligns with the server’s intended difficulty and playstyle.
+
+
+
+## Death penalty configuration
+
+The death penalty settings are located within your server’s main `config.json`. These values are read when the server starts and apply globally to all players.
+
+Within the configuration file, the death-related settings are part of the gameplay configuration.  To add or modify the death penalty, locate the following line inside `config.json`:
+
+```
+"GameplayConfig": "Default",
+```
+
+This entry defines the active gameplay configuration profile.  The death penalty configuration is placed directly below this line as a new block. Once located, add the death configuration block to define how respawning and item loss are handled:
+
+```
+"Death": {
+   "RespawnController": {
+     "Type": "HomeOrSpawnPoint"
+   },
+   "ItemsLossMode": "Configured",
+   "ItemsAmountLossPercentage": 50.0,
+   "ItemsDurabilityLossPercentage": 25.0
+ },
+```
+
+The following example shows a typical configuration where item loss and durability loss are partially applied on death:
+
+```
+{
+  "ItemsLossMode": "Configured",
+  "ItemsAmountLossPercentage": 50.0,
+  "ItemsDurabilityLossPercentage": 25.0
+}
+```
+
+In this configuration, the server uses the `Configured` loss mode, meaning item loss is controlled by percentages.
+ When a player dies, half of each item stack is removed and items lose 25 percent of their current durability.
+
+If no item loss should occur at all, the loss mode can be set to `None`, in which case the percentage values are ignored:
+
+```
+{
+  "ItemsLossMode": "None"
+}
+```
+
+For a more punishing experience where all items are dropped on death, the configuration can be set to:
+
+```
+{
+  "ItemsLossMode": "All"
+}
+```
+
+After modifying the `config.json`, the server must be restarted for the changes to take effect.
+ It is recommended to verify the behavior in-game after restarting to ensure the death penalty matches the intended difficulty.
+
+
+
+## Conclusion
+
+With the death penalty configured, you now have a clear overview of how player deaths are handled on your Hytale server. For further questions or assistance, please don't hesitate to contact our support team, which is available daily to assist you! 🙂
+
+
+
+<InlineVoucher />

docs/hytale-firststeps-connect.md

@@ -40,10 +40,9 @@ Using the information mentioned above, you should be able to locate your server
 
 ## Establish server connection
 
+The connection to the server is established using the server **IP address** and **Port**. An optional password may also be required. To do this, open **Servers** in the main menu and click **Add Servers** in the bottom right of the server list. Enter the IP address and port of your server and assign a name or description. Then click on the newly added server to establish the connection. If a password is set for the server, you will be prompted to enter it during the connection process.
 
-The connection to a game server can often be established in one or more ways. Available methods are described and explained in detail below.
-
-The server connection is typically established using the server IP address and port and optionally a password. The exact procedure for connecting to the server will be documented here once the final implementation for the official release is confirmed.
+![img](https://screensaver01.zap-hosting.com/index.php/s/Q6cqdsF3ofXpnid/download)
 
 
 

docs/hytale-gamemode.md

@@ -2,7 +2,7 @@
 id: hytale-gamemode
 title: "Hytale: Game Mode Configuration"
 description: "Discover how to secure your Hytale server by managing player access with whitelist features and protect your gameplay → Learn more now"
-sidebar_label: Whitelist
+sidebar_label: Gamemode
 services:
   - gameserver-hytale
 ---
@@ -32,7 +32,7 @@ The game mode can  be changed while the server is running by using the live cons
 Using the console command updates the active game mode immediately for the server session. Depending on the server setup, the change may persist until the next restart or revert to the value defined in the configuration file.
 
 ```
-/gamemode <gamemode>
+/gamemode <gamemode> <playername>
 ```
 
 The value of `GameMode` determines which game mode is applied when the server starts. Depending on your desired gameplay experience, this value can be adjusted accordingly.

docs/hytale-obtain-uuid.md

@@ -0,0 +1,51 @@
+---
+id: hytale-obtain-uuid
+title: "Hytale: Obtain UUID"
+description: "Discover how to find or obtain a player’s UUID for use in server configuration and permissions → Learn more now"
+sidebar_label: Install Mods
+services:
+  - gameserver-hytale
+---
+
+import YouTube from '@site/src/components/YouTube/YouTube';
+import InlineVoucher from '@site/src/components/InlineVoucher';
+
+## Introduction
+
+Each player on a Hytale server is identified internally by a UUID, also known as a Universally Unique Identifier.  This identifier is permanent and does not change, even if the player later changes their username.
+
+UUIDs are required for various administrative tasks such as managing permissions, assigning groups, or referencing players in server commands and configuration files.
+
+:::info Early Access Notice
+
+Hytale released on January 13th, 2026 and is currently available in Early Access. As the game is still in an active development phase, server software, configuration files, modding support, and installation workflows may continue to change over time.
+
+:::
+
+<InlineVoucher />
+
+
+## Obtain UUID
+
+A player’s UUID can be obtained directly from within the game using the server’s built-in chat command.  This method is especially useful when the player is already online and the UUID is needed immediately.
+
+While logged in with sufficient permissions, open the in-game chat and execute the UUID lookup command for the desired player:
+
+```
+/whoami <playername>
+```
+
+After executing the command, the server responds directly in chat with the UUID associated with the specified player.  The returned UUID uniquely identifies that player and can be copied for use in permission management, group assignments, whitelist entries, or other server-side operations.
+
+
+
+![img](https://screensaver01.zap-hosting.com/index.php/s/E7QrJGn3q79Kzm6/preview)
+
+
+
+## Conclusion
+
+Obtaining a player’s UUID is an essential step in advanced server management tasks on a Hytale server. For further questions or assistance, please don't hesitate to contact our support team, which is available daily to assist you! 🙂
+
+
+<InlineVoucher />

docs/hytale-permissions.md

@@ -1,8 +1,8 @@
 ---
-id: "hytale-permissions"
+id: hytale-permissions
 title: "Hytale: Managing User and Group Permissions"
 description: "Manage user and group permissions on your Hytale server → Learn more now"
-sidebar_label: Slow Connection / World Not Loading
+sidebar_label: Permissions
 services:
 - gameserver-hytale
 ---

docs/hytale-pvp-management.md

@@ -0,0 +1,54 @@
+---
+id: hytale-pvp-management
+title: "Hytale: PvP Management"
+description: "Manage and configure player versus player combat (PVP) on your Hytale server → Learn more now"
+sidebar_label: PVP Management
+services:
+  - gameserver-hytale
+---
+
+import YouTube from '@site/src/components/YouTube/YouTube';
+import InlineVoucher from '@site/src/components/InlineVoucher';
+
+## Introduction
+
+PvP management on a Hytale server controls whether players are able to damage or fight each other within a world.  By adjusting PvP settings, server owners can define if combat between players is fully enabled, completely disabled, or restricted to specific situations.
+
+<InlineVoucher />
+
+
+
+## Configuration
+
+PvP behavior is defined on a per-world basis and configured through the server’s configuration file:
+
+```
+/gXXXXXXX/hytale/universe/worlds/default/config.json
+```
+
+This setting determines how the server handles player-to-player damage and whether PvP is allowed within the active world. Changes to PvP settings apply globally to the affected world and require a server restart to take effect.
+
+The following example shows a configuration where PvP is disabled for a world:
+
+```
+"WorldConfig": {
+  "PvP": false
+}
+```
+
+With this configuration applied, players are no longer able to damage each other within that world, effectively creating a PvE-focused environment.
+
+To enable PvP and allow player-to-player combat, the configuration can be set as follows:
+
+```
+"WorldConfig": {
+  "PvP": true
+}
+```
+
+## Conclusion
+
+Once set up, you have a clear overview of how PvP is managed and can easily adjust the configuration to support cooperative gameplay, competitive environments or a combination of both. For further questions or assistance, please don't hesitate to contact our support team, which is available daily to assist you! 🙂
+
+<InlineVoucher />
+