Titan Development Log

The World Time page now stacks its clock, event countdowns, schedules, and status cards cleanly on phones. Text and ferry details stay readable without sideways scrolling, while the desktop layout remains the same.

The Recruit feature banner now shows generated adventurers from Titan instead of the older story Trust screenshot. The page layout and artwork around it are unchanged.

Clicking the Sparks button now gives you a system chat receipt with the Sparks spent, gil earned, and your gil balance before and after the exchange. The amounts come from the server after the conversion succeeds.

The 10 gil per Spark rate and balance checks are unchanged.

The five companion buttons once again cycle only through Tank, Support, and DPS. Each pool still draws a random eligible Recruit job, so you can shape your party without selecting a specific job.

Old job-specific slot choices return to their original pool defaults. The server also rejects job-specific slot commands; player Gambits and Recruit combat behavior are unchanged.

Generated Recruits now have a wider range of short, original replies shaped by their appearance and individual personality. Humes, Elvaan, Tarutaru, Mithra, and Galka can sound distinct while giving the same truthful answer about a spell request, greeting, or thanks.

The server still decides whether a spell is ready, queued, on recast, short on MP, or already active before anyone replies.

Recruits now give varied, short replies that fit what is happening: they can greet you, respond to thanks and jokes, explain when a spell is queued or waiting, and tell you when the target is already covered or needs no cure. Each Recruit has a consistent way of speaking, and repeated TAB messages no longer flood party chat.

Their server-owned spell checks and casting queue still make the decisions. Recruits speak when a requested cast starts or finishes, and explain when a queued request becomes invalid.

Recruits now answer TAB requests in their own words. They greet players with varied replies and explain when a spell is queued, waiting for MP or recast, or already active on its target. They also say when they cannot find a named player or cast a requested spell.

The existing server spell checks and casting queue remain in charge.

Recruits could answer “Understood” to a Sneak request but never cast it. The queued request was looking up a player by the wrong kind of ID, so it vanished before the spell began. Recruit spell requests now keep the correct player target through casting.

The server still checks spell range, MP and valid targets.