Second Heart Universal Fix

Second Heart Universal Fix

Sometimes after respawning with the Second Heart implant, combat mode would get stuck and the game would stop responding to inventory calls, the map, the menu exit button, etc. This fix removes the main problems caused by this bug:

游戏玩法

[b]Description[/b]
Sometimes after respawning with the Second Heart cyberware, combat mode would get stuck and the game would stop responding to inventory calls, the map, the menu exit button, etc. This fix removes the main problems caused by this bug: inventory, map, and menu exit start working again. The character also exits combat mode (the red frame around the minimap disappears). However, this fix doesn't work perfectly — it doesn't restore combat behavior to its original state. The red frame around the minimap no longer appears even if combat is actually ongoing or starts again — the game's behavior will stay the same, just without the red frame. If combat has actually ended, you can save again, use fast travel points, etc., but you won't have the red frame notifying you of combat mode. Combat mode becomes invisible. But there are upsides too: now during combat, after respawning with the implant, you'll be able to craft ammo and switch quickhacks on your deck — so it's not a bug, it's a feature :) Either way, this fix removes the main problems with the implant, and you can play comfortably with it. After loading a save, everything will return to normal.

[b]Installation Instructions[/b]
Place the folder into the game's root directory: "./Cyberpunk 2077"

Update 1.3
Fixed some compilation errors to improve compatibility with other mods. Thanks, flibdev :)
Update 1.2
I've improved compatibility with [url=https://www.nexusmods.com/cyberpunk2077/mods/14515]Walk by Default 2.0[/url]; compatibility with other mods will likely improve automatically as well. If you notice that this fix conflicts with any of your installed mods, please let me know in the discussion thread so I can figure out how to make them work together. 
Thank you, Romulus30, for reporting the incompatibility and for testing the new version :)