BlueTemplar
King
- Joined
- May 14, 2006
- Messages
- 611
Path and Road have the same shortcut : R, while Jungle Camp doesn't have any.
Path and Road have the same shortcut : R, while Jungle Camp doesn't have any.
I keep getting a CTD on this save here...I have no clue what the issue is...any help would be appreciated.
I'm using rev619 - I am downloading latest version now and will try and use this save with that version and see if that works.
Will there be any incompatibility issues using a 619 save with the 623 version that you are aware of?
They don't show up in WB?
JosEPh
Nope. Some iterations have a few uranium sources, while others haven't a single one. I think this might be specific to a few map scripts as I recently switched from almost always using perfectworld2, but I thought that it was definitely odd for such a critical late game resource not to be included.
Example from the pangea mapscript included (rev 622). Settings for resources were standard; standard map size.
@Blue Templar,
There is a BUG Option setting for it to show or not. Go into BUD screens and find it and turn it off.
JosEPh
45°38'N-13°47'E;12304529 said:IIRC that option doesn't work. That BUG reminder will always remain there no matter what you do.
Edit: Or better, IIRC that option makes something else, but I don't remember right now what is doing.
45°38'N-13°47'E;12304519 said:You're right, there's no uranium. Could be the map which is too small. Anyway uranium could popup just mining here and there, so it's not 100% certain that you won't find it before the modern era.
Is there any way for me to manually tweak the map script in order to force at least one resource of each critical type without using the "balanced" option? I had one game I played up until modern in which there was plainly no uranium. I had a decent tech lead but was facing an opponent with a very large force and so nukes would have been quite useful at that point.![]()
If you want that reminder to stay gone, you have to edit the file Assets\Python\Afforess\AutomatedSettings.py and either delete or comment out lines 27 and 31. That is what's turning the reminder back on every time you start a new game or load a saved game.
45°38'N-13°47'E;12305693 said:No, I don't think it will work. That option that you are disabling this way, is the same that you can disable via BUG menu. It doesn't disable the blinking BUG option reminder. It just disables the option box that appears on the right when you start or load a game.
def onLoadGame(self,argsList):
self.optionUpdate()
MainOpt.setShowOptionsKeyReminder(True)
def onGameStart(self,argsList):
self.optionUpdate()
MainOpt.setShowOptionsKeyReminder(True)
What I'm referring to is getting the reminder to stay gone once you turn it off from the BUG menu.
This piece of code is in both the ANewDawnSettings.py file and the AutomatedSettings.py file.
Code:def onLoadGame(self,argsList): self.optionUpdate() MainOpt.setShowOptionsKeyReminder(True) def onGameStart(self,argsList): self.optionUpdate() MainOpt.setShowOptionsKeyReminder(True)
To keep the reminder from reappearing, the line MainOpt.setShowOptionsKeyReminder(True) has to be deleted or commented out in both files -- it's been done in the ANewDawnSettings.py file, but not the AutomatedSettings.py (looking at the logs, it was done to both of them at one point, but that got lost during a revert). Otherwise, the reminder will show up again whenever a new game is started or a saved game is loaded.
45°38'N-13°47'E;12305842 said:Edit: On second thought, it could be better to disable automatic blinking of Ctrl+Alt+O on loading the game but leave it there when starting a new game. That way you only have to disable it when you start a game but people won't forget about the option (if you remove it completely, I'm sure people will ask in the future how to reactivate it).