SAC

DM me: - the modded ambientgangs file - ModManager.log, vfs.log (from the RDR2 root directory)

No, it goes into lml\PedExpressBySAC\PedExpress after you unpack the mod I've provided you above, however... of course it would conflict, Ambient gangs introduces new models and updates the sandboxing by updating the same file. So, in this case, forget PedExpress and modify the ambient gangs file direcly (which, if I read it right, should be in \lml\Ambient Gang - RDR1 Gang). This way you are effectively creating what we've called a "merged patch" in FO4/Skyrim, i.e. two mods coexisting even though they affect the same file. Backup the AG file in advance, keep in mind that updating Ambient gangs will overwrite your modded file, so back it up while you work on it. You can use https://www.xmlvalidation.com/ to make sure you are not introducing errors - upload the file after you mod it and it will tell you if you have structural issues.

New in 1.0.4 introduced a minimum sandboxing interval per ped, should help improve performance fixed auto-spawn chances overall logic optimization to minimize inefficient validations and help performance improvement slightly updated sandbox scenario list, eliminated scenarios which require props such as seats pariah events have their own dedicated ini settings (enable, minimum recurrence interval, chance of occurring)

This it the item (model) you want to insert. Notice it starts with <Item>, closes with </Item> ( / is for closing) and inserts what between them. Where you add it is up to your own testing, what I've posted is some examples of proper placing where it would have a noticeable impact.

Yes, I did some changes and was asking if it feels more balanced now. I think I'll add in the bunch of quasi-hillbillies from Rhodes. Install the mod I've attached earlier, edit ambientpedmodelsets.meta, search for "val_", find the relevant female Valentine Town model sets, add the rough traveler, see if they spawn and sandbox <Item type="CAmbientModelSet"> <Name>VAL_TOWN_FEMALE_FANCY</Name> <Models> <Item> <Name>A_F_M_ValTownfolk_01</Name> <Variations type="NULL" /> <Probability value="1.000000" /> <TimeOfDay /> <InventoryInfoHash /> </Item> <!-- ^^ this is the original entry --> <Item> <Name>a_f_m_roughtravellers_01</Name> <Variations type="NULL" /> <Probability value="1.000000" /> <TimeOfDay /> <InventoryInfoHash /> </Item> <!-- ^^ this is added --> </Models> <SpawnDistance value="100.000000" /> <AIMemoryGroup>VALENTINE_RESIDENTS</AIMemoryGroup> </Item> <!-- ... --> <Item type="CAmbientModelSet"> <Name>VAL_TOWN_FEMALE_POOR</Name> <Models> <Item> <!-- SAC --> <Name>a_f_m_roughtravellers_01</Name> <Variations type="NULL" /> <Probability value="1.000000" /> <TimeOfDay /> <InventoryInfoHash /> </Item> <Item> <Name>A_F_M_ValTownfolk_01</Name> <Variations type="NULL" /> <Probability value="1.000000" /> <TimeOfDay /> <InventoryInfoHash /> </Item> </Models> <SpawnDistance value="100.000000" /> <AIMemoryGroup>VALENTINE_RESIDENTS</AIMemoryGroup> </Item> <!-- ... other relevant model sets -->

Please test these (overwrite the initial ones) and let me know if they provide a better balance for males in Valentine (it's a balance test for males that I've done for Valentine only for the moment). a_m_m_valtownfolk_02.ymt a_m_m_valfarmer_01.ymt a_m_m_vallaborer_01.ymt a_m_m_valtownfolk_01.ymt

Failing is part of the process. I've failed dozens (hundreds) of attempts to do various stuff, depending of the complexity, a lot of which due to the fact we are doing this partially in blind for lack of documentation, another lot due to sheer incompetence until I've learnt better. You cannot do permanent damage (the game saves are not persistent enough to do so), just give it a shot, see what happens. Worst case scenario, you delete the mod. (btw, speaking of failing, my example above is failed due to the fact females, or at least NPC females don't seem to have animations for piano playing, meaning they just stand around the piano with a blank look on their faces... oh well, notch another fail)

I'm not sure about riding horses, has not been a focus for me. There is this ambientpedmodelsets.metafile where you can specify which models go into which "ambient model set" which is linked to a specific set of sandboxing scenarios. For example, I have added "abs" (Annesburg) females (the mining town) to be eligible piano players in Valentine. Which makes no sense until you factor in my other mod which spawns various females (including "abs") around the player, so you eventually do get "abs" females into Valentine and I want them to be able to sandbox as much as possible. <Item type="CAmbientModelSet"> <Name>VAL_PIANO_PLAYER</Name> <Models> <Item> <!-- SAC --> <Name>a_f_m_asbtownfolk_01</Name> <Variations type="NULL" /> <Probability value="1.000000" /> <TimeOfDay /> <InventoryInfoHash /> </Item> You can play with the file and use this barebone LML mod to get it into the game: PedExpressBySAC.rar (replace the payload file with your modded one). Search for <!-- SAC --> to see where I made additions, for now I am testing Valentine only to figure out how the system works). Please note that adding models into model sets also makes those models eligible spawns - in this case, you will get Annesburg females spawning as piano players in Valentine, not just sandboxing just in case they are there. Which is something I wish I knew before messing with the ymts to mix up population, but this feature is something I've learnt a few days ago. This does not mean females will be able to perform all the male scenarios (far from it) because there are no female animations for that scenario - e.g. you cannot make females carry timber because there is no female animation for that, only male. I don't have a solution for that, I've tried making a female model to use a male skeleton but that did not go pretty. But some activities are accessible, I'm sure I've seen females driving carts around Valentine - riding, I don't know, haven't seen them, but that can also mean I need to add them into a different "model set" (e.g. "cowboys", Idk) Give me some examples of what you mean by "models". Due to reasons that escape me, RDR uses different skeletons for the unique characters, which means that haircuts or clothes that fit unique characters cannot be worn by vanilla NPC skeletons. This is also why the player cannot wear NPC clothes, mismatched skeletons. But mashing up some models can be achieved the same way I did this mod, as long as the skeletons are compatible.

Correct Partially There is, but not an easy one. Each of the main ymts (a_x_m_xxx_towfolk, laborers and some others) contain around 30-50 models each, in vanilla, plus those added by me (the ones you are seeing as "new"). I need to go through each of the lists and remove some in order to rebalance. Not easy, not fast. On top of that, the game seems to have a weird (or unknown to me) randomization engine. Meaning if you have two sets of models in an ymt (vanilla plus others added), if they are not interlaced in the files (and they aren't) it will pick a number of random NPCs from one "block", then switch to the other and pick another number of randoms. It doesn't seem to do real randomization, or at least I don't understand the methodology. So yeah, whenever I get the time and the disposition I take one of the population files and go through each model, remove some, clone some, mashup some others, but there is no set calendar.

What's New in Version 1.0.3 See changelog - fixed a coding error causing the scenarios and scenario points to not trigger for NPC sandboxing - more safeguards implemented to prevent possible crashes when (auto-)spawning new peds Can use the ini from 1.0.2 if previously downloaded / configured, no new ini controls have been added in 1.0.3

What's New in Version 1.0.2 See changelog - (important) fixed a potential crash when calling "lobotomize" on the same ped twice, please make sure to update the mod if you have downloaded the previous version - added ini toggle for previously un-documented "mute player" function - added ini toggle for previously un-documented "flee horse" function

Pool of female models Pool of random scenarios