Design Notes on FFXIV Loop

FFXIV Loop started from a practical observation: rotation practice is mostly about feedback timing, not just memorizing a list of skills.

In Final Fantasy XIV, a good loop is built from rhythm, conditions, cooldowns, buffs, resources, and mistakes that are easy to feel but harder to isolate. A practice tool should make those invisible rules visible without trying to become the game itself.

1. Practice the Decision Surface

The goal is not to simulate every part of combat. That would be too large and not very useful for the first version.

The useful surface is narrower:

• which skill can be pressed now
• which combo action should come next
• which cooldown is blocking an action
• which buff, debuff, DOT, or proc is active
• whether the hotbar layout supports the player’s muscle memory

That is enough to practice a rotation loop. The tool should focus on the decision the player makes every global cooldown.

2. Make the Hotbar Real Enough

Hotbar layout matters because rotation practice is physical. A tool that only lists actions in order misses the point.

Dragging skills onto bars, assigning keys, and pressing them in rhythm gives the practice session a closer shape to actual play. It does not need to reproduce the full client UI, but it should preserve the parts that affect memory:

• position
• key binding
• cooldown state
• disabled state
• combo highlight

The hotbar is not decoration. It is the main input device.

3. Keep Skill Rules in Data

Skill behavior changes. Jobs get patched. Potencies, cooldowns, combo chains, and conditions move around over time.

For that reason, the design should keep skill data in configuration instead of burying every rule in application code. JSON is not glamorous, but it makes the project easier to adjust. A job can become a data file instead of a hard-coded feature.

This also keeps the practice engine simpler. The engine reads rules, updates state, and tells the UI what is available. It should not need to know the personality of every job in advance.

4. Feedback Should Be Immediate and Quiet

The tool should show mistakes clearly, but it should not shout.

If a skill is unavailable, the player needs to know why. If a combo is ready, the next action should be obvious. If a buff is active, its duration should be visible. These are small feedback loops, and they work best when they stay close to the hotbar.

I do not want the interface to become a dashboard of warnings. Rotation practice already has enough information. The UI should reduce uncertainty, not add noise.

5. Avoid Building a Full Combat Simulator Too Early

A full simulator would need encounter timelines, enemy behavior, party buffs, animation locks, latency assumptions, and damage calculation. That is interesting, but it is a different project.

FFXIV Loop should first answer a smaller question:

can I rehearse the shape of this loop and notice when I break it?

If the answer is yes, then deeper simulation can be added later from a stable foundation.

Current Rule

For FFXIV Loop, the design rule is:

practice the next correct press

The project is useful when it makes the rotation loop concrete enough to rehearse without pretending to replace the game.