Thanks for putting up the pre-release! When trying the SVN, I'm getting an error on the link
https://revolutiondcm.svn.sourceforge.net/svnroot/revolutiondcm/RevolutionDCM
doesn't exist
@Nudden:
I can't reproduce this bug. Does it occur in the latest prerelease version? You can just download from the link below and reinstall, and it'll update for you automatically, the prerelease is still save game compatible with the version I posted a few days ago.
Oh, now I see it. You don't have alphabet yet, which means by default BtS rules you shouldn't be able to adjust Espionage. This is default BtS behavior, research alphabet, and you should be able to adjust the rate, if not let me know.
Now this reminds me about one thing - I'm pretty sure I've seen AIs adjust Espionage rate if I use AI Autoplay at the start of the game and without Alphabet.. on rare occasions. Don't have now screenie to prove it but if I'll see it happen, I'll take a screenshot.Oh, now I see it. You don't have alphabet yet, which means by default BtS rules you shouldn't be able to adjust Espionage. This is default BtS behavior, research alphabet, and you should be able to adjust the rate, if not let me know.
Hey glider, one thing that's always bothered me is the hit% of ranged bombard. I have all the units with it enabled set to 100 accuracy in the XML in LoR, but they don't seem to hit more then 1/3rd of the time in the field, and maybe 10% of the time against units in cities. I think the XML needs to change to reflect actual values. Why is 100 so low? Where in the DLL is this controlled, and how can we give modders more intuitive control over the accuracy of the units when ranged bombarding?
its in the globaldefinesalt.xml: Bombard Inaccuracy. For some crazy reason its set to give artillery a 250% penalty for accuracy in default revDCM, making ranged bombard a rigged crap shoot.
<Define>
<!-- RevolutionDCM variable - higher values increase ranged bombard inaccuracy making city attack/defense harder against the AI. 100 is equal to previous releases -->
<DefineName>DCM_RB_CITY_INACCURACY</DefineName>
<iDefineIntVal>350</iDefineIntVal>
</Define>
I'm not 100% sure, I think actually if you put it at 100 it will be exactly what it says, but I haven't tested it enough to really know for sure.