ponderingdemocritus
commented
1 year ago @tenoxious
My thinking:
- let's build the raw dynamic query system (80% there)
- hardcode queries like the above into a select menu (which we can just keep adding to) - these just inject into the dynamic ones
List of economic data needed:
HIGH PRIORITY
Monthly data for:
[x] Total resources minted and total resources burned.
[x] Total resources burned building battalions.
[ ] Total resources burned building light battalions.
[ ] Total resources burned building heavy battalions.
[ ] Total battalions destroyed in combat (in resource value).
[ ] Total battalions destroyed in raiding Realms (attack and defence) (in resource value).
[ ] Total attacking battalions destroyed in raiding Realms (in resource value).
[ ] Total defensive battalions destroyed in raiding Realms (in resource value).
[ ] Total battalions destroyed by desertion (in resource value).
[x] Total resources burned constructing buildings.
[ ] Total resources burned constructing buildings/day cycle.
[ ] Total resources burned for each type of building.
[ ] Total resources burned for each type of building/day cycle.
[ ] Total food consumed by battalions.
[ ] Total food consumed by light battalions.
[ ] Total food consumed by heavy battalions.
[ ] Total storehouses built.
[ ] Total resources raided.
[ ] Average of resources raided for successful raids.
[ ] Average of resources raided for total raids.
[ ] Number of Relics stolen and retrieved.
Group data (still monthly):
[ ] All food consumption data needs a total amount, and then the amount for $FISH and $WHEAT.
[ ] All battalion data also needs to be individualised for each of the eight battalion types (Arcanist, Apprentice, Light Infantry, Heavy Infantry…)
[ ] Number of items built for all of the above, when applicable (i.e. how many battalions were built based on the resources burned.)
[ ] Averages for all of the above (i.e. number burned/number of settled Realms)
LOW PRIORITY (Systems designed but not implemented into alpha yet)