Skip to content
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

Prevent unit requests from stacking during production. #15982

Merged
merged 1 commit into from Jan 4, 2019

Conversation

pchote
Copy link
Member

@pchote pchote commented Dec 31, 2018

Consumers of IBotRequestUnitProduction need to be able to check what is already in the queue so that they don't request N duplicates while the first one is still building.

Note that this is a speculative fix that I haven't yet tested ingame. @reaperrr did you have a simple way to test the behaviour of this module?

@reaperrr
Copy link
Contributor

reaperrr commented Jan 3, 2019

Note that this is a speculative fix that I haven't yet tested ingame. @reaperrr did you have a simple way to test the behaviour of this module?

On the mcv module, increasing the MinimumConstructionYardCount to something like 3 or higher.
On #15991, disable the free harvester on the tested mod's refinery.

Doesn't work so well actually, goes out of cash too quickly.
Adding an * 3 at the end of this line should work:
https://github.com/OpenRA/OpenRA/pull/15991/files#diff-6cc35cd8c4e6900b084a2e26aa56edf2R137

According to my test of #15991 before I rebased onto this, the issue this should prevent is probably real on bleed, I haven't tested this fix itself yet, though.

Copy link
Contributor

@reaperrr reaperrr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me and seems to work as intended

@pchote pchote deleted the botrequestunitproduction-queue-check branch January 26, 2019 12:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants