Titan Development Log

Player Auto-Abilities was loading only the main-job profile, which meant an MNK/WAR could ignore Berserk and Warcry despite having learned them. Dynamis now loads eligible subjob ability rules using the actual subjob level. Defender remains a defensive choice at low HP while holding hate, rather than repeatedly replacing Berserk just because it is ready.

Player ability registration now checks the native job and level catalog through level 75 instead of using older doubled-level Recruit assumptions. Learned abilities, merits, equipment, resources and recasts still apply, and the Auto-Abilities and master switches continue to control execution. Player special abilities remain manual. Preparatory abilities that need a planned follow-up, pet acquisition, Charm, retreat and travel utilities are not triggered blindly by importing another main-job profile.

The update passed 156 gameplay regression scenarios against the Titan engine and 179 against the separate Dynamis engine, plus a registration audit of 3,388 main/subjob and level combinations. Dynamis loaded the Lua changes without restarting game services. Live Titan is unchanged; these changes have joined the staged Titan master patch for later activation. Player testing of additional job combinations is still welcome.

Invited Dynamis testers can now try the separate Recruit test addon and its selected Summoner and Scholar support routines. Those two prototype coordinators activate only after custom test preferences are explicitly applied; switching those preferences off returns to their released coordinators. Current Auto action switches, job-based support memory, medicine pacing and Corsair’s eighteen-roll catalog, including its EXP roll, remain available.

Other test policies apply across Dynamis, including revised support selection, spell-range checks and automatic Blue Magic exclusions with a separate manual request path. The server validates ownership and targets for manual requests. Diagnostics start off and require an explicit opt-in; the recorder keeps numeric gameplay events in a bounded rotating log. The private addon must be connected deliberately and should be used instead of the regular TitanGambits controller during these tests.

The feature-enabled and feature-disabled builds passed their native checks, including 169 Lua/native scenarios for the enabled build. In-game acceptance is still pending; the supplied manual checklist is not a record of completed tests. Titan’s live gameplay and public launcher addon were not changed. Six independently validated shared spell fixes are staged in the new Titan master patch for later activation.

The main launcher button now shows Checking while required files are checked and Updating while a detected launcher, client or addon update is being prepared. If a required update remains unfinished, the button says Update Launcher or Update instead of continuing to say Play Titan. It returns to Play Titan after the required checks and updates finish successfully.

Clicking a pending Update action completes the update step without immediately starting the game. Automatic update checks continue as before, and the game remains blocked while required files are being installed or verified. The final launcher and installer are Microsoft Artifact Signed.

Character sheets now keep Equipment directly below Overview, followed by Jobs, Missions, Artifact Armor, Relic Armor, Assault, Dynamis Victories, Avatar Unlocks, Achievements, Accolades, Titles, Professions, Fieldcraft and Bazaar. Overview remains open, while the other 14 sections start collapsed and can be expanded individually.

Each section heading now includes a compact summary from that character’s saved data, such as filled equipment slots, unlocked jobs, active nation rank, owned armor pieces or completed achievements. Armor and Bazaar totals follow their collection updates, and the headings wrap on smaller screens while keeping the existing dark styling and gold accents. Armor totals cover the jobs shown in those collections; missing data is marked unavailable rather than shown as zero.

TitanGambits 2.4.16 gives your character and each owned Recruit separate Auto-WS, Auto-RA, Auto-Abilities and Auto-Spells buttons. Green means enabled and red means disabled. The server enforces each choice, and the interface changes color after the server confirms it. Turning an individual Gambits row OFF disables all four categories; turning it ON enables all four, after which you can switch categories independently.

Your own automation starts OFF with all four categories OFF on this first rollout, including characters opted into the previous version. Later choices are saved per character and main job through logout. Every newly summoned Recruit starts with its Gambits and all four categories ON; its action switches last only for that summoned Recruit. Recruit melee positioning and the two Support priorities keep their separate job preferences. The master switch remains a pause for the whole owned party and does not erase individual choices.

Player actions use the normal job AI while retaining native access and costs: weapon skills require an available equipped-weapon skill and TP, ranged attacks need a compatible equipped weapon and ammunition and consume real arrows or bullets, and spells require learned magic and normal MP and item costs. Player two-hours remain manual. Recruit ammunition and virtual supplies are unchanged. Individual Recruit OFF now pauses its automatic AI and queued requests instead of falling back to ordinary Recruit AI; following continues and actions already underway may finish.

Treasures of Aht Urhgan now gives short next-step notices through Titan’s Emotes channel, shown in Window 2 with the usual chat filters. After an interaction changes your objective, the notice names the NPC, item, location or battle needed next. All 48 mission entries were reviewed against BG Wiki and Titan’s scripts: 47 playable missions, followed by the Eternal Mercenary story marker. The automatically assigned opening mission stays quiet until you have a Boarding Permit.

