I guess this error was already fixed in SVN.after new SVN i get this dump
I guess this error was already fixed in SVN.after new SVN i get this dump
If you meant city filters, then they never got saved.I was curious, does this release fix the issue of it not saving the option to not show buildings that can not be built. Sorry if this message is confusing, I am operating on a lack of sleep.
When you make any changes to BUG options Always Double save before you continue play, Always. If you do not double save it will Not lock them in. Has been this way for a long long time.I put it the BUG options to not show buildings that can not be built, but PPIO never saves that. So I was wondering if this version fixed that. It is not a big deal, just curious.
Could be typo somewhere in city filter code: saved under different name than loaded.I can't get it to save that either and I'm not using PPIO. I have no idea what happened to make it not hold that data during a save but it was a while back when we decided to remove the usersettings entirely from the initial mod download. Ever since then the unconstructable buildings filter needs to be reset in each city every time you start the game back up. Freakin' annoying but I've gotten used to it. Again, I have NO idea where all that happens.
Nope, sorry, haven't had time for that.I put it the BUG options to not show buildings that can not be built, but PPIO never saves that. So I was wondering if this version fixed that. It is not a big deal, just curious.
PPIO doesn't use the option at all as far as I know, it saves the value of the option fine, but it doesn't care what the option is set to either way.It used to work for me, then one day it stopped working, I think it was after PPIO changed to the format it is now, but maybe it is the SVN.
It is not that way with PPIO. Never figured out why it seems to be that way without PPIO, but I changed how the BUG options saves to a more sure thing in PPIO.When you make any changes to BUG options Always Double save before you continue play, Always. If you do not double save it will Not lock them in. Has been this way for a long long time.
All normally unbuildable buildings (-1 cost) could get this treatment.I was thinking about the 'opaque systems' comment/complaint we got on the other form LP the other day and it occurs to me that there's still some real mystery in a number of our systems for players in the game.
One thing that would be cool to add to a UI wish list would be a screen that would show all the property autobuildings, grayed out if you can't currently get them due to technology, but fully lit if you can, so you can get hover info on them, part of which would show the threshholds of property values at which they would emerge (do the help hovers on those buildings already show this, such as in the pedia?)
Another screen for housing in a similar vein might be neat.
I don't know how much of this would be python side and how much would be SDK side. I'm just initiating the discussion since it would be kinda cool to have that somewhere other than a pedia list only that is more of an in-game display. Not sure how you'd bring that up, maybe as a page under the victory screen or some place like that.
Again, just musing at the moment.