pandakraut

Size of Cabell and limit of 10 is intended. Not being able to cap off the men in the unit is a side effect. Will see if I can fix it. Will also get back to you on your other longer posts, just haven't had time for a longer response yet.

Yes this was changed to reduce the effectiveness of dumping vets into a new unit. AI pathing to return detached to unit uses a straight line regardless of where that would take the skirmishers. So it's as likely to just get them killed as anything. The AI also only detaches from a small percentage of their total units at any one time, so they will end up cycling in new detached skirmishers as the initial ones get destroyed.

Crashing on game startup usually this means that installation was only partially successful. Double check that you have an /ultimate general civil war_DATA/mod/rebalance folder. The crash usually means that the config files aren't being found. If that doesn't work let me know.

Have you seen the tooltip when hovering over your total recruits? The information there has been expanded to show the totals for all the pools. I'm not sure if I can get tooltips to appear off of the veteran/recruit checkboxes but will take a look.

Strong units will generally have higher stats than the stats of your veteran pool, so when adding veterans the unit's stats will go still go down. However, the stats will decrease less than if you added recruits. Since the veteran pool stats are the average of all casualties taken the stats will generally always be worse than your best units. This has the effect of making it easier to create and maintain 1* units, but harder to maintain 2 and 3* units. But as long as you're keeping your kills high and casualties low on your better units you can net a positive change in stats even after adding vets. Investment in training and medicine will assist in this process. If your high veterancy units end up taking too many casualties consider merging them with another good unit. A lot of the extraneous time has been cut out of battles which makes it harder to full clear this, this has a side effect of reducing xp growth, but I think the rate is fine at the moment. The bonus to a unit's progress towards the next star is determined by the officers xp and modified by the battles led bonus. So assigning a high ranked officer will still provide a significant bonus, as would assigning an officer with high battles led. I frequently assign high ranking officers to units to push them over the threshold to gain a star, though sometimes planning ahead by a few battles is necessary. It's not clear to me what you're requesting here. When moving the slider you can see the affect of the added veterans/recruits on the units stats already as well as the number of men being added from the respective pool? Allied officers appearing in the reserve was a bug that was partially fixed. Some still slip through now and again, but it's less consistent now that the bug is fixed. If you have more officers wounded the replacement officers can end up filling up the reserve a bit, but otherwise the only way to get officers there is to buy them from the academy. That section of the UI is unfortunately very locked down. There is little to nothing we can change there. While the constraints are arbitrary, I do think they have a decent balance of options. Tying the selections to later events is something we've discussed, but no definite plans at this point. Glad to hear you're enjoying the new version overall

Main post will be updated later when Jonny has time but for now Rebalance Mod V1.28.3 is now available Steam: https://www.dropbox.com/s/yvjxgnp4n305j9s/RebalanceModV1.28.3.zip?dl=0 Good Old Games: https://www.dropbox.com/s/hhchd9jcrfy85n9/RebalanceModGoGV1.28.3.zip?dl=0 Changelog Highlights - Campaign battles now updated through Fredericksburg. - Units that are charging apply a morale regen penalty to enemy units that are not charging or in melee. If the enemy unit is moving, the penalty is increased. - Artillery canister damage, cavalry pistol damage, and mounted carbine cavalry reload speeds reduced. - Morale damage resistance increased from morale stat and several perks. - General scaling reductions with higher reductions in specific battles. - Improvements to several underused cavalry, infantry, and artillery perks. - Static Mode: Optional mode that removes all scaling against player units. Instead the AI units are all set to a default size based on the current campaign date. Specific battles that normally have larger default sizes can exceed these size restrictions. Player units are limited to same size as the AI. This mode is very bare bones and by default can result in facing larger units than the normal scaling algorithm. There is also little to no adjustment to sizing between difficulties, so adjustment using configs is highly recommended. This mode can be enabled in the configFile, the percentage size of the player units can also be adjusted there. By default the AI size caps out at 50% of the normal maximum sizes. Maximum sizes can be adjusted in the AIConfigFile if larger or different sizes are preferred. AIscalingSizeMultiplier will also continue to work to make adjustments to sizes. full changelog is in the /Mod/Rebalance/Change logs folder

I ended up having very little time to work on getting it ready over the weekend. Will try to finish up the change notes and the package tonight. The units in the west are just a delaying action. I wouldn't be further west than the edge of the river.

Saves are always compatible

Did you update to one of the test versions at some point between those battles? At cold harbor you can capture enough enemy wagons that could solve the issue, but I would have thought the side battles after it were still a problem. I'll have to think on the multiday casualty issue. Maybe there is a way I can get it to work without reseting the units starting point. Though that may open up other bugs it was covering over. Will see what I can do. Richmond day 2 is definitely a walk over. Should be able to make it more interesting once we get to updating it(will be a while.) 1.28.3 is nearly ready, hopefully we can get it posted this weekend.

yes

The 12 gun limit was found through extensive in game testing to compare damage between guns. It was later mostly proved the be correct by data mining the actual in game calculation used. The actual limit is 14 but the difference between 12-14 is minimal. You can find graphs here I'd highly recommend just using this mod which fixes the curve to be diminishing instead of parabolic among a variety of other bug fixes. https://forum.game-labs.net/topic/25750-ui-and-ai-customizations-mod-v192/ The Napoleon is mediocre in my opinion. It has a terrible range curve and is only good close in. I replace it with 24pdrs or rifled guns as soon as possible.

There have been some other players on the discord who have also had trouble with newport. Here are some the suggestions that worked for them. Consider bringing a melee cav unit. They can help you clean up routing units so that they don't come back over and over. Just be careful about where you use them so they don't get shot too much in melee. And watch out for the enemy cav. Try using the fortifications, they are significantly better in the mod and can help against charges. Keeping an arty unit for the high morale shock damage can also be very useful. Though it is a bit of a trade off since it's harder to cover everything with only 2 infantry. Hope this helps, good luck!

This is pretty normal for legendary. Will vary a bit depending on how many infantry units you create and of what size. If you'd prefer a bit easier version the configs are always an option. If this is your first attempt at legendary you may want to consider setting the size multiplier to .85 as a bit more of a stepping stone.

Are you running 1.28.2 or one of the 1.28.3 test versions? There is a bug with the artillery resupply costs in 1.28.2 that would largely explain what you are describing. Some of the other changes appear to have affected this battle more than intended. Will try to get some kind of initial update into the next release. In the meantime I'd just use the /mod/rebalance/AIConfigFile to adjust it a bit. Give AIscalingSizeMultiplier of .7 a try maybe?

Sorry if I overlooked your response in the main mod thread. Responded there with more details.

The install for that version and the current version should be essentially identical. Most likely one of the files in the zip did not end up in the right spot. Make sure you are extracting into C:\Program Files (x86)\Steam\steamapps\common\Ultimate General Civil War\Ultimate General Civil War_Data. You should not end up with a RebalanceModV1.27.4.3 folder if you did it correctly. Here is the link to the older version: https://www.dropbox.com/s/w0neimnw0et3ebv/RebalanceModV1.27.4.3.zip?dl=0 If you're still having trouble let me know.

Any unit in the generals aura gets 25% more xp from any actions they take. Parker's I always defended off point in the woods to the right. Since this battle hasn't been updated yet feel free to just adjust AI unit sizing and quality in the configs to what feels fun(no issues if you want to do this with updated battles as well.) For Stones River you may need to fall back from your positions on the right to form a more concentrated line.

The default values of both of those are 1 since it results in no change to the defaults. Setting them to 0 will set AI units stats to 0 and give them the worst possible weapons. Nothing wrong with questions here, though I am more likely to overlook posts or respond to them more slowly than on discord. This was added to the mod a while back. You can use the hotkeys t and y to set the unit to only canister or on canister + shell. There are also buttons available(borrowed the supply infantry and supply artillery buttons from the supply wagon).

Sorry I overlooked this question. Yes the mod/rebalance folder should go into the /Contents folder. Unfortunately, my ability to provide support on macs is very limited. The instructions in the main post have been reported to work from other mac users.

