HDIAndrew / EFS

12 stars 0 forks source link

Sometimes the game gets to a state where Engineers don't build anything but are expended #137

Closed floralpond closed 1 year ago

floralpond commented 1 year ago

Description:

In discord, Porfirogeneta reported that he had gotten to a situation where Engineers would not build any cities, but are expended. They supplied two save files, one from a Lost Worlds, and another from Dark ages. I was able to replicate the issue with the supplied save files. Engineers don't seem to be able to build any cities. It doesn't seem to be isolated to certain engineers or certain planets or certain city types or anything like that.

Some additional information for game settings:

Expected behavior: Engineers should be able to build cities

Actual behavior: Some game scenarios got to the point where Engineers couldn't build cities.

Game version:

1.5

Steps to reproduce:

Open either of the attached save files, and go to an engineer and attempt to build a city. For the rigobertofallo.sav, go to Sharprut, and there is an engineer in the Well west of the Palace. For the rimero.sav, go to Ravenna, and there is an engineer to the northwest of the palace.

Lazy_engineers.zip

Additional information:

I was able to get the rigobertofallo.sav to allow engineers to build cities again by advancing one more turn and seems to be OK, but I didn't really do anything special so I'm not sure if it will stay fixed. See rigobertofallo2.sav. RIGOBERTOFALLO2.zip

I'm trying to see if I can get the rimero.sav to work again, but so far no success in the same way. EDIT: I was able to use an autogen galaxy from the rimero.sav that kept the state of the galaxy (except techs and ministries and that sort of thing), and using that file, engineers seemed to have no problems. So it doesn't seem like it's because of having too many cities or anything like that.

Matt-Caspermeyer commented 1 year ago

I have an update on this issue.

I have created a fix that is currently undergoing our testing, review, approval, and merge process.

Once this process is complete we hope to provide the fix in a future update (V1.51)