gcctbilly
commented
9 months ago I think not providing the number of tasks upfront is a reflection of what happens in real-world development. In reality, we don’t know how many emergent tasks will need to be completed in the future.
I think a better solution would be to provide a function to stop the assigned current job (Also return some part of the budget). So that when a new task coming, users can stop currently assigned tasks and move on to more important tasks.
The number of tasks within a project is not specified upfront, which can result in players misallocating their budget for upgrading the environment. Without an understanding of the expected workload, players may face resource shortages, delays, or reduced efficiency.
In my experience, I thought there were more tasks ongoing even though all the tasks were done, which caused me to allocate more budget to upgrading the environment.
Proposed Solution: Introduce task quantity information at the start of each project to provide players with an estimate or a range of expected tasks. This enhancement will allow players to make strategic decisions regarding resource allocation, budget planning, and upgrade prioritization.