The directions follow actual mission status, key items, zone requirements and waiting periods. They distinguish Cacaroon’s accepted payments, Pyopyoroon’s acid trade, Jazaraat’s headstone steps, palace dress requirements and replacement battle-entry items. Consumed entry items do not send you out of an active instance, and victory states point to the remaining exit scenes. Titan’s optional Rytaal tutorial is not presented as a required mission step; reward guidance follows Titan’s actual ring, Imperial Standard and Glory Crown handoffs. This adds directions without changing mission requirements, rewards, waits or combat.

Each complete notice, including its ToAU label, stays within 120 plain-text bytes; the longest checked message is 113 bytes. Unknown or oversized directions remain silent instead of being guessed or cut off. The shared observer waits for conversations to close, rechecks stale objectives and suppresses immediate repeats. Physical line wrapping still depends on your chat font and window width.

Checks cover 12,611 objective snapshots, all 48 mission script loads and a real progression callback from each of the 47 playable missions, including item recovery and waiting boundaries. All 120 native regression tests passed, including ten ToAU tests covering real NPC handoffs, reward and timer preservation, Emote packets and terminal-state handling, alongside the nation, Zilart, CoP and companion checks. Dynamis accepted the Lua extension without a game-service restart. This does not replace a full player walkthrough of every battle and scene; report a missing or incorrect notice with your mission number and last interaction.

Chains of Promathia now gives short next-step directions through Titan’s Emotes channel, shown in Window 2 with the usual chat filters. After an interaction changes your objective, the message names the NPC, object, area or battle to visit next. All 33 playable missions from The Rites of Life through Dawn are covered, along with The Last Verse story marker. The directions were checked against BG Wiki’s 34 main mission entries and three Three Paths guides, then reconciled with Titan’s actual mission flags.

The Road Forks keeps its San d’Oria and Windurst routes separate, and Three Paths tracks Louverance, Tenzen and Ulmia independently. Promyvion lights, Vahzl Memory Fluxes, Warder kills, conversations and later multi-area objectives track what is still needed, including objectives completed in different orders. Dawn follows the midnight wait, its five independent epilogues and final scenes; defeating Promathia alone does not produce a false story-completion notice. Mimeo Jewel replacement and full-inventory reward recovery also have directions. Existing mission requirements, rewards, waiting periods and battles stay unchanged.

Every complete notice, including the CoP label, stays within 120 plain-text bytes. The longest checked CoP message is 118 bytes. The observer rejects oversized or unknown directions instead of cutting text off or guessing, waits for conversations to close, rechecks stale objectives and suppresses immediate repeats. Your chat font and window width still determine where a message wraps.

Validation checks 10,764 objective snapshots, all 33 mission script loads and one real progression callback per mission, branch combinations, key items, timers, invalid states and read-only behavior. All 110 native regression tests passed, including eight CoP tests covering real NPC handoffs, independent branches and outgoing Emote packets, alongside the existing nation, Zilart and companion checks. Dynamis accepted the Lua extension without a game-service restart. This is not a complete player walkthrough of every battle and branch; report a missing or incorrect notice with your mission number and last interaction.

Rise of the Zilart now gives short next-step notices through Titan’s Emotes channel, shown in Window 2 with the usual chat filters. After a mission interaction changes your next objective, a message such as "[Zilart 3] Talk to Jakoh Wahcondalo in Kazham (J-9)." tells you where to go. Directions follow Titan’s actual mission flags, with all 18 BG Wiki mission entries reviewed as references.

The guidance covers all 17 playable missions and The Last Verse, which is a final story marker rather than another battle. Headstone prayers and Ark Angel shards track what you still need, including out-of-order collection; the Chamber of Oracles follows each pedestal you have used. Papyrus and crystal handoffs, interrupted victory cutscenes, the postponed opening and Awakening’s two epilogues have their own directions. After the epilogues, the notice points toward the CoP and Ru’Lude Gardens follow-up chain instead of claiming Zilart is fully finished early. This does not add general quest notifications or change mission requirements, rewards or battle difficulty.

Every complete notice, including its mission label, stays within 120 plain-text bytes. The longest Zilart direction checked is 113 bytes; the observer rejects oversized text rather than cutting it off. Messages wait for conversations to close, suppress repeats and recheck stale directions. Line wrapping still depends on your chat font and window width. Unknown states stay silent instead of giving guessed instructions.

Checks cover 5,084 states and all 17 mission handoff callbacks, including all pedestal combinations and fragment and shard subsets. Thirteen native-engine tests verify Zilart handoffs and Emote packets alongside the existing nation guidance, including its text-length boundary tests. Dynamis accepted the Lua extension without a game-service restart. These tests are not a complete player walkthrough of every branch; report a missing or incorrect notice with your mission number and last interaction.