Not quite sure which numbers you are referring to here. By forecast do you mean the army size listed on the campaign screen recon report? Or on the pre-battle corps deploy screen? The recon report number is basically a snowball factor, it's not an actual indicator or limiter of how many men the AI will deploy in a given battle. The pre-battle corps deploy numbers should be roughly accurate. They don't factor in potential splits, but even with very bad luck that shouldn't result in more than a 10% change most of the time. By second boss battle do you mean Shiloh? 100k is significantly more than is normal on legendary unless you are doing something to massively scale up the AI units. What is your average infantry unit size? What is your largest infantry unit? What difficulty are you on? If you built a 4k unit or something like that it could explain these numbers. The scaling algorithm is considerably more complex than what you are describing. Turning it off entirely results in wildly unbalanced battles, some harder and some easier because the default sizes were entered with the expectation that they would be modified. What the AIscalingSizeMultiplier config option does is apply a multiplier to whatever the final size of a unit would be as determined by scaling. So for example if scaling determines a unit should be 3,000 and you have changed the config value to be .8, then the resulting unit size would be 2,400. My general recommendation is build the army you want to build, if the difficulty is too much just adjust the multiplier down a bit to what feels reasonable. Also, unit size is rarely the highest priority. Stats and perks are far more important, size just tends to give you more durability. Enemy weapons and experience do not scale off the player army in any way. The mod tries to support players who like to play with a variety of unit sizes. Some players like to play with 1k infantry, some like 6k. This only works if the AI units adjust somewhat against what the player is using. Because of this, the scaling has been modified to try to keep the AI roughly in the same size range as the player. So if you build only 1k units you normally won't face units larger than 2-3k(some battles can be exceptions on higher difficulties.) If you are building 3k units you'll probably be facing 4-5k units depending on difficulty. The anti-ballast change was designed to prevent players from exploiting this and building a few 6k units while the rest of their army was 1k. As long as you aren't building units more than 2k bigger than your average unit size this won't have any affect. We are also working on an experimental mode where the AI actually doesn't scale and instead has its sizes determined by campaign date. Player units are limited to the same sizes. This system has significant flaws and ends up being harder than the scaling system in many cases, but if you have trouble disconnecting the idea that changing your army can change the AI's then it seems to be the solution. A test version that includes this mode is available on the discord, full release is probably still a few weeks away at best.

Looks like the AI took advantage of some insufficiently supported artillery May have to adapt prior approaches to this battle a bit.

Potentially yes, but the follow-up there would be that the stats would need to come from your veterans, which requires you to actually lose units to captures before you can have an exchange. Other options do exist, but at the moment the veteran pool seems pretty healthy as is from what I've seen. But it's something that we'll keep in mind in the future.

Saves are stored at C:\Users\YOUR USERNAME\AppData\LocalLow\Game Labs\Ultimate General Civil War\Save\CampaignBattle appdata is a hidden folder by default, you'll need to change your folder settings to display it.

Ok, clearing with cav seems fine. Getting the Ohio units across would not have been, so all good there. Yes, don't lose immediately if you end the phase without it. But I think you only have until the contested timer to take it back(not 100% certain on this.) After the battle the level of the AI size, AI training, and AI weapons are checked against expected timeline values. This affects the chances of which type of reinforcement will be generated. Recruits will always be generated, but there is also a chance that either officers, weapons, or veterans get selected. There is randomization involved in the troop amounts, and if you kill enough to push the Ai size below the minimum, the reinforcement amount will be boosted to bring it back up to the minimum. But in this case you're still keeping them at the minimum, so the size of the reinforcement number doesn't matter. Also in general the AI size only has a relatively small effect on scaling. A change of 5k is so small that it might as well be 0. It's when it starts to build up by 30-40k+ over the minimum that it starts having noticeable affects.

If a unit is exhausted, morale is capped at 50%(steady). If you have a negative penalty to morale from reputation, this reduces your morale stat and also your morale cap in battle. This can result in a unit being stuck at wavering for an extended period. Are you sure your condition isn't going up at all over time? Are you continuing to fire and reload while you wait? Or is the unit actually resting? Especially for snipers with long reload time weapons you can wear them out relatively quickly if you are firing and moving constantly. Multiple players have commented on crampton's gap, so an extra 30 minutes is getting added to that battle in the next patch. You can increase the timerRecommendedMultiplier to 1.2 to replicate this until the patch comes out. I'm not sure what you'd need to set the endofDayMultiplier to exactly, but maybe try 1.05.