New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Production site ware request fullfilled before equipping worker request #3427
Comments
(by franku) But i am not against prioritizing building a worker. |
(by tino79) I encountered this problem on playing the second barbarian campaign mission: |
(by franku) I played the scenario yesterday but had no problems getting trainers, but i built the barracks very late, so the Ax Workshop started making axes before they are demanded by the barracks. Instead of prioritizing workers we may should check for trainers in this campaign and give the player a hint? Or change the campaign to build the training camps and barracks after the Ax workshop has been built? |
(by tino79) I'll update the Bugs title and try to explain better: If a building (i think the baracks is currently the only one) stocks/requests the same ware as it is needed to produce a worker (in this case: trainer) for it, the engine fullfills the stock request before it fullfills the worker request (when no building worker is already stocked). The worst case scenario would be: No trainer available, but 8 axes (and no ressources to produce more axes) Result: No soldier at all, 8 axes stocked in baracks. Excpected result: 1 Trainer and 7 Soldiers. So in my expectation the engine should always prefer equipping workers before sending wares to production sites (where the user can set the priorization). |
(by franku) The only concern i have is: It will make the game less focused on economy. I believe managing an economy is a big part of the game and doing some managing automatically by the engine would make it easier for players to focus on other things, e.g. creating fast a big army. Just my personal opinion :-) |
(by tino79) But i am not suggesting adding automation but to fix a existing,faulty engine decision ;). The best solution of course would be to implement a UI for this (like the small UI buttons the player can use to priorize ware distribution between production site requesting the same ware), but this would be complicated... Managing the economy: yes: Managing to circumvent engine bugs: No. "Bug" here: Very weird decision to stock a ware instead where it is stocked in a building instead of creating specialized worker which makes the item usable in the first place. This is definitely different from the aspect to let the user figure out how to produce most optimized soldiers by configuring arena/training in a short(er) time. Ok, enough from me, let's wait for some more opinions. |
(by gunchleoc)
|
Consider the following situation for babarians:
Then build a barracks.
Expected outcome:
Current outcome:
In my opinion the ware request to "build a worker" should always prioritized to a ware request from a building.
Imported from Launchpad using lp2gh.
The text was updated successfully, but these errors were encountered: