......... 🕓 🕗 🕛 .........
InediaInfectedAI v1.20
The mod has been updated.
......... 🕓 🕗 🕛 .........
https://github.com/ysaroka/InediaInfectedAI/wiki/PatchNotes_1.20

......... 🕓 🕗 🕛 .........
InediaInfectedAI v1.19
The mod has been updated.
......... 🕓 🕗 🕛 .........
https://github.com/ysaroka/InediaInfectedAI/wiki/PatchNotes_1.19

......... 🕓 🕗 🕛 .........
InediaInfectedAI v1.18
The mod has been updated.
......... 🕓 🕗 🕛 .........
https://github.com/ysaroka/InediaInfectedAI/wiki/PatchNotes_1.18

......... 🕓 🕗 🕛 .........
InediaInfectedAI v1.17
The mod has been updated.
......... 🕓 🕗 🕛 .........
The main addition is new types of injuries in the pain system.
Now, in addition to fractures, characters can suffer deep wounds, bullet wounds, and internal bleeding:
https://github.com/ysaroka/InediaInfectedAI/wiki/Inedia-Pain-system-guide
Visual guides:
- EN: https://github.com/ysaroka/InediaInfectedAI/wiki/Inedia-Pain-System-Visual-Guide-EN
- RU: https://github.com/ysaroka/InediaInfectedAI/wiki/Inedia-Pain-System-Visual-Guide-RU

A medical system has also been introduced, including a variety of pre-made medications and medical tools, as well as the ability to attribute these properties to any item you choose:
https://github.com/ysaroka/InediaInfectedAI/wiki/Inedia-Medicine-guide

More detailed information is available in the patch notes:
https://github.com/ysaroka/InediaInfectedAI/wiki/PatchNotes_1.17

---------------- 🕓 🕗 🕛 ----------------
InediaInfectedAI v1.16
The mod has been updated.
---------------- 🕓 🕗 🕛 ----------------
⚠️ HOTFIX ⚠️
Fixed a bug where the character's blood volume was fully restored upon taking any damage.

---------------- 🕓 🕗 🕛 ----------------
InediaInfectedAI v1.16
The mod has been updated.
---------------- 🕓 🕗 🕛 ----------------
⚠️ HOTFIX ⚠️
The issue causing the server crash when the mod was used with "eAI_Reloaded" mod has been fixed.

---------------- 🕓 🕗 🕛 ----------------
InediaInfectedAI v1.16
The mod has been updated.
---------------- 🕓 🕗 🕛 ----------------
⚠️ HOTFIX ⚠️
The damage handler for survivors is disabled for "DayZ-Expansion-AI" bots that have modified damage multipliers (DamageReceivedMultiplier != 1 or DamageMultiplier != 1) in ExpansionMod\Settings\AISettings.json or in quest objectives Quests/Objectives/(AICamp or AIPatrol).

The issue was that if these parameters were set to values other than "1", both "InediaInfectedAI" and "DayZ-Expansion-AI" would control damage from and to such bots simultaneously, causing a conflict that prevented killed bots from being counted in "DayZ-Expansion-Quests" objectives.

Now, if the "DamageReceivedMultiplier" parameter is set to a value other than "1", damage from the player to these bots will be processed by "DayZ-Expansion-AI", not "InediaInfectedAI". This means that weapon multipliers ("Zombies.DamageToZombieWeaponsMultipliers") and melee damage multipliers from injured hands will no longer apply to these bots. If "DamageMultiplier" is set to a value other than "1", damage to the player from such bots will be handled by "DayZ-Expansion-AI", meaning that damage multipliers will not apply to bot damage to the player.

https://github.com/ysaroka/InediaInfectedAI/wiki/PatchNotes_1.16

---------------- 🕓 🕗 🕛 ----------------
InediaInfectedAI v1.15
The mod has been updated.
---------------- 🕓 🕗 🕛 ----------------
⚠️ HOTFIX ⚠️
The synchronization of the player's configuration variables has been reworked through RPC, without using the functionality "PlayerBase.RegisterNetSyncVariable*()", as this functionality has a limitation on the number of registered variables, leading to various issues such as disappearing sounds, etc.
With this hotfix, I removed about 20 variables synchronized in this way, which should reduce the likelihood of such problems occurring.

---------------- 🕓 🕗 🕛 ----------------
InediaInfectedAI v1.15
The mod has been updated.
---------------- 🕓 🕗 🕛 ----------------
⚠️ HOTFIX ⚠️
For action "ActionSearchZombieBodyToViewCargo", the setting "IsLockTargetOnUse" has been disabled, as it could potentially cause issues. Although I did not encounter these issues in my tests, I disabled it just in case.