HyTari Studios · Official configuration guide

My PvP Controls

Give players choice without giving up server control.

PvP is bilateral: a player-versus-player hit is valid only when both players have effective PvP enabled. The server can leave each option to the player or force it ON/OFF.

START THE GUIDE MOD PAGE

BEFORE YOU START

Getting started

STEP 01

Install only one build

Remove old PvPToggle/MyPvPControls builds that would register the same /pvp command.

STEP 02

Define the defaults

Choose PvP state, timers, and initial risk settings.

STEP 03

Choose the authority

For each option choose PLAYER, FORCE_ON, or FORCE_OFF.

The mod is not meant to replace server protections: if another system blocks a hit, My PvP Controls does not re-enable it.

CHAPTER 01 · 1 EXAMPLES

Bilateral PvP

How personal protection works and when a hit is allowed.

01LOGIC

Consent must be mutual

PvP combat is allowed only when both players have effective PvP ON.

LOGIC
Attacker OFF + Target OFF  -> BLOCKED
Attacker ON  + Target OFF  -> BLOCKED
Attacker OFF + Target ON   -> BLOCKED
Attacker ON  + Target ON   -> ALLOWED

Runtime rule

WHAT IT DOES

PvP combat is allowed only when both players have effective PvP ON.

IMPORTANT BEHAVIOR

  • The mod does not force a hit if another protection system already cancelled it.
  • PvE and environmental deaths are not converted into PvP.
  • The effective value also accounts for server-side FORCE_ON/FORCE_OFF rules.

CHAPTER 02 · 1 EXAMPLES

Defaults and timers

Set initial state, saving, combat lock, and cooldown.

01JSON

Defaults and timing safety

Combat timer and cooldown prevent opportunistic setting changes during or immediately after a fight.

JSON
{
  "DefaultPvPEnabled": false,
  "DefaultPvPStatusSave": false,
  "CombatTimerSeconds": 10,
  "ToggleCooldownSeconds": 5
}

mods/MyPvPControls/config.json

WHAT IT DOES

Combat timer and cooldown prevent opportunistic setting changes during or immediately after a fight.

IMPORTANT BEHAVIOR

  • CombatTimerSeconds locks changes while the player is in active PvP combat.
  • ToggleCooldownSeconds prevents rapid ON/OFF switching.
  • Saving the PvP state is separate from the other risk values.

CHAPTER 03 · 1 EXAMPLES

Risk and item loss

Item Drop, Full Inventory Drop, and Durability are separate controls.

01JSON

Personal risk defaults

Item Drop, Full Inventory Drop, and Durability can be chosen independently.

JSON
{
  "DefaultItemDrop": false,
  "DefaultFullInventoryDrop": false,
  "DefaultItemDurability": true
}

mods/MyPvPControls/config.json

WHAT IT DOES

Item Drop, Full Inventory Drop, and Durability can be chosen independently.

IMPORTANT BEHAVIOR

  • Full Inventory Drop takes priority over normal Item Drop.
  • With Item Drop disabled, qualifying PvP deaths use Hytale's native NONE mode.
  • Durability protection applies to valid PvP and does not alter normal PvE wear.

CHAPTER 04 · 1 EXAMPLES

Server controls

PLAYER, FORCE_ON, and FORCE_OFF determine who has the final say.

01JSON

PLAYER, FORCE_ON and FORCE_OFF

Each option can remain under player control or be locked by the server.

JSON
{
  "PvPControl": "PLAYER",
  "PvPStatusSaveControl": "PLAYER",
  "ItemDropControl": "PLAYER",
  "FullInventoryDropControl": "PLAYER",
  "ItemDurabilityControl": "PLAYER"
}

mods/MyPvPControls/config.json

WHAT IT DOES

Each option can remain under player control or be locked by the server.

IMPORTANT BEHAVIOR

  • PLAYER lets the player choose.
  • FORCE_ON forces the value on.
  • FORCE_OFF forces the value off.
  • The GUI always shows the effective value after server rules are applied.

CHAPTER 05 · 1 EXAMPLES

Player data and logs

Choose storage backend, PvP audit logging, and retention.

01JSON

Storage and audit

Preferences can live in the mod folder or in the player's Hytale profile.

JSON
{
  "PlayerData": {
    "Storage": "MOD_FOLDER"
  },
  "Logs": {
    "FileLogging": true,
    "ConsoleLogging": false,
    "AutoPurgeEnabled": true,
    "AutoPurgeDays": 30
  }
}

mods/MyPvPControls/config.json

WHAT IT DOES

Preferences can live in the mod folder or in the player's Hytale profile.

IMPORTANT BEHAVIOR

  • MOD_FOLDER uses readable JSON files under playerdata/.
  • PLAYER_PROFILE is useful on networks that already synchronize Hytale profiles.
  • Switching backend does not automatically migrate existing data.
  • The PvP log records the effective values used at the time of death.

CHAPTER 06 · 1 EXAMPLES

Commands and administration

The /pvp panel, player commands, and admin tools.

01COMMANDS

Player and admin commands

The /pvp panel exposes the same controls available through subcommands.

COMMANDS
/pvp
/pvp on | off | toggle | status
/pvp itemdrop <on|off|toggle>
/pvp fulldrop <on|off|toggle>
/pvp durability <on|off|toggle>
/pvp save <on|off|toggle>
/pvp admin config
/pvp admin set <key> <value>

In-game commands

WHAT IT DOES

The /pvp panel exposes the same controls available through subcommands.

IMPORTANT BEHAVIOR

  • Administrative commands require mypvpcontrols.admin.
  • Supported admin changes are saved to config.json.
  • Rules displayed in the panel can be localized and edited per language.

Before using an example

PvE and environmental deaths remain handled by Hytale and the server's other systems.

PLAYER_PROFILE is intended for networks that already know how to synchronize player profiles.

The rule text shown in the GUI can be customized in the language files.

BACK TO TOP