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

Lock constructionList Source #282

Open
FlavioCoutinhoGO opened this issue Oct 31, 2024 · 1 comment
Open

Lock constructionList Source #282

FlavioCoutinhoGO opened this issue Oct 31, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@FlavioCoutinhoGO
Copy link

Is your feature request related to a problem? Please describe.
When you run two constructionLists in a row, the second one can access the resources that will be used by the first one. You request construction with the constructionList, but the resources in the city are still available for other construction tasks. This may result in a lack of resources when ordering construction.

Describe the solution you'd like
I would like the resources used in the constructionList to not be available (visible, etc.) for other tasks, such as a new constructionList.

Describe alternatives you've considered
I see no alternatives other than blocking the resources that will be used by the constructionList task that was successfully saved.

Additional context
Nothing

@FlavioCoutinhoGO FlavioCoutinhoGO added enhancement New feature or request evaluation required Items is pending review or evaluation by the team labels Oct 31, 2024
@ikagod ikagod removed the evaluation required Items is pending review or evaluation by the team label Jan 12, 2025
@ikagod
Copy link
Collaborator

ikagod commented Jan 12, 2025

This is hard to accomplish with the current mode of execution in ikabot (multiprocessing). Once we switch to multithreaded exection, this will be possible. I will close this issue once the appropriate branch is merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants