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

If the unit uses BuildLimitGroup, the construction progress will be reset when placing the production building #1414

Open
5 tasks done
WhiteFeather127 opened this issue Nov 2, 2024 · 1 comment
Labels
Phobos bug Something isn't working properly

Comments

@WhiteFeather127
Copy link

WhiteFeather127 commented Nov 2, 2024

Description

If the unit uses BuildLimitGroup, the construction progress will be reset when placing the production building

Phobos Version

https://github.com/Phobos-developers/Phobos/releases/tag/build-44

Conditions to reproduce

No response

INI code

[HTK]
BuildLimitGroup.Types=HTK
BuildLimitGroup.Nums=1
BuildLimitGroup.Factor=1
BuildLimitGroup.ContentIfAnyMatch=true

Steps to reproduce

Build a FlakTrackGun and place a factory when it hasn't been built yet.

Expected behaviour

The FlakTrackGun should be built.

Actual behaviour

The construction process of FlakTrackGun has been reset to zero and is in a holding state.

Additional context

No response

Checklist

  • The issue happens on the latest official version of Phobos and wasn't fixed yet.
  • I agree to elaborate the details if requested and provide thorough testing if the bugfix is implemented.
  • I added a very descriptive title to this issue.
  • I used the GitHub search and read the issue list to find a similar issue and didn't find it.
  • I have attached as much information as possible (screenshots, gifs, videos, debug and exception logs, etc).
@WhiteFeather127 WhiteFeather127 added the Phobos bug Something isn't working properly label Nov 2, 2024
@Starkku
Copy link
Contributor

Starkku commented Nov 3, 2024

It is possible to work around this issue by simply not listing the type itself in BuildLimitGroup.Types and using BuildLimit in conjunction for controlling the max limit for a single unit. This may be addressed in future on Phobos's side but it is a conflict with how the existence checking and factory queues work which is somewhat complicated to fully fix AFAIK.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Phobos bug Something isn't working properly
Projects
None yet
Development

No branches or pull requests

2 participants