Titan Development Log

TitanGambits 2.4.28 removes the Sparks balance from the Venture Moogles tab button and returns it to the same height as the other tabs. Your balance still appears at the top of the Venture Moogles page, and expedition choices continue to show their Sparks costs. The update is available through the launcher; no game-server restart was needed.

TitanGambits 2.4.27 makes Venture Moogle expedition prices easier to understand. Each choice now says how many Sparks it costs and how much Moogle EXP it awards, and the Send button names the selected Moogle and the Sparks it will spend. Expedition EXP trains the Moogle; it is not a Sparks reward. Prices and rewards are unchanged.

Use /venture to open Venture Moogles directly. Your server-reported Sparks balance appears at the top and on the tab after status is received. The selected expedition and specialty buttons turn fully green, and Send gently pulses yellow when the selected trip is affordable and dispatch is available. It stays inactive while another expedition or dispatch confirmation is pending, or when a fresh balance is unavailable. The update is available through the launcher and did not require a game-server restart.

Castle Oztroja treasure coffers can now award an Astral Ring in place of a Safeguard Ring. The ring keeps the existing 21% chance in the normal coffer loot roll; gil and gem rewards are unchanged. Map and Artifact quest rewards still take priority when applicable, and treasure chests and other zones are unaffected. The change is active on Titan and was applied without restarting the game server.

The Venture Moogles section on the About page now uses the same cards, body font and spacing as Recruits. Each expedition has its own duration, Sparks cost and EXP summary, followed by smaller sections explaining specialties, rewards and delivery. The oversized bold phrases and mismatched serif paragraphs have been removed. Expedition costs, rewards and gameplay are unchanged.

After today's update, players across multiple zones encountered black screens when entering the world. We found a map-server database transaction that had remained open since startup and reset that database connection. Characters then loaded successfully again, including a confirmed GM login. The trigger that left the transaction open is still under investigation.

We also cleared seven stale online records left by failed logins after checking that those characters were not loaded in the map server. Active characters and recent login attempts were preserved. Titan is open again with the new patch installed; this recovery did not require another game-server restart.

Adventurer profiles now show all eight Ephemeral Moogle crystal balances beneath Professions. These compact counters read saved character data without moving any items or changing stored balances. A deposited cluster counts as 12 crystals; changes appear after the character data is saved and the profile is refreshed.

Multiple Recruits of the same job now retain separate support settings by owner, job and support slot. Level changes preserve each current Recruit’s choices. A replacement takes the lowest vacant support slot; after a full resummon, summon order determines which saved template each Recruit receives. Existing job settings migrate into the first slot, while additional slots begin with defaults. Every newly summoned Recruit still starts with Gambits and all four action switches ON; those switches are not saved into the next summon.

Duplicate COR, BRD and GEO support planning could skip useful choices based on a Recruit’s position among same-job members. They now consider current coverage and accepted support work when choosing their next action. A Recruit tries its selected buffs first, then can fill free support capacity with other useful available effects when those choices are already covered. Player-character selections remain strict. Normal job, level, resource and recast restrictions still apply; a limited repertoire can correctly leave a Recruit waiting.

Bard song ownership could lose part of the singer’s entity ID when crossing the Lua/native interface. Song creation, lookup and removal now preserve the full 32-bit ID, so singers with matching low bits remain distinct. Normal song limits and same-effect/tier overwrite rules are unchanged. The correction applies to newly applied songs; it does not try to reconstruct ownership from old truncated effects.

Summoner support planning now accounts for accepted Hastega, Aerial Armor, Earthen Ward, Shining Ruby and Rolling Thunder requests before their effects land. A pending ward covers only relevant nearby recipients and remains reserved for at most 15 seconds while its provider and pet remain valid. This reduces overlapping requests from multiple Summoners without bypassing MP costs, recasts, action switches or emergency healing. Selecting or summoning an avatar alone does not reserve a ward, so this is not a guarantee of optimal summon MP use.

