HughJanus

As of v1.47 the NPC should go into ragdoll as soon as its health crosses the DyingMovementThreshold - no matter if on horseback or not. It was tested quite thoroughly, so it should work. As for your accuracy suggestion, I will add that to the "to be discussed" list :) The disappearing weapons with switches for on and off and all this little stuff would currently take to much time, we just dont have (we are already removing planned features from v1.48, because we just dont have enough time for testing and polishing). I will keep it on my personal list, though.

@ChrisCrosssss this is already fixed in v1.47 (shooting NPCs off horses). @Adman I will address your points one by one: "[...] disarms can be a little annoying in story mode (and in my advice should be disabled for story mode to avoid quests bugging due to fleeing enemies), [...]" -> You can already disable the disarming in the ini. "[...] In regards to the issue with how bodies glitch when in slow mo menus, would it be possible to disable the time slow effect in menus? Like how it works in multiplayer in realtime? [...]" -> We have looked into it in the past, but havent found a solution back then. Its still on our list, but development has slowed down a little, since we dont have that much free time currently. "[...] A disarm % chance, a variable that randomises the success rate of a disarm. [...]" -> I put it on our todo list. "[...] An accuracy % chance, a variable that randomises each enemies accuracy. [...]" -> How would that work? Ranging from which to which accuracy percentage and how likely are high or low percentages? I wouldnt know which logic to put behind such a randomizer. "[...] Controls over Health/stamina/deadeye restore rate (not the cores, the outside ring). [...]" -> I wouldnt know how to properly influence the rate of the circle filling up without a lot of research (for which I currently dont have time). "[...] Controls over Health/stamina/deadeye core specific drain rates (instead of the one for all). [...]" -> I put it on our todo list. "[...] A variable that controls how often an enemy runs away or attacks with melee after disarmed. [...]" -> I put it on our todo list. "[...] Misfire chance; (for player too if possible) bullets not firing, guns jamming etc, could be based on weapon type/damage. Controls over stamina drain rates, options for drain while crouch walking/running, options for drain while aiming with all weapons, control over bow draw drain etc. Zombie mode; when enabled enemies get back up from the dead once after some delay (after death states). Controls over animal NPCs, like how common they spawn if possible, but also things like how fast they are, how sensitive to noise etc. [...]" -> I wouldnt know how to implement the first two points (without a lot of research). The last two points I dont really see to fit in the scope of this mod. "[...] With the disarms, would it be possible to have them go for the gun? or pull more guns out of nowhere? or make more npcs carry more guns? [...]" -> What we do when disarming is just snatch their weapon and drop it to the ground. Some pull their handguns, some go for melee - its vanilla behavior, we dont task them with anything specific. I suppose you could equip them with a gun, but I dont really find that to be realistic (pulling guns out of nowhere and such). To make them carry more guns (on their belt) we would have to alter the appearance or equipment of the ped models, which we have not done yet and were not planning on doing. "[...] And with the guns that NPCs drop, is it possible to have them deleted or not pick uppable? Also ammo? [...]" -> Not with the ways we tried (we already tried making them non-pickups). What we could do is just let the gun vanish instead of dropping it, but that would look weird, I suppose. Thanks for the suggestions - we are always happy to get some :)

@djap3 Have you tried loading an older savegame and checking if it also happens there? Maybe its really a R* bug.

@djap3 I dont think its caused by PDO, because PDO never explicitly tells an NPC to attack the player. The disarming feature only tells NPCs to put their hands up, cower or flee explicitly. Based on chance, one of those things happens or the script will just let the NPC be as it is - its vanilla reaction then is to attack the player (because he has done damage to the NPC). Also PDO never tells any NPC to get up (only to stay down). So both causes of the above posted problem (getting up, attacking the player) cant be caused by PDO directly. But maybe in combination with another mod, it may - I have no idea. Maybe you have a mod which lets NPCs stay up until a certain amount of health is deducted and PDO gives the NPC more health - so the duelling script maybe puts the NPC down automatically, but since it has more health (thanks to PDO), your other mod tells it to get up. This is an example of how such things could occur, but since I dont know which other mods you have installed and how they work, I cant really tell. I also dont think that a script mod can mess your savegame up (unless it alters something permanent, like trophies you have to earn or so), but as long as they are just affecting minute to minute gameplay, I dont think they will influence your savegames.

I will put it on our list and we will check it out.

@Cuddlecreeper8 The way we currently handle the NPCs is with the method "worldGetAllPeds(container for peds, ped count)". The ped count must be a constant though, because the container for peds has to be initialized with a fixed value and the ped count has to be the same value (so the container has enough space). I dont know how the gunshot wound guy handled it, but we the way we currently do it, we cant put the ped count in the ini to be set by the people themselves 😕

Unfortunately, I wouldnt know what to change. The script just iterates through all the available NPCs and applies certain effects (like stumbling or giving them more health). There is no magic done - just simple commands.

The next big step we want to take is adding proper animations to the dying states (instead of the force pushes, which are our current workaround). But we will only be able to do this with the help of OpenIV. We need to know the animation names to be able to actually use them. Edit: the current version (v1.46) is not this "big step" - we just found a workaround for using these animations, but it is not the desired end result yet.