Affected area
Stats DB (stats.techhaven.org)
Describe the feature you'd like
The Rares DB was intended to do fancy stats with it's data.
Currently the Stats DB displays the total number of Rares for a server, updated hourly.
The Stats DB is also doing daily snapshots of the Rares DB data.
Here is the Claude AI summary of the 3 snapshot tables.
rare_stats_parts - a daily snapshot of total parts held across all users, broken down by server_id and part_id. One row per part-type per server per day.
rare_stats_total_parts - a daily snapshot of aggregate part totals per server, with pre-computed time-window breakdowns (24h / 7d / 30d / 60d / 90d) and per-group subtotals (e.g. qty_l, qty_t, qty_e, qty_battleChurch). The groups come from rare_item.rare_stat_group in the rares DB.
rare_stats_users - a daily snapshot of distinct user counts per server, again with the same time-window breakdowns.
The stats tables are effectively historical time-series archives — the rares DB holds live current state, and thn.stats snapshots aggregates of it once per day.
I have no clue was BattleChurch columns was intended for.
Why is this needed?
Need to do something with this data.
Affected area
Stats DB (stats.techhaven.org)
Describe the feature you'd like
The Rares DB was intended to do fancy stats with it's data.
Currently the Stats DB displays the total number of Rares for a server, updated hourly.
The Stats DB is also doing daily snapshots of the Rares DB data.
Here is the Claude AI summary of the 3 snapshot tables.
I have no clue was BattleChurch columns was intended for.
Why is this needed?
Need to do something with this data.