GAMQ Signs 0.1.8

• Makes black the default sign-letter color, so signs require suitable ambient lighting to remain readable at night, while keeping white available as an explicit option.
• Preserves every explicitly saved black or white choice; only new signs and records without a valid stored color use black.
• Makes Cancel and the window close button discard unsaved text and color changes.
• Preserves unsaved text when switching between white and black before saving.
• Aligns the editor and server limits at 120 characters and 4 lines.
• Prevents placement of a nearby sign from rotating an existing sign attached to the same support block. Placement now records the exact PlaceBlockEvent destination and preserves Hytale's preview orientation without searching for or mutating any neighboring sign.
• Removes the obsolete duplicated sign-editor UI resource; the editor now ships only from the canonical GoblinsAteMyQuest UI namespace.
• Removes the former optional module integration, its shared-database adapter, and its release dependency metadata. plugin-data/GAMQ-Signs/signs.json is now the sole sign persistence source and existing explicit colors remain intact.
• Removes the former module-specific claim authorization bridge. GAMQ Signs no longer checks claims itself when a sign is broken; servers that require this protection must enforce it through a separate server-wide block-protection mechanism.
• Requires and validates against stable Hytale 0.6.5 / Update 6 (hytale/3). Earlier 0.5.x, prerelease 0.6.0-pre.x, and other unvalidated versions are no longer advertised as compatible.
• Keeps the validated glyph renderer as the release default. The experimental composed-texture path is not enabled or supported for this release because it failed the real-client performance gate.

Texture-atlas investigation

We carefully evaluated Hytale 0.6.3's dynamic entity-texture atlas path through the server Common Asset publication and rebuild mechanism. The spike composed each sign into a single generated texture and quad, but it did not meet the required client performance level. Every previously unseen sign texture caused a full client Common Asset update and entity-atlas preparation. Captured updates took approximately 0.9-2.1 seconds end to end and produced a visible gameplay stall; client diagnostics attributed 221-336 ms of that work specifically to RebuildEntityRenderers on the main thread, with the remaining time spent in asset and atlas preparation. The composed path is therefore on hold until an incremental texture-update mechanism can avoid the global atlas rebuild.

No sign IDs or stored explicit color values are changed by this release. Existing installations must preserve plugin-data/GAMQ-Signs/signs.json when upgrading; there is no secondary database import path in 0.1.8.

Hytale 0.6.5 compatibility verification

The release was rebuilt against the official stable 0.6.5 server. Automated validation covers Java API, protocol, assets, isolated compilation, Linux Docker boot, and persistence. Real-client validation of the editor, rendering, saved colors, and adjacent sign placement was completed before publication. Compared with 0.6.3, the protocol has no changes and none of the Java API changes map to GAMQ Signs. The official asset changes are limited to the global asset index and pt-BR, uk-UA, and zh-CN language files; GAMQ Signs does not depend on those changed assets.