Building comparison
head to head
Blue ArchivevsCitizen Sleeper
Neither is meaningfully harder - they pose close to the same test. The widest gap is execution, and it is a single point.
Blue Archive
Optimization · Systems & Chaos
Team-building math against gacha randomness with minimal manual play.
Citizen Sleeper
Optimization · Systems & Chaos
A tabletop-flavored RPG about an android surviving on a derelict station.
Blue Archive leans Optimization (Systems & Chaos); Citizen Sleeper leans Optimization (Systems & Chaos).
Blue ArchiveCitizen Sleeper
Axis by axis
Execution1 vs 0
Blue Archive leans a little harder on execution, though the gap is small.
Blue Archive
Timing EX skills is the only manual input
Citizen Sleeper
Dice placement, no manual skill.
Reads1 vs 1
Same score on reads - which means the number cannot separate them. The difference is in what each one asks of you.
Blue Archive
PvP defence teams are static setups, not live minds
Citizen Sleeper
NPCs follow branching scripts.
Variance6 vs 6
Same score on variance - which means the number cannot separate them. The difference is in what each one asks of you.
Blue Archive
Gacha pulls and skill-cost rolls shape every roster and run
Citizen Sleeper
Daily dice rolls drive outcomes.
Optimization7 vs 7
Same score on optimization - which means the number cannot separate them. The difference is in what each one asks of you.
Blue Archive
Team composition, terrain affinity and raid strategy are deeply solvable
Citizen Sleeper
Action allocation and clock management dominate.
A matching score does not mean a matching test. Two games can both sit at 10 on execution and demand completely different things of you - which is why the reasoning above matters more than the number beside it.