Bases already planned
A base counts after its first meaningful layout or fitting change.
Plan a base →Visible only to you after signing in with your ChatGPT account. Planning activity continues to be counted anonymously.
A base counts after its first meaningful layout or fitting change.
Plan a base →A fitted design counts once, with further changes kept in the same plan.
Design a ship →A fleet counts when its composition, formation or fitted ships are edited.
Assemble a fleet →Days use Europe/Berlin time. Repeated edits do not create new plan counts.
| Period | Bases | Ships | Fleets | Views |
|---|
| Tool | Page views |
|---|
A page view is a visible page load. Reloads and repeat visits can be from the same player.
These are counts of plans, not unique people. One player may plan several bases, ships or fleets. Merely opening a planner does not count as planning. A random plan receipt prevents repeated edits, reloads and re-imports of the same saved plan from inflating its total. Explicitly generated new base concepts, newly fitted ship designs and new fleet concepts can count separately.
Only daily totals, the tool category and one-way hashes of random plan receipts are stored. Names, IP addresses, coordinates, module selections and saved design content are not stored by this counter. It uses no tracking cookies or third-party analytics. Recognised bots and browsers requesting Do Not Track or Global Privacy Control are excluded, so counts can be lower than actual activity. Measured counts begin with activation.
Waiting for the first recorded activity.
Shared preview edits can count as planning while preserving a visitor's saved local design. Exported JSON preserves the plan receipt; public base share links open an independent copy.