Titan Development Log

TitanGambits 2.4.22 changes how server-command buttons send requests after reports that Sort, Optimize and job recruitment sometimes echoed a /say command without completing. These controls previously used the client text-command queue. They now send ordinary game command packets directly, avoiding that interpreter. We reproduced an accepted queue entry with no outgoing command in a transport simulation; the exact client condition behind the reported failures remains unconfirmed.

Sort, Optimize, balanced recruitment, individual job recruitment, release and Gambit control buttons now attach request IDs and wait for matching server receipts. Lost requests or receipts can retry up to four times over ten seconds. The server remembers each request, so a retry does not sort twice, summon another recruit or apply a switch twice. Pending duplicate clicks are combined, control changes stay in order, master OFF cancels older queued clicks, and requests cancel after a character or zone change. If confirmation remains unknown, queued clicks are discarded and the plugin asks you to check the result before trying again.

All existing recruitment cooldowns, party and leadership requirements, job availability, inventory restrictions and equipment checks remain in place. A control receipt means the original command handler ran; its normal result messages and confirmed settings still determine whether the requested action succeeded. Sort and Optimize results now use Emotes, which appears in Window 2 with Titan's default chat settings. Read-only status polling also bypasses the text queue, while combat actions retain their existing receipts and are not replayed as delayed button clicks.

LuaJIT regression checks exercised the actual addon, request handlers and individual job commands with simulated packet loss and mocked native operations, including lost replies, duplicate requests, cancellations, exceptions and stale or spoofed receipts. Inventory browser and relevant background-pacing checks also passed. Fresh in-game button testing is still needed. The launcher delivers this addon update through its managed files; after updating, use /addon reload TitanGambits if already in game. No launcher executable or game-server restart is required.

The Dynamis test addon could time out even when the server received its connection request. Titan's custom string conversion accepts multiple arguments, while the test protocol passed each field together with all fields after it. Replies therefore contained repeated values, and the addon correctly rejected them. The protocol now converts one field at a time. The same repair covers handshake, party polling, diagnostics and result messages without loosening the client decoder.

Fifty LuaJIT checks exercised the actual matching client decoder and protocol, using both standard string conversion and a model of the deployed variadic conversion. They reproduced the old handshake timeout and verified corrected polling, diagnostic fields, reconnects and message lengths. The server module was reloaded through Dynamis's file watcher without restarting either game server. Existing test clients need to connect again; a fresh in-game handshake and continuous diagnostic capture still need tester confirmation. Live Titan gameplay and the native engine are unchanged.

Launcher updates could replace a separately installed Dynamis test addon with an older copy. The public installer was collecting that folder from the packaging machine and overwriting it during installation. The embedded startup addon bundle and public addon-update manifest did not contain the test addon. The installer overwrite was reproduced using the signed previous release.

Public packages now exclude the reserved test-addon folder, and both the installer and public addon updater reject it as managed content. A separately installed test addon and its configuration remain untouched during launcher installation and repeated startup. Tests exercised the signed new installer over a newer test copy, a fresh installation, repeated startup extraction and both update guards. Normal TitanGambits remains available through its existing public release path. The launcher and installer are Microsoft Artifact Signed, and the graphics fixes from 1.6.12 are retained. No Titan or Dynamis game services were restarted.

DLSS 5 could close the game before its window opened even after the separate neural helper passed its 300-frame test. The supplied dgVoodoo 2.87.2 wrapper crashed while creating the Direct3D 8 interface; the same failure reproduced in an isolated 32-bit test without neural rendering. Clarity now pins the reviewed 2.87.5 wrapper used by the working dgVoodoo mode. That build passed interface and device creation, including the ReShade and feeder combination. Existing managed Clarity installations receive a reversible upgrade that retains personal graphics configuration. Unknown wrappers remain protected from automatic replacement.

A stale boot profile could also override a menu resolution selected in the launcher, including changing 1080p back to 1440p. Resolution choices now take priority when building a launch profile, and a saved choice stays pending across launcher restarts until applied. Both Titan and Dynamis profiles refresh together, while their fresh connection tickets remain separate. Clarity still requires a 4096 by 4096 background buffer; that requirement does not change the selected menu resolution.