Player Gambits can now use learned Utsusemi: Ichi with Ninja support job level 12 or higher, and Utsusemi: Ni at support job level 37 or higher. These spells require usable Shihei in inventory and obey normal recasts. Automatic player actions also pause inside a Mog House and resume outside, preventing automatic shadow casting while changing jobs there.

Crawler Sticky Thread was replacing the Haste effect with Slow. It now leaves an existing Haste effect intact and reports no effect; targets without Haste can still receive its normal Slow. This change is specific to Sticky Thread and does not alter other Slow effects.

The website weather feed now records native weather changes immediately instead of waiting for the next 30-second heartbeat. The heartbeat and stale-reading checks remain in place, and website caching and refresh intervals can still delay what a browser displays. Local tests verify the new event path, but the reported historical Qufim discrepancy has not been reproduced against a simultaneous player observation.

Manual recruitment was blocked during One to be Feared and The Warrior's Path because Sealion's Den is classified as a town. These two mission battlefields now pass the town restriction after entry, while the Sealion's Den lobby remains blocked. Encounter registration, party leadership, combat and hate restrictions, the six-participant limit and individual job cooldowns still apply. Native local tests covered recruitment in all three arena copies of each battle. This eligibility correction does not change phase movement, healing or encounter mechanics; full battle completion and phase transitions still need player testing.

Command tracing on Titan and Dynamis now records only approved operation names, request nonces, processing stages and fixed result codes instead of complete command text. Private session keys and command payloads are excluded from these traces, with a limit of 12 trace records per requester per second.

The Dynamis testing protocol was formatting integer replies through an unsigned 32-bit conversion. An idle distance of -100 could arrive as 4294967196, and larger capture IDs could lose their upper bits. TEST replies now use explicit decimal formatting without changing the game-wide formatter. Exact integers through 9007199254740991 and existing decimal strings are preserved; unsafe numeric replies are rejected rather than presented as valid evidence. Authenticated requests above the existing 20-per-second limit can now receive one short retry notice per second. Rejected actions are not automatically replayed. Request-stage tracing has been added, but the separately reported request-79 timeout has not been reproduced or assigned a confirmed cause.

This maintenance package has separate Titan and Dynamis payloads. Titan retains the gameplay changes described above. Dynamis receives the WotG crafting changes below, TEST protocol repairs, command-trace privacy change and the two Sealion’s Den recruitment exceptions, while retaining its private test features and addon. Both engines also receive the Recruit Poison Potion behavior and battlefield entry item cleanup described below. This does not copy Titan’s newer native duplicate-job changes into the private Dynamis engine or introduce a coordinated test-action scheduler, new evidence exports or broader log access.

Wings of the Goddess recipe restrictions prevented crafting items such as Exactitude Mantle even when players had obtained the materials. All 327 existing WotG-tagged recipes are now enabled for player synthesis and desynthesis, with their original skills, crystals, materials, key-item requirements and yields preserved. The Guild can produce eligible synthesis outputs and its crafting services offer 311 recipes, including Exactitude Mantle; the normal level-75 equipment limit, non-deliverable item restrictions, materials, fees and stock rules still apply. The 12 desynthesis recipes remain player-operated, and the four non-deliverable Enfeebling Kits cannot be ordered through delivery-based Guild services. Other expansion settings are unchanged.

Recruits now carry unlimited Poison Potions and can use one while fighting a nearby enemy whose spell list or known TP moves include Sleep. They prepare only while engaged, at 75% HP or more and above 60 HP, with no Poison already active; recovery items keep their priority. The normal potion applies 1 HP of poison damage every three seconds for 180 seconds, which can wake the Recruit from ordinary Sleep. Recruit cleansing previously treated every Poison effect as an ailment. Antidotes, Remedy and Poisona now check the effect's source and preserve deliberate self-poison, while poison applied by an enemy remains curable, including an enemy effect that replaces the potion's poison. Players can still remove it manually with Poisona. The Recruit AI switch continues to stop automatic medicine use, and normal item activation and Medicated rules are unchanged.

