AGEOD Forums

[color=blue]The AGEOD team recognize the enormous number of volunteer hours spent improving the Rail network accuracy, addition of new regions to enhance historical play, creation and adaptation of the "Kentucky Mods" to give a different "feel" to the start of the war, numerous other fixes and enhancements by various modders to the Database, and public beta testing of new executables and changes. Without the efforts of the community, AACW would not be as complete as it is today. We all know games are never perfect or can ever be considered as finished, but help and implication of our fan base always leads to a better product, and, once again, THANK YOU ALL!
================================================== ========================
AGEod's American Civil War Update 1.16 Release Candidate 5
November 8, 2011
================================================== ========================
= New AI parameter: aiCTM_ThreatValInFow in AI.opt to help regulate AI aggressivness

= Depot build bug fixed. Depots can be built with Supply or Transport Ships/Bateaux to the level defined in 2Depot.str
(where MaxLevel = 1)
===Depots cannot be “built up” above level 1, but can be defined higher in a Setup or Event.

= New parameters in settings to regulate Automatic Experience gain. Bug fixed.

= Ammo non-consumption bug fixed.

= "Scrambled" Battle Reports bug fixed.

= There is now a stack (group) name memory. Basically when the scenario setup is created the current name is also stored. This has been done (and is very often useful) so that the name of a stack doesn't change as soon as you move a unit out of it, or the reverse. A stack will assume a new name by merging the stack into another unit or stack.

= An insidious bug with the "NotEnemy" script parameter is fixed. (This was part of the issue with the "Hortelez Supply" arriving in Enemy Ports in WIA.)

= Cavalry won't switch posture when crossing a river, even if 100% hostile MC on other side

= Bug fixed where sometimes a replacement was used from a wrong faction tag to replace an element in an unit

= Fixed Naval movement bug between 1451Matagorda Bay and 1278Lower Colorado River

= Removed events changing the Fixing of KY Militia when Kentucky joins a side. (The ''old'' Kentucky system)

= ''Cleaned up'' the Kentucky Entry.sct (The ''new'' Kentucky system).
=== Created ''Kentucky Unblock.sct'' to reduce replication of code.
=== Changed all ChgEvtOccurs to SetEvtOccurs commands for clarity and error reduction.

= Removed all ''RESERVED'' Models and Units to save space and speed loading

= Enabled Model and Unit cache files, to speed loading. Modders must remember to delete these files after changing a Model or Unit, or the change will not be read by the game engine.
[/color]

deguerra wrote:Would this be save game compatible with previous 1.16 releases? Understand if its not, but just curious. Thanks for the great and continued support, AGEOD and all the many volunteers!

gchristie wrote:

I'm eager to jump back into PBEM play once the patch is released.

Philippe wrote:It's a little late to be throwing in my two cents for something this minor, and I fully realize that if it involves making anything more than simple cosmetic changes it would probably be dangerous to attempt this late in a patch's production.

But is there any chance of re-naming the two counties of Connecticut that appear in the extreme north-east corner of the map? I brought this question up a few years ago and it didn't receive an enthusiastic reception, but I'm mentioning it again now just in case.

In the game the southernmost county (the one with Danbury in it) is named Westchester. I actually live in Westchester New York and used to do work in the parts of Connecticut that are adjacent to the New York border, and can assure you Westchester Connecticut is a misnomer. If you can do it without having to track down too many changes, I would propose that the "county" name you should use is Fairfield.

[I think the mistake arose because that part of the map was translated from the BoA map, where an area that was mostly in New York and named Westchester spilled over into CT and included Danbury. I don't have a problem with that, but here, the different scale lends itself to a greater degree of accuracy.]

The county to the immediate north of Westchester CT should probably go by Litchfield rather than Berkshire. Again, this comes from the geography of BoA leaking into AACW. It wasn't a problem there, but it really doesn't look right here.

I realize that the best you can probably do after reading this is to sigh. If this correction can't be made, I'll just have to hope that I've made enough of a fuss about it for it to show up in AACW2.

lodilefty wrote:Let me look.
While renaming a region per se can be a disaster (all references to it must also change) AFAIK, there is a "Region Display Name"capability that exists.

Stay tuned!

Philippe wrote:You're a gem. I just hope making the change doesn't have any unforseen consequences on any reinforcements that might arrive from up there.

ohms_law wrote:Moderate bug:

In the Full campaign W/Kansas scenario, Raphael Semmes is available to the Confederacy on turn 1. He then becomes available again, by event, on turn 32. After the event fires the original Semmes is apparently deleted and then recreated in the Atlantic Shipping box (I can tell that he's recreated because I promoted him this time around [why not?], and he reappears in the Shipping box as a one star who is promotable again).

ohms_law wrote:Moderate bug:

In the Full campaign W/Kansas scenario, Raphael Semmes is available to the Confederacy on turn 1. He then becomes available again, by event, on turn 32. After the event fires the original Semmes is apparently deleted and then recreated in the Atlantic Shipping box (I can tell that he's recreated because I promoted him this time around [why not?], and he reappears in the Shipping box as a one star who is promotable again).