resource counting confusion for the player

[WanderingHead]

FYI

There is a sort of confusing detail to the way resources are displayed in game. I think that this explains recent complaints about "missing" resources.

When you build things, resources move to where you are building them. They stay there and are not consumed until after you hit "Next Phase" and end the turn, at which time they are consumed.

EXCEPT for research. As soon as you click on a new research point (on a specific attribute, not the research beaker in a region), the resource disappears from the map. It returns to the map if you cancel the resource.

So the issue is now that if you start any new research points, then try to actually count resources on the map (or on at the Region Info Screen), you will observe a shortfall and get confused.

This just happened to me. I was confused, thought there was a bug, but worked through it and found that everything is correct, but the displays are confusing.

I can't see that improving this is going to happen. The difficulty is that the research, once dedicated to an attribute, isn't really associated with a region. So it has to grab the resource right away, it cannot wait until the end of turn. Just rest assured that resources are not disappearing, it isn't really a bug.

[MrQuiet]

Thanks for that info WH.
Do you still plan to add a 'totals' line to the the summery screen that lists Resources, factorys etc...?
 
-MrQ

[WanderingHead]

ORIGINAL: MrQuiet
Do you still plan to add a 'totals' line to the the summery screen that lists Resources, factorys etc...?

Already there!

All numbers on this screen reflect the resource count _after_ resources are removed for committed research.

The only thing holding up the release is getting a little testing. I'm trying out mod features like letting air move across narrows (for the Battle of Britain, but actually it just makes sense anyway), and it isn't until a game is played that I notice things like resources scooting across the Kattegat without any transports (fixed this last night).