Development Thread

[Sam_Yeager]

BTW, when you turn off espionage, you never get to see power ratings or scores for any civs. Should we entertain the idea of "fixing" this optionally -- off by default -- or leave it to Firaxis to patch?

Solver's posted a link to a patch in the patch thread.

 

[EmperorFool]

Solver's posted a link to a patch in the patch thread.

That covers the graph, but BUG also shows the power ratio in the scoreboard. This would require modifying CvMainInterface.py specifically for BUG.

 

[alerum68]

Can we make it not optional? Something that says if no espionage is triggered, then you cannot see power in the score? Or is having it optional and can be turned on and off at will, our only option? (I'm testing you here, I think I know the answer.)

 

[EmperorFool]

I guess I get an F because I understand none of what you wrote.

As it stands, if you disable espionage, you can never earn enough espionage points to see demographics. Thus, you'll never see the power ratio in the scoreboard.

I'm suggesting an option that would show the power ratio for all civs in this case, just as it was before espionage was introduced. The same would apply to the graph.

To be clear, if you play with espionage enabled, you would still have to spend points against a civ to see their graph and power ratio, just as it is in 3.13.

My reasoning is based on my assumption of Firaxis's intentions, that disabling espionage should make the game play like it did before BtS -- you can always see the demographics of other civs.

 

[·Imhotep·]

The problem code is

if not gc.getGame().isOption(GameOptionTypes.GAMEOPTION_NO_ESPIONAGE):

This will fail in 3.13 as it stands. I could try wrapping that bit in a try/except block and having someone without the patch check it out.

Reading through the 3.17 thread makes me think there might be a not-insignificant number of people that will stick with 3.13 for a while -- or maybe people just whine but upgrade anyway.

@EF:

I do not know Python, but I think you could use the new function to solve the problem:

Added ability for mods to specify minimum version (MIN_VERSION in GlobalDefines.xml)

Now there must be some function that checks the version of the game for MIN_VERSION to work, and then it should be fairly easy to wrap your code into it:

//something like
if game_version == 3.17 
if not gc.getGame().isOption(GameOptionTypes.GAMEOPTION_NO_ESPIONAGE):

 

[EmperorFool]

Added ability for mods to specify minimum version (MIN_VERSION in GlobalDefines.xml)

I'll check that out, but it sounds to me like this allows you to say "this mod only works with 3.17 or higher". What I actually want is "this mod works with 3.13 but will take advantage of 3.17 features". The Python I was talking about is pretty simple; I just have to test in 3.13 to see if it works.

try:
  bEspionage = gc.getGame().isOption(GameOptionTypes.GAMEOPTION_NO_ESPIONAGE)
except:
  bEspionage = True

if bEspionage:
  ...

The try/except clause basically says, "try <this> except [if there is an error, do] <that>". I'm hoping that CyGame.isOption(int) throws a Python exception instead of crashing to desktop due to a failed assert. I'll find out when I get home tonight.

 

[EmperorFool]

I've added CvInfoScreen.py and updated CvMainInterface.py with the "No Espionage" option changes only. If you're playing with 3.17 and you turn on that option, disabling espionage:

• The scoreboard shows the power ratio for all civs,
• The Info screen shows the graph for all civs, and
• The Espionage graph is removed from the drop-down menu.

Can someone please test this in 3.17? In 3.13 you should see no difference.

Note: I haven't done the rest of the 3.17 CvMainInterface.py changes (shrinking Research/GG/GP bars). If anyone wants to tackle those, that'd be terrific. Best to diff the 3.13 and 3.17 stock versions and apply reasonable changes to the BUG SVN version.

 

[ruff_hi]

added worst enemy to BUG military adviser
added BUG Military Adviser to credits tab (me for sit rep, EFool for deployment)

 

[NikNaks]

Not too sure if this is the best place for this, but it's the best without starting a new thread.

I've made another (hopefully better) icon for the mod. It looks like this:

It's in SVG format, which means you can make it any size you like. It looks a little jagged around the edges because I re-sized the exported PNG. It can look a lot nicer at that size
Thoughts?

 

[alerum68]

It looks good. Is it set up properly to be used as an icon?

 

[NikNaks]

No, but it can be. I wanted to get some feedback before I started doing that.

 

[alerum68]

The only thing I'd suggest is maybe dropping the legs, but other then that I'd say go for it.

Glad to see you back around.

 

[NikNaks]

You mean get rid of them, not make them longer or something, right? English even confuses us Anglophones sometimes...

 

[alerum68]

I don't speak English. I speak American. Two completely different langauges that just sound alike. Yes, I mean getting rid of them.

 

[EmperorFool]

Ya looks great! Yes, ditch the legs or add two more (for six total). As a .ico, though, I think the legs would muddle the image. Hard to tell at that scale.

 

[NikNaks]

Okay, find it attached

 

[alerum68]

Sweet. Will use this for the Installer Icon, and the Help File icon as well.

 

[EmperorFool]

It's that time again!



No . . .



Closer . . .



Seriously, seek professional help.


It's release time!​

With all the new stuff added lately, bug fixes, and 3.17 compatibility, it's time to kick BUG 3.0 out the door. We are targeting a code freeze for noon (PDT) on Sunday, July 6th. Alerum will package it up, and we can pound on it for a while to make sure it's solid.

In the interim, please post here any new features you are planning. We may hold off on anything that is too complex. If you need translations (new text), post it here so the translators can be prepared. Finally, please test the heck out of the SVN version. It is 3.13 and 3.17 compatible.

Happy BUGin'!

 

[Cammagno]

It's that time again!



No . . .



Closer . . .



Seriously, seek professional help.


It's release time!​

With all the new stuff added lately, bug fixes, and 3.17 compatibility, it's time to kick BUG 3.0 out the door. We are targeting a code freeze for noon (PDT) on Sunday, July 6th. Alerum will package it up, and we can pound on it for a while to make sure it's solid.

In the interim, please post here any new features you are planning. We may hold off on anything that is too complex. If you need translations (new text), post it here so the translators can be prepared. Finally, please test the heck out of the SVN version. It is 3.13 and 3.17 compatible.

Happy BUGin'!

@ Alerum: the new release is supposed to have an updated help file? If so (and I think it should, if possible), I'll try to complete the Italian translation of all the help pages in time, even if I'm a bit busy, if not I'll take it easy, so... please let me know

 

[alerum68]

Yes, I'm going to recompile the help file. There are 2 files that need to be written still. One is the MA which either Ruff or EF need to write up, but that's going to be tricky since it's not completed yet. The other is PLE which I'm working on converting to HTML.