Titan Development Log

TitanCasketHints 1.2.1 recognizes more casket appearance messages, including found, dropped and appearing caskets. This helps it clear the previous lock when a new casket arrives. If a clue leaves no possible combination, the helper now tries that clue against a fresh 10-99 list instead of keeping the previous lock candidates. An impossible clue is still ignored.

The helper remains chat-only: it suggests possibilities from clues received by your client and never submits guesses. The new file is included in the launcher-managed addon update and the fresh installer. Lua 5.1 tests cover resets, conflicting clues, duplicate messages and on/off controls; an in-game check has not yet been performed.

Launcher 1.5.98 and its installer are Microsoft Artifact Signed. Existing settings are preserved, and no game-server restart is required.

Client downloads were occupying most of the system disk. They now use a dedicated data volume, with their existing URLs, manifests and file contents preserved. Every copied file was verified before the switch, including hard links shared between releases.

The new drive uses one shared filesystem, with separate downloads and test directories so either can grow as needed. The migration required no game-service restart or launcher update. Space is available for a future test environment; the test server itself has not been installed.

The release uploader previously relied on a hard link between its upload area and public storage, which cannot work across separate disks. It now verifies a destination-side copy before making the archive available. Manifests and replacement files also use verified temporary files and atomic renames, and temporary upload URLs are blocked so players cannot download a patch while it is being written.

Historical release packages, older rollback copies and inactive build files were taking up space needed for future updates. We moved the reviewed files to separate backup storage and checked every archived file against its original SHA-256 before removing the obsolete server copies. The active game files, player downloads, current rollback backup and pending update remain available.

This storage cleanup did not restart game services or change gameplay.

Rampaging Ram and Lumbering Lambert now return on independent one-hour timers after defeat. Hunting ordinary rams is no longer required to trigger their placeholder lotteries, so Purple Belt hunters can look for the NMs directly.

Steelfleece Baldarich and Bloodtear Baldurf also spawn independently, with a 21-hour timer after defeat. Previously, reaching their 21-hour cooldown only made them eligible for a chance to appear when the lower-tier ram despawned. That extra lottery and placeholder requirement are removed, and the rams no longer block one another from spawning.

Their existing loot, combat behavior and spawn locations are unchanged. Remaining timers survive server restarts, and the transition preserves tracked cooldowns and NMs already up. Local Lua runtime and spawn-data checks passed; observation of the full respawn cycles in game remains pending.

Tank, DPS and Healer cards now use the standard job AI without selectable role presets. Their preset buttons have been removed, and old saved selections no longer alter healing thresholds, resource use or weapon-skill decisions. Tanks coordinate automatically through the normal AI.

Support keeps its two priority selectors. Master pause, player opt-in, Recruit defaults, melee switches and individual Release controls remain available. LuaJIT profile tests, native preference tests and Support, Ranger and following regressions passed; live gameplay confirmation remains pending.

Your recruits now have a Release button beneath their role controls. It dismisses the recruit you selected, even if another recruit uses the same template. The button appears only on recruits you own, never on player characters.

Ranger recruits could stop outside shooting range with Melee OFF: their 15-yalm standback position exceeded the default 14-yalm ranged-attack limit, and movement tolerance could also leave them too far away. Their standback distance now accounts for both the native attack range and that tolerance. With Melee ON, generated Rangers move into melee range; player movement remains manual.

A selected melee weaponskill could also prevent an ordinary shot while Melee was OFF, even though that weaponskill could not execute. Those melee-only choices are now excluded earlier, and Ranger weaponskills are checked before ordinary shots so a failed weaponskill attempt can fall through to shooting. Native recasts and action-state protections remain in place. The native build and targeted regressions passed; live combat and in-game visual confirmation remain pending. Use launcher Check Files after activation to receive TitanGambits 2.4.6.

Joining an alliance through the Yes/No prompt or !join now sends its confirmation to the Emotes channel, alongside Titan's other gameplay notices. The confirmation previously used the default system channel and appeared as a purple SystemMessage. It now follows your Emotes window setting, including Window 2. Both acceptance paths passed LuaJIT regression checks; in-game display confirmation remains pending.

The Plugins and Addons lists show their original names again, including nheatx, pivot, XIView and butterfeet. Click a name for its description or hover for a short summary; the checkbox still controls whether it loads. Existing selections are preserved.

Enhanced Maps could block launch with an XIView error even when XIView was unchecked. Both options used a helper that rejected any custom Pivot root folder. The launcher now prepares verified overlay files in separate Titan subfolders under a full drive or UNC custom root, keeps personal overlays in their existing order, and uses a separate launch configuration without editing the original Pivot settings or base game DATs.

XIView and Enhanced Maps work independently or together through the corrected preparation path. Relative, quoted or environment-variable root values receive a feature-specific message requesting a full folder path rather than being guessed. Configuration and copy tests passed; in-game texture rendering remains unverified. The launcher and installer are Microsoft Artifact Signed, and no game-server restart was needed.

ButterFeet is now available in the launcher Addons list as an optional download, off by default. It removes client-side movement locks during job abilities and engagement; it does not shorten server cooldowns. Click its name for a description or hover for a short summary, then use its checkbox to download and enable it for the next launch.

The Ashita v4 addon is pinned to a reviewed upstream revision with its original license notices preserved. Titan adds a missing-address guard so failed memory scans do not write to an invalid address. Load/unload restoration and missing-address cases passed isolated tests; in-game animation behavior has not yet been confirmed on Titan. Disable the addon before the next launch to return to normal behavior.

The launcher and installer are signed with the Titan Microsoft Artifact Signing identity. This release does not restart game services or activate the deferred Ranger and Gambits patch.

We're making our patch-note writing guidelines a required part of every Development Log update. When a bug's cause is verified, the notes should explain what players experienced, what went wrong, and how the correction changes the game. Useful technical details belong in that explanation; vague claims that something was improved do not.

New features should explain how they work, including relevant numbers, requirements and limitations. When a cause is unknown or a result still needs confirmation, we'll say so. These guidelines now sit in the workspace instructions and publication checklist, with a review of the final prose required before posting. This changes our release-writing process, not gameplay.