How to read member readiness without mistaking missing data for zero.

The Readiness Board combines the current faction roster with the newest valid Personal snapshot for each member. It should produce one row per roster member and explain why someone is ready, limited, blocked, stale, or missing data.

Open Readiness Board Start the guide Open Personal

ShadowCore readiness board showing member scores, bars, cooldowns, location, HQ use, roles and actions — **Readiness rows**The row should use the faction roster as identity and the Personal snapshot only as enrichment. Blank bars mean unavailable snapshot data—not zero energy.

What each column means

MemberName, Torn ID, data source, and Personal snapshot age.

Score / stateA compact readiness signal. Use the blocker details before making a final call.

BarsCurrent energy and nerve from the member's newest valid Personal snapshot.

DrugRemaining drug cooldown or clear state.

LocationHome, travel, abroad, hospital, or another current operational state.

HQ useRecent ShadowCore activity from the member's last HQ heartbeat.

RoleFaction or war role used for context.

Action / blockersThe first useful action and the reasons the member is not fully ready.

Step-by-step

Refresh the board

Refresh before a chain, war push, defense call, or emergency message. Check the source line to confirm the roster and Personal snapshot counts are sensible.

Start with state, then read the row

Ready and Standby are useful groups, but the score is not the entire decision. Confirm bars, location, cooldown, snapshot age, and listed blockers.

Treat blank bars correctly

—/— means ShadowCore does not have usable bar data for that member. It must not be interpreted as 0/0. Ask the member to open Personal and refresh their snapshot.

Check snapshot age

Old Personal data can make bars, cooldowns, or travel state misleading. A stale label means the member should refresh before leadership relies on the row.

Use the action column

The action should tell you whether to call the member, refresh Personal data, wait for a cooldown, return home, or resolve another blocker.

How the states should be interpreted

Ready: no critical blocker is present and the available signals are strong.
Standby: usable, but not the first call.
Limited: one or more conditions reduce immediate usefulness.
API missing: the member is on the faction roster but has no usable Personal snapshot.
Stale: a snapshot exists, but its age is beyond the configured freshness window.

Common problems

Duplicate member rows

Rows should be keyed by Torn ID from the authoritative faction roster. Browser labels or unmatched snapshot names should never become extra faction members.

Old travel state

The newest operational snapshot should control travel and status. Older destinations must not be merged into newer bars.

API missing for an active member

The member can still appear from the roster. Ask them to open Personal and refresh so bars and cooldowns can enrich the row.

Score looks wrong

Read the component signals and blocker list first. A full bar does not cancel travel, medical, cooldown, stale-data, or assignment issues.