get_civics recentDemographics contains large blocks of duplicated events #224

New issue

Closed

opened 2026-08-12 23:14:00 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-08-12 23:14:00 +00:00

Member

QA sweep, Eco via Sirens, day 40, 2026-08-12.

Observed

get_civics.recentDemographics repeats whole runs of identical records. The day-19 joined block (roughly 35 citizens) appears three times verbatim in a single response, and the day-15 block appears twice. Smaller duplicates are scattered throughout — e.g. Sal day 27 joined ×2, PVC Pipe Connecter day 26 joined ×2, Jovi day 17 joined ×4 / left ×4.

Why it matters

The counts derived from this stream look wrong as a result:

citizensGained: 371, netCitizens: 346
but get_server_status reports players.total: 165 — the server has never seen 371 distinct players.

perActionCounts.BecomeCitizen: 371 matches, so the duplication is upstream of the counters, in the event ingest.

Expected

Either de-duplicate on ingest, or state clearly that these are raw repeated events and that citizensGained counts events rather than people. As it stands the demographic headline is roughly 2× reality.

Note

May share a cause with the subject/settlement blanking in the sibling issue — worth checking whether the same rows are being re-emitted per settlement with an unresolved settlement key.

QA sweep, Eco via Sirens, day 40, 2026-08-12. ## Observed `get_civics.recentDemographics` repeats whole runs of identical records. The day-19 `joined` block (roughly 35 citizens) appears **three times verbatim** in a single response, and the day-15 block appears twice. Smaller duplicates are scattered throughout — e.g. `Sal` day 27 joined ×2, `PVC Pipe Connecter` day 26 joined ×2, `Jovi` day 17 joined ×4 / left ×4. ## Why it matters The counts derived from this stream look wrong as a result: - `citizensGained: 371`, `netCitizens: 346` - but `get_server_status` reports `players.total: 165` — the server has never seen 371 distinct players. `perActionCounts.BecomeCitizen: 371` matches, so the duplication is upstream of the counters, in the event ingest. ## Expected Either de-duplicate on ingest, or state clearly that these are raw repeated events and that `citizensGained` counts events rather than people. As it stands the demographic headline is roughly 2× reality. ## Note May share a cause with the `subject`/`settlement` blanking in the sibling issue — worth checking whether the same rows are being re-emitted per settlement with an unresolved settlement key.

coilyco-ops referenced this issue

2026-08-12 23:34:54 +00:00

Tracking: 2026-08-12 full-surface QA sweep of the eco MCP (22 tools, 23 findings) #240

coilyco-ops referenced this issue

2026-08-12 23:36:09 +00:00

Tracking: 2026-08-12 full-surface QA sweep of the eco MCP (22 tools, 23 findings) #240

coilyco-ops referenced this issue

2026-08-12 23:47:23 +00:00

Tracking: 2026-08-12 full-surface QA sweep of the eco MCP (22 tools, 23 findings) #240

coilyco-ops referenced this issue from a commit

2026-08-13 06:00:12 +00:00

fix(civics): separate demographic events from the people behind them