Titan Development Log

TitanGambits 2.4.31 requests fresh Venture Moogle information as soon as you open the page, reopen the window on that page, or use /venture. Previously, reopening could leave the page waiting for its normal 20-second refresh, and other background requests could delay it further. Opening now triggers its own refresh, with a short limit on repeated clicks.

Your current display stays visible until the full server response arrives. Automated LuaJIT checks covered opening and reopening, rapid clicks, stale responses and retry handling, and the existing dispatch and countdown checks still pass. This addon update is available through the launcher and needs no game server restart.

On Dynamis, explicit Recruit distance settings now keep their selected destination across movement ticks. The previous controller could treat a lost temporary destination as an arrival and pause before reaching the requested range. The same consecutive-tick test fails on the previous engine and passes with this change.

Native engine tests confirm RDM, COR and RNG can reach and hold 16-, 17- and 19-yalm positions, including in a full five-role party. Close-attacker hold-ground checks and emergency Cure remain available. Movement recording now distinguishes busy actions, rooting, path rejection, replanning and arrival, and completed diagnostic captures include sequence and loss information.

All 111 scoped native gameplay scenarios and 75 C++ cases passed. Live player acceptance has not been performed because no tester was available. These changes are confined to Dynamis; Titan gameplay and its pending patch have not been activated.

The movement-triggered screen shake on Colossal enemies is disabled on live Titan while we investigate nearby-player client crashes. This effect could send repeated Quake Stomp animations when a Colossal moved near players, including players who had not attacked it. That makes it a possible contributor, but the crash cause has not been confirmed.

We removed the two movement-effect listeners from all 82 Colossal source monsters and disabled future attachments without restarting the game. The 45 active sets of shake listeners were removed, and the live check confirmed their models, HP, hitboxes and respawn timers were unchanged. Colossals and their rewards remain available; this change disables only their custom movement effect.

TitanGambits 2.4.30 shows the active expedition countdown on all three expedition choices, all 13 Moogle choices and the Send button. These controls stay locked while a Moogle is exploring, and the running Moogle stays highlighted. When the timer reaches zero, the buttons show that the return is being confirmed; dispatch unlocks only after the server reports that the assignment has ended.

The extra expedition advice, exploring status and unavailable-on-expedition lines have been removed from above the Moogle choices. Moving the timer into the existing buttons keeps the normal active and idle layouts aligned. The updated addon is available through the launcher, with no game server restart.

The Send Moogle button was disabled because the Venture worker had stopped with the map server during recovery and was not started again. The worker is running again and its heartbeat is current. It now starts with the map service, and worker failures have bounded retries without restarting the game.

Automatic crash recovery now blocks player connections, preserves and clears stale login sessions after the game endpoints have stopped, and checks that the Guild and Venture heartbeats advance for at least 25 seconds. It clears maintenance before starting a fresh login process so the previous GM-only setting cannot remain cached. If verification fails, the server stays in maintenance and automatic map restart loops are stopped.

These hooks were installed without restarting the running game. The isolated recovery and session-cleanup checks passed, and both live worker heartbeats were current after installation. We have not deliberately crashed the live server to test the complete recovery path. Existing expedition costs, rewards and delivery transaction rules are unchanged.

After the Guild recovery, ordinary players were still being rejected by GM-only maintenance mode. The settings file had been changed, but the running login service retained the old setting. We restarted only the login service so it would load maintenance as disabled. The game map stayed running, and Guild maintenance continued advancing. The earlier reopening announcement was premature; we are checking ordinary player logins separately from GM access.

Players were being left on a black loading screen after startup, while the Mercantile Guild stopped working. We traced this to the WotG recipe eligibility update: excluded items could return an empty result instead of false. The native worker expected a boolean, and the invalid result interrupted its scheduled task while leaving a database transaction open. The check now always returns true or false, without changing which items the Guild is allowed to handle.

The correction is installed on Titan and Dynamis. We cleared 11 stale Titan login records while its game endpoints were stopped, verified a GM could enter the world, and reopened player connections after the Guild heartbeat and crafting resumed normally. Both engines passed the scoped regression checks, including eligibility checks across all 65,536 item IDs.

The earlier server abort reported after a Colossal Mandragora kill has not yet been conclusively explained. Local death, disappearance and respawn tests passed, and a controlled live Mandragora kill awarded Sparks and disappeared normally without a reported client crash or invisible monster. This recovery did not replace the game engine or roll back the Colossal packet changes.

TitanGambits 2.4.29 removes the Refresh Venture Moogles button. The page continues to request current progress, Sparks balance and delivery history automatically every 20 seconds while open. The update is available through the launcher.