Titan Development Log

Boss-pop hints in San d'Oria, Bastok, Windurst, Jeuno, Beaucedine and Xarcabard now use Titan's native Emote channel, following the approved Window 2 log routing. Each hint names the required Bijou and the boss it summons. Examining these pop targets gives guidance rather than invoking the victory-reward handler; existing trade checks are preserved.

After a verified Goblin Golem kill, Jeuno could fail to offer the Hydra Corps Tactical Map because its configured victory ??? was absent from the current NPC catalog. A real victory target now appears at the boss's death location and awards the normal key item and title when examined. New-run initialization hides and invalidates the old victory target, so an earlier kill cannot grant a new run's rewards. The missing target for the reported earned kill was restored without requiring another fight.

Jeuno's existing loot data listed Roving Bijou on two named monsters but omitted ordinary Vanguard mobs. Normal Jeuno Vanguard kills now have a 15% chance to add one Roving Bijou to the treasure pool. The roll runs once per qualifying kill; pets, bosses and named monsters retain their existing loot behavior.

No game-server restart is required.

The boss ??? in Dynamis Jeuno could remain hidden after a previous run because cleanup hid the zone's NPCs and the run-start code did not restore this target. New runs now restore the Goblin Golem pop target. The hidden target in the reported active run has also been restored without restarting the server.

Examining the boss ??? now explains that one Roving Bijou summons Goblin Golem. It no longer calls the era victory handler when examined; the existing trade and spawn checks remain in place.

The boss ??? in Dynamis Windurst did not explain how to summon Tzee Xicu Idol because its trigger was routed through the era victory handler, which returned without showing a pop hint. It now tells players to trade one Divine Bijou. The existing trade and spawning checks are unchanged, and the separate victory target still handles earned clear rewards.

The hint was checked against the active pop table and item data.

A repeat Dynamis San d’Oria entry still froze with TitanHub 2.4.159. The same player then entered successfully with red Collision ON selected, which leaves normal character blocking enabled and turns TitanHub's walk-through changes off. The earlier safeguard did not resolve this report.

TitanHub 2.4.160 restores its owned collision flags as soon as an NPC is targeted or an interaction begins. Collision updates now remain paused through the event transaction, including string-based events, and wait for two continuous seconds of normal control after completion before resuming. Event-update acknowledgements cannot end that pause. The local player is also excluded by entity index even if its spawn flags change during a scene.

Bounded diagnostics now record collision pauses and actual flag-write counts. This change does not establish a fix for the separate Cid, ferry, Promyvion or blue mage reports.

Routine PacketFlow and TrueFPS load announcements issued by TitanHub are now hidden using the actual Ashita message format. Plugin failures and warnings remain visible. Saved FPS, PacketFlow, cutscene and collision choices are preserved. Update through the launcher and reload TitanHub outside dialogue; no game-server restart is required.

Dynamis San d'Oria entry repeatedly stalled with TitanHub loaded. The same character entered successfully after TitanHub was unloaded, and a separate replay succeeded with TitanHub's walk-through collision feature disabled. Collision handling was isolated as the trigger; changing FPS and disabling enternity had not prevented the reported stall.

The collision updater had no NPC-event safeguard and could reapply its render-flag changes while the client was running a cutscene. TitanHub now restores only the flags it owns before an NPC interaction and when an event begins, pauses collision updates throughout menus, cutscenes and zoning, and resumes them after normal control returns. Saved collision preferences are preserved.

The four FPS choices, PacketFlow controls and Normal/Instant dialogue controls are back at the user’s request. Saved selections are preserved, and 30/60 Hybrid is used only when no FPS preference exists. Instant advances dialogue through Enternity; it does not skip every cutscene or animation. PacketFlow retains its previous guarded behavior during cutscenes and zoning.

TitanHub 2.4.159 is available through the launcher. Update through the launcher and reload TitanHub to use it. No game-server restart is required.

The Connection section, PacketFlow buttons and Normal/Instant cutscene buttons have been removed from TitanHub. It no longer loads, unloads or automatically switches PacketFlow or enternity during startup, zoning or cutscenes. Previous saved choices no longer control those plugins. The diagnostics checkbox is now in its own section.

Players can choose enternity independently through the launcher or use /addon load enternity and /addon unload enternity. Plugins already loaded in the current game session remain loaded; use /unload PacketFlow to disable PacketFlow immediately. The cause of the reported entry and cutscene hangs remains unconfirmed.

TitanHub 2.4.157 is available through the launcher. Update and run /addon reload TitanHub; no game-server restart is needed.

TitanHub 2.4.156 no longer controls game FPS. The Frame Rate label and all four choices—Static FPS 30, Static FPS 60, 30/60 Hybrid and TrueFPS—have been removed, and the settings section is now named Graphics. TitanHub no longer switches FPS caps during cutscenes, sends FPS commands, or loads and configures TrueFPS. Older saved FPS preferences are ignored. Players can manage FPS independently through their own plugins and settings.

This removes automatic FPS switching while we investigate reports of black screens, stalled cutscenes and battlefield progression problems. We have not established that Hybrid caused every report. Update through the launcher and fully restart the game to stop the previous controller and clear any commands it already queued. Passive FPS measurements remain available in automatic diagnostics.

With PacketFlow ON, TitanHub now pauses it during cutscenes and zoning, then restores it after one second of normal gameplay. Choosing PacketFlow OFF keeps it off. These automatic transitions do not change your saved preference.

Successful PacketFlow and TrueFPS plugin load/unload confirmations are hidden when TitanHub changes their state. Errors and restoration warnings remain visible. This changes PacketFlow handling while the cause of the reported cutscene hangs remains unconfirmed.

TitanHub 2.4.155 is available through the launcher. Update and run /addon reload TitanHub; no game-server restart is needed.