Skip to content

Implement production overflow #4081

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

Merged
merged 1 commit into from
Jun 8, 2021
Merged

Conversation

Thyrum
Copy link
Contributor

@Thyrum Thyrum commented Jun 8, 2021

As discussed on #4058, production (or hammer) overflow in Civ 5 is a thing and goes according to rules described on https://forums.civfanatics.com/threads/hammer-overflow.419352/ . This has been added to the game.

Currently there are no visual indicators that there is an overflow present. I don't know if and where these should be added. I think (but don't know) Civ 5 doesn't communicate this in any way either so maybe it is good as is. Suggestions are welcome.

I also don't know how an older version would react to a new game with the field productionOverflow. In general, how do older versions react to units/data fields they don't think should exist?

As discussed on yairm210#4058, production (or hammer) overflow in Civ 5
is a thing and goes according to rules described on
https://forums.civfanatics.com/threads/hammer-overflow.419352/
This has been added to the game. There are no visual indicators for the
user yet. This will probably be added later.
@yairm210
Copy link
Owner

yairm210 commented Jun 8, 2021

Clean, simple, and elegant
Excellent work!

@yairm210 yairm210 merged commit 7cad6dc into yairm210:master Jun 8, 2021
@yairm210
Copy link
Owner

yairm210 commented Jun 8, 2021

Fields not present are given the default value - in this case, 0.
Fields present but not in class are ignored.

@Thyrum Thyrum deleted the production-overflow branch June 8, 2021 18:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants