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
(RFC): List of problems for ConstructionAutomation #11264
Comments
Also pinging @tuvus in case he wants to look over some of these. Also, Uh, do you want me to ping you like this on issues/PRs or do you want to just look over them as you go? |
No problem, you can ping me if you want. I probably won't see it if you don't ping me since I don't do regular checks on the issues or PRs unless they show on discord.
I definitely agree with this, the AI is somewhat incompetent with gold income. It seems to me that the best fix was just to make the AI cheat. There also aren't many gold production buildings early on in G&K anyway.
I looked at this again and am startled to find that this is true. This might need to be fixed by evaluating them in two different places, once without the stat and once with.
Good point, why are we splitting up multiple add-building choices just to use the same evaluation algorithm for a different stat? The current method is certainly not very mod-friendly. We will probably have more uniques in the future that need to be added, so keep in mind that this probably won't be a static list. About buying buildings with gold. We probably need to rewrite that as well to use the production system. Currently, the AI only buys the building/unit in production. If I understand this correctly, if the AI half builds a building and buys it, it costs the same amount. Meaning the AI should not want to buy the current building/unit in production unless it just started if this is true. |
This is actually one of the more minor issues in the grand scheme of things. There are actually two situations that can make this much worse
|
Before creating
Problem Description
Right now I want to try to focus in on cleaning up ConstrcutionAutomation, or at least get the issues with the it documented to work on for later. Right now there's a few issues with the class
isStatRelated
. This accidentally includes percentage increases, which generally are differentIf there's other issues, please point them out. Hopefully we can get the issues crossed off as we go
Related Issue Links
No response
Desired Solution
Fixes to the above
Alternative Approaches
Yes
Additional Context
No response
The text was updated successfully, but these errors were encountered: