April Campaign Alt Leader scenario (WIP)

[runyan99]

I'm hoping to create a new scenario which will be compatible with the official version of the game, without overwriting any files. Not really a mod, just a new additional scenario.

The basic idea is simply to reevaluate leader ranks, and cut down on the number of corps commanders in the game. I'm also adjusting the arrival dates of many of the generals. I'm using Hancock's arrival times from his leader mod in most cases.

No stats are being changed, because that would mean editing Unit and Model files. So, all leaders have their original Strategic, Offensive and Defensive ratings and traits.

This scenario is a work in progress, and incomplete. I'm posting it here so that experienced modders can tell me if I am editing any of the .XLS files incorrectly.

Once all the data is complete, I'm hoping someone will be able to compile the XLS files into a new scenario, because I cannot get that right....

I do have a question about adding Units and Models data. While I'm not changing any of the original files, in some cases I need to ADD new Units and Models data for leaders who do not have profiles at * rank. I'm guessing that by simply adding the appropriate new lines in the Units and Models .XLS files, that will be sufficient to create the leaders I need. I have created about 4 of these * leaders so far using the empty and reserved slots. They can be found and the end of the files. The new leaders start with a * ranked C. Hamilton. If there is any additional step I need to take, please let me know.

Attached is a zipfile with the .xls files edited so far.

And a changelog to date:

CSA

Jackson, Bonham and Holmes arrive as *, not **
Bragg arrives as **
Hardee arrives as **
Pemberton arrives as **

DR Jones moved to the 61 generals
WHC Whiting moved to 62
Carter Stevenson moved to 62
EP Alexander moved to the 63 generals
Charles Winder moved to 63
Robert Hoke moved to 64


Simon Buckner's arrival date changed to 01/1862
John Pemberton's date changed to 09/1862
John Marmaduke's date changed to 03/1863


Edward Johnson no longer automatically promoted to **
Jackson and Longstreet now automatically promoted to ** on 06/1862
G.W. Smith no longer automatically promoted to **



USA

Buell's arrival date changed to 01/1862
Hooker's arrival date changed to 10/1861
Sigel's arrival date changed to 09/1861
Hancock's arrival date changed to 10/1862

Sumner, Heintzelman and Keyes automatically promoted to ** on 02/1862
Phil Kearney no longer promoted automatically

The following leaders now arrive at * rank, instead of **
Robert Milroy
Charles Hamilton
L. Rousseau
J. Foster
A. Whipple

David Birney moved to 62 generals
Francis Blair moved to 62
Henry Hunt moved to 62
G. Morell moved to 62
C. Griffin moved to 62
A. Humphreys moved to 62
A. Howem moved to 62
I. Rodman moved to 62
R. Schenk moved to 62
T. Wood moved to 62

H. Berry moved to 63
C. Devins moved to 63
J. Geary moved to 63
D. Gregg moved to 63
R. Johnson moved to 63
J. Caldwell moved to 63
A. Hays moved to 63
J. Barnes moved to 63
C. Pratt moved to 63


J. Dix removed
P. Marston removed
E. Food removed
E. Clarke removed
B. Hanson removed
J. Totten removed

New * Units and models added for
C. Hamilton
L. Rousseau
J. Foster
A. Whipple
R. Schenk
G. Dodge
H. Berry
J. Forney

Maximum number of CSA/USA divisions increased

[McNaughton]

Technically, if Bragg is listed as a 2-star general when he arrives, Jackson, Johnston, Holmes, Magruder and EK Smith should be promoted. They were all contemporaries in seniority, and commanded corps-sized forces in 1862. Historically they were all promoted in October 1861, and thereby very similar in seniority as Major Generals (Lee had to promote Longstreet and Jackson later on, as well as transfer Magruder and Holmes out of the theatre in order to solidify his command structure based on seniority). Technically, Jackson, Longstreet, Magruder and Holmes all commanded corps-sized forces in late 1861-early 1862, so dates of promotion to two star of June 1862 are historically very late.

Also, events could have done what you wanted without having to create a separate PBEM scenario.

[Jagger]

If you create a new model or unit file, you will need to add references to them in the uni_alias and mdl_alias files within the Alias folder.

The model/unit files are named with a number. The reference in the alias files will need to reference the file number. If you open up either of the alias files, you will see the format.

[runyan99]

If you create a new model or unit file, you will need to add references to them in the uni_alias and mdl_alias files within the Alias folder.

The model/unit files are named with a number. The reference in the alias files will need to reference the file number. If you open up either of the alias files, you will see the format.

I noticed that from Hancock's mod, but I didn't see any way to edit the alias files in the .XLS files. I wasn't sure that these alias files couldn't be automatically kicked out when compiling from the .XLS files. I don't know where those alias files come from, if they are generated, or made by hand.

[Jagger]

I noticed that from Hancock's mod, but I didn't see any way to edit the alias files in the .XLS files. I wasn't sure that these alias files couldn't be automatically kicked out when compiling from the .XLS files. I don't know where those alias files come from, if they are generated, or made by hand.

The CVS splitter will create new alias files when you convert the XLS sheets to create the new unit/model files. Make sure the new alias files are placed into the alias folders.

You can also do it manually but best to work with the spreadsheets and use the CVS splitter.

[Jabberwock]

IIRC, Hamilton was promoted to * after Yorktown, ** after McClellan shipped him out west.

[runyan99]

Okay I've updated the XLS files and the changelog attached in the first post. Now the hard part.

Can anyone familiar with the CVS splitter use the attached files and generate a new scenario file? Let's see if we can get it to work.

Be aware - the included files have not been renamed, and whatever internal references that tell the scenario to look for the new CSA and USA events files have not been edited. The compiling person will need to make those changes, and also use any of the additional stock (unedited) database files needed to compile the scenario. Also note that there should be 8 new units and 8 new models files for the generals who have been demoted to appear at * rank. These leaders are listed in the changelog.

If successful, please attach here the generated files, and also your new version of the XLS files with the changes made.

[Pocus]

Not that I want to push you to learn, but the process take 15 mn to understand and is explained in the wiki I think.

[Eugene Carr]

Had a try but obviously doing something wrong, managed to create the new scenario file which loaded but never got any reinforcements after first turn.
Suspect something to do with naming files in the events folder.

Had the first set of files you posted running by just overwriting existing and I liked the idea of more Brigs , would like to see it combined with a restriction on number of divisions early on (like Experimental Mod ) and seniority reworked to be more historical.

Hope someone else can get this running for you.
S!

[runyan99]

I cannot do it. The process it too complex, and the instructions are insufficient. As soon as I start, I am left with questions I cannot find the answer to. I'm left in a sea of questions.

For example, the first few sentences of the Wiki leave me lost

Scenarios in AACW have the .scn extension. They are to be placed in the ACW\Scens directory. If you created some events tied to this scenario, a file named as the scenario, but with the .sct extension must be placed to the ACW\Events directory.

First, there are at least three different kinds of events files. Leaders, various and USA/CSA events. What events files do the above instructions apply to? All of the stock scenarios seem to share the same events files. What if I want my scenario to utilize my custom events files? I have edited the USA Leader events and the CSA leader events XLS files. But first how do I get these files from XLS to .sct format? The instructions do not say at all. The instructions only speak about the events tab in the scenario XLS file. Also, does my custom scenario know which events files to use because they have the same name (I don't think so) or is it because of cells D4-D7 in the events tab of the scenario XLS which appear to list the applicable events files?

[McNaughton]

I cannot do it. The process it too complex, and the instructions are insufficient. As soon as I start, I am left with questions I cannot find the answer to. I'm left in a sea of questions.

For example, the first few sentences of the Wiki leave me lost



First, there are at least three different kinds of events files. Leaders, various and USA/CSA events. What events files do the above instructions apply to? All of the stock scenarios seem to share the same events files. What if I want my scenario to utilize my custom events files? I have edited the USA Leader events and the CSA leader events XLS files. But first how do I get these files from XLS to .sct format? The instructions do not say at all. The instructions only speak about the events tab in the scenario XLS file. Also, does my custom scenario know which events files to use because they have the same name (I don't think so) or is it because of cells D4-D7 in the events tab of the scenario XLS which appear to list the applicable events files?

Trial and error. Once you figure it out, it is easy going from then on.

Just follow the instructions EXACTLY, do their little test, and you will understand the process. Don't do your own modifications first, do that after you get the process.

Use this link, as I don't think it has been fully implemented into the WIKI as of yet...

http://www.ageod-forum.com/showthread.php?t=3974

[runyan99]

I could follow the instructions exactly, but the problem is the instructions don't get me where I need to go. The example doesn't change what I want to change in some cases. Once I try to make changes that go beyond the example given, I don't have the knowledge to make the changes correctly.

I feel like I have instructions on how to change a battery on a car, when in fact I need to replace a muffler. What I really need is an overall undertanding of all the parts of the car, otherwise I cannot tinker with it without ending up with a useless pile of junk.

Also, I've seen it before, but the link you posted also leaves me with a lot of questions.

11. Copy the created 'Script.ini' to the game directory '...\AGEod's American Civil War\ACW\Scripts\'

This part with the script.ini puzzles me, because the directory in question already contains a file with the same name. If I compile a new script.ini from my edited scenario setup file, and overwrite the original script.ini, doesn't that cause a problem with something else?

[McNaughton]

I could follow the instructions exactly, but the problem is the instructions don't get me where I need to go. The example doesn't change what I want to change in some cases. Once I try to make changes that go beyond the example given, I don't have the knowledge to make the changes correctly.

I feel like I have instructions on how to change a battery on a car, when in fact I need to replace a muffler. What I really need is an overall undertanding of all the parts of the car, otherwise I cannot tinker with it without ending up with a useless pile of junk.

Also, I've seen it before, but the link you posted also leaves me with a lot of questions.

This part with the script.ini puzzles me, because the directory in question already contains a file with the same name. If I compile a new script.ini from

my edited scenario setup file, and overwrite the original script.ini, doesn't that cause a problem with something else?

No, just overwrite it (all other scripts are backed up). Every time you 'compile a scenario' (Press F9 during the game loadup) it takes the script.ini and uses this as the basis. If you make a new script.ini, for a new scenario, it won't over-write a thing creating the scenario (imagine it as a zip file, the outside name is the same, but the internal stuff is different and won't over-write when you compile the scenario).

So, just create the script.ini, save it to that directory, overwrite the file, and compile the scenario. Most likley you will get many errors during your first few compiles, as there will probably be mistakes in the scenario creation (an incorrect connection between units, a conflict, a missing file that you forgot to copy, etc.). Just check the main.log file and it will tell you where your error is.

I suggest start small, with just one change to a scenario (follow their instructions exactly, create that modified city file), just to see how the process works. This way you won't have to be befuddled by errors when you are trying to work on the system on how to compile the program.

It took me a while to become very comfortable with the system, but, now I can create and modify very easily. It just takes time, practise and getting over that initial learning curve.