Battlefield entry items no longer need to be thrown away after their final use. Successful entry now removes the exact exhausted testimony or cracked BCNM/KSNM orb that opened the fight, using its recorded wear state. Titan's existing single-use testimony rule is unchanged. Cancelled menus, rejected entries and items with uses remaining are kept, and joining another player's battlefield does not consume your own item. This applies at entry, so losing the battle does not restore the spent item. Old worn items already in inventories are not swept or deleted automatically.

Venture Moogles offer three expedition choices in /titan. Standard keeps its original 30-minute duration, 50-Sparks price and 100 EXP at every Venture Moogle level. Extended takes two hours for 200 Sparks and 500 EXP; Grand Expedition takes four hours for 400 Sparks and 1,100 EXP. Every trip returns exactly one full stack from the same weighted discovery pool, using the Venture Moogle level recorded at dispatch before its EXP is awarded. Longer trips grant bonus training EXP with overflow through multiple levels, but add no item rolls, rarity bonus or guaranteed higher-level material. Frequent Standard trips collect more stacks over the same time. All 13 specialties remain available, including Synergy with shared crafting materials; Synergy crafting stays disabled. The menu shows the full price and expected EXP before dispatch, and Recent Ventures records the expedition type, duration, price, actual EXP and delivery result.

Assignments keep their original due time while you are offline or the server is in maintenance. Rewards come from a reviewed list of stackable supplies, and the destination is always the character who sent the Venture Moogle. A full delivery box keeps the reward pending for automatic retry. Personalized notices use Titan's existing Emotes route to Window 2, and the return message names the item and quantity only after delivery has committed. Notification acknowledgments prevent ordinary reconnects, zoning and retries from repeating the same notice. Character profiles now show all 13 specialty Moogle levels and EXP in a collapsible Venture Moogles section below Fieldcraft, with a matching explanation on the About page. Automated engine, database, protocol and responsive layout tests cover this release; broader player economy effects and in-game usability still need observation.

Colossus spawn messages now explicitly include their custom model, and their disappearance messages retain the correct despawn flags and animation. The renamed-monster packet path was adding ordinary update flags to those disappearance messages, while a late movement update could alter a queued despawn. These malformed lifecycle packets were found while investigating reports of invisible monsters and client crashes after Colossus kills. Native regressions cover all 82 configured Colossus models and the next ordinary-crab spawn. Client confirmation of the reported crash is still needed after activation. Rewards, HP scaling and respawn timers are unchanged.

Dancer Recruits are available again on Dynamis through the manual !dnc command, the existing job recruitment controls and the balanced !recruit pool. They can also appear among the randomly selected world-anchor Recruits. Dancer remains disabled on live Titan. Non-GM manual summons retain the normal 30-minute Dancer cooldown, party-leader requirement and party-capacity checks; GMs remain exempt from the cooldown. World-anchor recruitment keeps its separate rules and does not use or clear the manual job timer.

This is a Dynamis-only test reopening, not a claim that the historical Dancer client-crash reports have been resolved. The existing native engine and Dancer combat behavior are unchanged. Local native regressions cover recruitment, level caps, timers, anchor selection and construction, and Dancer action-packet behavior. Client visual stability and sustained gameplay with Dancer still need player testing. Existing anchors continue to roll their normal jobs; reopening Dancer does not force every anchor to offer it.

Dynamis TEST replies could turn a negative diagnostic distance such as -100 into 4294967196 because their integer formatting used an unsigned 32-bit conversion. The protocol now formats its own scalar values without changing the game-wide formatter. Exact numeric integers through 9007199254740991 and existing decimal strings are preserved. Unsafe numeric values are rejected instead of being returned as valid diagnostic data.

The existing limit of 20 TEST requests per owner per second remains. Authenticated requests above that limit can receive one short retry notice per second; rejected actions are not automatically replayed. Command tracing now excludes session keys and command payloads and adds bounded diagnostic processing-stage correlation. The reported request-79 timeout has not been reproduced or assigned a confirmed cause. This stage changes Dynamis only and preserves its native engine and private addon. The broader diagnostics platform and its 52 formal acceptance cases remain unfinished.