The Microsoft Artifact Signed launcher and installer passed 35 shared-settings checks and 21 existing interface checks. Fifteen managed graphics checks covered installation, helper evaluation, mode switching, unknown-file rejection and interrupted-write recovery. A genuine older Clarity installation also passed upgrade, personal-setting preservation and restoration checks. These tests verify the repaired startup path and settings behavior; a fresh FFXI launch and Titan/Dynamis switching still need player confirmation. No game server restart was required.

The Adventurers page now opens with All selected, followed by Online and Offline. All includes both groups and keeps online characters above offline characters for every sort option. Your selected sort applies within each group, and name searches and pagination continue to work. Online still shows only online characters, and Offline still shows only offline characters.

Titan and Dynamis now use the same launcher settings for graphics, input, extensions, fonts and preserved custom preferences. Previously, Dynamis merged an older boot profile into the selected settings, so it could retain different values. Both launch buttons now use one canonical preference profile, and a Dynamis launch updates that shared profile before a later return to Titan. The server name and fresh connection ticket remain separate.

The old advanced graphics control allowed presentation flags through 7, including flags that FFXI's Direct3D 8 interface does not support. A local GPU test reproduced the reported 0x8876086C startup error with flags 7; the same test opened a device successfully with flags 0 and 1. The control now accepts only -1 for the game default, 0 or 1. Unsupported saved values are backed up and reset to the game default. Both server profiles and launcher preferences are preserved before migration. Clarity also enforces its required 4096 by 4096 background resolution after preference merging, preventing an older profile from overriding the depth-filter setup.

The Microsoft Artifact Signed launcher and installer passed signature verification. Testing covered 31 configuration checks, including a Titan-to-Dynamis-to-Titan round trip, all four graphics modes, save/reload, custom settings, migration backups and connection-ticket separation, plus 21 existing launcher interface checks. A fresh in-game round trip still needs player confirmation. No Titan or Dynamis game services were restarted for this launcher update.

Dynamis is testing a change for enemies that continue chasing into the character holding their attention after reaching melee range. An active chase could bypass the existing in-range settling check. The test build now allows a clear-route chase to settle within attack range and limits the approach step so faster monsters do not run past their stopping distance.

The change preserves the enlarged Colossus hitboxes and existing attack reach. Ranged and skill-list monsters retain their previous movement behavior. On a fixed outdoor route, the old engine failed seven of eight spacing scenarios; the new engine passed all eight, covering normal and enlarged hitboxes, several movement speeds, a moving target and a monster that must remain stationary. The complete local test build passed all 205 gameplay regression scenarios.

This movement change is available on Dynamis only; live Titan is unchanged. Real-player testing around corners, obstacles and crowded fights is still needed. Please report monsters that stop out of reach or still crowd their target.

The separate TitanGambits test addon on Dynamis now supports detailed buff evidence. With Diagnostics set to Decisions or Trace, it records native effect insertion, rejected applications, changes, removals and selected action or target rejections. It distinguishes a landed effect from a cast message and reports the duration and source when the engine can identify them. Unknown sources and removal causes remain unknown.

Diagnostics still start OFF and use a five-minute capture lease. Choose OFF, then Decisions to begin a fresh capture; the panel shows its session, sequence, dropped-record and write-error counters. Logging uses anonymous actor aliases and fixed numeric fields, with a global limit of 50 records per second and four rotating 4 MiB files. Missing or dropped records cannot prove that a buff never occurred.

The supplied changes were merged into Dynamis’s current code. Current medicine pacing, Auto action switches, melee/ranged WS modes, recruitment and mission routes were preserved. The test addon retains the official 2.4.21 interface and uses separate test configuration. Testers must unload the official addon before loading TitanGambits_Test and explicitly connect its test controls.

Both diagnostics-enabled and diagnostics-disabled local builds passed all 197 native regression scenarios. A separate local engine Protect cast was recorded through application, duration/power changes and removal, with a continuous sequence, zero dropped records and zero write errors. These tests are not completion of the supplied gameplay checklist; broader multi-job buff interactions and performance under gameplay load still need invited tester checks. This release is for Dynamis only. Live Titan gameplay and the public launcher-managed addon were not changed.