Update 0.1.9

Update 0.1.9

Upcoming / in development — not yet publicly released. This page documents implemented additions targeted for 0.1.9, including experimental features and their current boundaries. Public 0.1.8 remains the released download. This is documentation, not a release announcement or a client/server deployment.

Server-controlled item statistics

Item type stats introduces eight server Lua functions:

• getItemTypes, getItemStats, getItemStatDefinitions
• setItemStats, setItemStatsBatch, resetItemStats
• getItemStatsProfile, replaceItemStatsProfile

One profile changes every copy of the same item type on that server, not individual inventory instances. Supported fields cover weapon and ammunition damage, seven damage/protection channels, armor and jewelry bonuses, equipment requirements, consumable restoration/regeneration, appropriate rune settings, and available common metadata such as value and stack size. See Item stat properties for exact support and ranges.

Changes are validated atomically, resource-owned, reversible and replayed to compatible joining clients. Profiles can be saved/restored by Lua. onPlayerItemStatsReport reports client application diagnostics; it is not authoritative proof of damage, inventory or gameplay success.

The bundled GothicRP generated native-item metadata follows configured value/weight/stack-size values; separately authored gamemode item/shop definitions remain the gamemode's responsibility. Changing stack size does not delete or rearrange existing quantities.

Armor, jewelry and NPCs

Ordinary armor defense values can be configured directly, independently for cutting, blunt, piercing, fire, wind, ice and energy damage. Armor/player bases and bonuses are kept separate. Raising maxima does not heal/refill; lowering them clamps current values when needed.

Explicit armor HP/mana/strength/dexterity bonuses also affect equipped scripted NPCs. NPC maximum setters use base values; getters return effective values. Combat-config dexterity remains a base value, and getNpcData exposes the new breakdown. Profile refresh does not intentionally reload ammunition or restart accepted attacks/casts. See NPC scripting and Item type stats.

Numeric ring/amulet overrides support the normal inventory equip/remove workflow and two owned identical rings. Reset-while-worn and multi-client lifecycle cases remain under qualification; NPC jewelry is not introduced.

Rune settings and mana recovery

Appropriate implemented runes support damage, range, duration and magic-circle requirements. A custom manaCost is a fixed cost per accepted release; zero means free and resetting restores original cost rules. It preserves other spell eligibility checks. Custom paid/free/reset casting still requires final in-game qualification.

The client also corrects a stale out-of-mana state after a successful positive mana assignment. This addresses cases where mana was visible in the HUD but casting remained blocked until restarting the game. The baseline Fire Bolt/Light and empty/refill sequence has been confirmed in game without restarting. The fix does not grant spells or bypass circle, ownership or equipment requirements. Scroll support is not added.

Interactive map-editor objects

The experimental Interactive map objects extension adds a searchable catalogue of 18 seat variants and 48 light/flame variants, editor placement/transforms, duplicate/history, prefab-aware save/open/export, initial light state and local native testing. Interactive prefab catalog lists all entries.

MapEditor.CreateInteractiveObject is a new editor-resource client helper. Preview/local-test transform alignment and deferred seat cleanup were corrected; cleanup waits for native release and a 1-metre clearance. These additions are distinct from the existing static-object API.

Shared multiplayer interactions for newly placed objects are not finished. The editor preview is static; Test native is local. Version-2 interactive maps cannot be deployed with the existing static-only map_scene loader. Beds, workshops and quest mechanisms are not enabled by this feature.

Scope and release status

Ordinary armor protection and armor-upgrade-slot effects are implemented; see the armor guide for catalog coverage and remaining visual qualification. Special haste/orc-spore/joint effects, critical-hit multipliers, stagger damage and NPC toughness are not advertised as writable. Consult getItemStatDefinitions rather than assuming all engine fields are supported.

In-game tests have confirmed selected potion and life-jewelry scenarios, not every item, tooltip, equipped-reset case or remote/late-join lifecycle. Experimental features remain marked as such until qualification is complete. No release date, final build number or protocol number for 0.1.9 is announced here. Use matching supported client/server versions when the update is released.

Armor bases and upgrade pieces (from 0.1.9)

Not yet publicly released; not included in public 0.1.8. Armor catalog lists all 26 bases (24 existing plus Royal Guard and Judge additions); Armor upgrade catalog lists all 84 authored parts and exact family presets. Armor upgrades explains ownership, full sets, individual slots, players/NPCs, numeric protection and persistence.

Eight new server functions: getArmorUpgrades, getArmorUpgradePresets, getPlayerArmorUpgrades, setPlayerArmorUpgrades, setPlayerArmorPreset, getNpcArmorUpgrades, setNpcArmorUpgrades, setNpcArmorPreset. Local-player and NPC checks are reported working; remote-human/late-join visual qualification remains pending. This is documentation, not a release announcement.

Female identity presentation

The existing syra, velaya, seraphia, chani and natalia identities receive corrected facial proportions, addressing stretched faces on female characters, including while wearing armor. The correction covers local players, remote human players and scripted human NPCs.

A matching identity without armor displays its full authored female body/outfit; an equipped armor keeps its original shape and selected pieces with the corrected female head. Facial expression is currently neutral. Existing setPlayerIdentity and setNpcIdentity APIs are used; no separate female API is introduced. See Female identities for usage, skin/tattoo limits and synchronization expectations. This is part of the upcoming 0.1.9 update, not a public release announcement.