Hotbar 1 uses the 12 MMO mouse buttons. Hotbar 2 uses those 12 buttons with Shift as the modifier. Hotbar 3 uses those 12 buttons with Alt as the modifier.

Designed with minimal swapping between 1 and 2. Most GCD on the non-D pad to help with attacking and moving. Hotbar 8 L and R are same so no thinking. Hotbar 1 is Single target while Hotbar 2 is AOE minded. Hotbar 2 has mount + sprint so keep in mind. Dye = Pot for raiders, if not than whatever you want. Enabled customization when weapon is drawn/sheathed Hotbar 1 + 2. That means hotbar 3 you will manually have to switch to if you need stuff on there. part of my Tank series where similar skills are in the same spots and play roughly in same style. Please Enjoy!

WAR Layout 6.55 (Not 7.0-Able)
LT>RT remapped from Set 8 Left to Set 8 Right, only right half of Set 8 is used
Set 1 - Primary Skills / DPS CDs / Defensive CDs ; Set 2 - Utility + Situational CDs ; Set 8 - AoE / DPS CDs / Defensives

Hotbars for Lv60 Dark Knight.

I've watched Bun Boss and a few others to get an idea of how things should flow on controller. This is a setup that works for me and I wanted to share it! I like to keep things consistent across my jobs.

MMO mouse setup with modifiers.

Current WIP for updated hotbars in 7.0, focusing on minimising swapping hotbars in combat and keeping visual clarity on relevant buff cooldowns and maximising consistency across all jobs. Bar 1 is for single target, and Bar 2 for AoE.

The Glamour Plate button is being used in place of the newly added skill as needed, and the dye represents potion. Sprint and LB are macroed to L3/R3 respectively.

Single Target (L)

Mobs (R)

Like paladin but edgier

PROVISIONAL - NOT LEVELLED OR TESTED

Buttons consistent for similar job actions (Dye = Potion)

自分用。

1️⃣RTはコンボと自分バフ。LTはアビと複数バフ。

Peripherals are Corsair Scimitar Elite

All jobs will follow a similar pattern to make job transitioning simple and not so overwhelming

How I set up my crossbars as a white mage on steamdeck (Currently level ~65)

I try to play every classes/jobs, thus I tend to reuse same slots for same "functionality" across jobs.