Repository navigation
PatchNotes_1.10
☑️ 1) Possibly, the issue with saving the player's pain system states after respawn has been fixed. But this is not certain, as the problem is not with InediaPain, but with some mod that affects the respawn process.
Sometimes, possibly due to mods affecting the player respawn process or server issues during restarts, the Inedia debuffs persist on players after death and respawn.
This happens because the server apparently either calls PlayerBase.OnStoreLoad(...) for newly respawned players - loading old data (which it shouldn’t do during respawn), or it doesn’t recreate the PlayerBase object after a player’s death and instead uses the old one with outdated data (which, apparently, it also shouldn’t do).
The issue occurs extremely rarely and most likely only on servers with some mod affecting the player respawn process. Therefore, reproducing it intentionally or identifying which mod causes it is practically impossible. There were several attempts to fix this issue blindly, but they ultimately failed.
This fix is intended to definitively solve the problem. It adds proper clearing of the Inedia debuffs directly in the on-disk storage immediately after the player’s death (the PlayerBase.EEKilled(...) event). This way, even if the server is broken or some mod interferes with the respawn process and the server decides to execute PlayerBase.OnStoreLoad(...) during the player’s respawn, it will in any case load already cleared data, and everything will be fine. Additionally, just in case (you never know, some crazy mod might monopolize PlayerBase.EEKilled(...)), clearing of the debuffs was also added during the player respawn event (MissionServer.OnClientNewEvent(...)). This is a rock-solid solution that should resolve the problem once and for all.
Users who have encountered similar issues are advised to monitor whether they occur after this update.
If, for some reason, the issue persists, there is little I can do in this case. You will need to investigate which mod interferes with the PlayerBase.EEKilled(...) or MissionServer.OnClientNewEvent(...) events, or why they are not being called correctly on your server, and resolve the problem yourself, as it is not related to InediaPain mod.
But it behaves very strangely.
Pain and fractures are based on the global Shock damage received in PlayerBase.EEHitBy(...), and there are no issues with them - the Shock damage is applied and everything works as intended, the player receives both pain and fractures.
However, for deep wounds/bullet wounds to work, a specific body zone of the player needs to receive Blood damage. For some reason, Blood damage for a specific zone from these bots is not being applied - it is 0 (i.e. damageResult.GetDamage(dmgZone, "Blood") == 0). As a result, deep wounds and bullet wounds will not work.
For everything to work correctly, PlayerBase.ProcessDirectDamage(...) must be called for the player zone that was hit, with the ammo Blood damage set to 100 for bullets, since the chance of getting a deep wound is calculated based on this value. In this case, when the correct zone is passed, the vanilla engine will automatically calculate damage reduction depending on the armor associated with that zone, and PlayerBase.EEHitBy(...) will receive the correct Blood damage value taking armor into account (as well as other damage types).
To summarize, I don’t know how these bots are implemented - but on my side I added support for processing their damage. However, for the full Inedia Pain System to work correctly, changes are required on the "AI Bandits" side.
- Added the LimbsBreakIgnoreAmmoList parameter, which allows excluding specific ammo from the fracture mechanic. This solves the issue with weapon types that deal shock damage but should not cause bone fractures (e.g., a taser or any other weapon that deals electrical damage).
- Fixed a bug where the character would receive shock damage when performing kicks while having pain in their arms. Also now, when kicking with pain in the legs, the character will also receive shock damage, and when kicking barefoot, they will receive leg pain damage.
- The bug that allowed Metoclopramide to let the character fill their stomach without limit has been fixed. Now, after taking the drug, the character can still fill their stomach beyond the normal amount, but this value is still capped at 4 liters (the vanilla value is 2 liters), and if it is exceeded, vomiting will still be forcibly triggered.
- Added the ability to disable the LimbsBulletTimeToSecondStageSeconds mechanic by setting this parameter’s value to
-1. - Fixed a minor desynchronization issue with the leaking bandage icon, which caused it to remain visible for 1–2 seconds after a wound was bandaged.
- The swing amplitude of the weapon when experiencing hand pain has been slightly increased.
You can always check what has changed in the Default configuration file, which is updated after each modification update. You can also view the configuration file DIFF between the latest versions here.
- Added stomach content clearing after vomiting, but only when it is caused by Inedia, vanilla triggers remain unchanged. It appears to be an issue or feature of the vanilla game after a certain update. However, in my opinion, it shouldn't work like this: after vomiting, the stomach contents should be emptied instead of continuing to restore food/water values. In vanilla mechanics, the issue is most noticeable when trying to eat or drink more than the stomach can hold. The BI report is here, they might fix it someday.
- Fixed a compatibility issue with
VPPthat prevented Inedia debuffs from being removed when healing the character using the "J" key. - Fixed an issue where phantom gunshot sounds from certain weapons, triggered by head pain, were not being played.
- Now, if the
Inedia Pain Systemtriggers vomiting, its animation will not be queued (only the food/water loss effect will remain). Previously, if a character vomited while inside a vehicle, on a ladder, or while swimming, the animation would be queued and only played after the character finished the current animation, for example, after getting out of the vehicle.