STS2CombatLogMod

##Features##

• In-combat log - on the left side of the screen, should be right above the energy that you have left. You can use + or - to expand or shrink the log size or use the Hide button to put it away.
• Post-game stats screen - At the end of a run, a button appears on the right side of the screen that lets you open up a scoreboard for the run with tabs for: Overview, Cards, Orbs, Relics.
• Run history stats - If you view past run history in the Compendium, your runs will actually have their endgame scoreboard be viewable (for runs that you have done since adding this mod!!)
• New current run, current combat, and past combats this run! See which cards performed well throughout the entire run instead of just at the end.

##Multiplayer##

• This does work in multiplayer!
• Differentiates per player stats, has stat comparison, and the log splits out by Steam username.
• I am still doing further testing, bug reports would be appreciated

##Usage notes##

⚠ Important: Save File Info

The game uses separate save files for modded and unmodded play:

• Unmodded: %APPDATA%\SlayTheSpire2\steam\<STEAM_ID>\profile1\saves\
• Modded: %APPDATA%\SlayTheSpire2\steam\<STEAM_ID>\modded\profile1\saves\
(quick copy paste: %APPDATA%\SlayTheSpire2\steam\)
If this is your first time installing a mod, your progress won't carry
over automatically. To fix this, simply copy your save files from the
unmodded folder to the modded folder. Make sure to copy (not move) so
you have a backup.

Logs - If you need to send logs to the dev team, they are saved in %APPDATA%\Roaming\SlayTheSpire2\steam\<STEAM_ID>\modded\profile1\ for the latest run and %APPDATA%\Roaming\SlayTheSpire2\steam\<STEAM_ID>\modded\profile1\history\ for long term storage. It uses STS2's naming convention so save files are prefixed with the timestamp that the run began.
%APPDATA%\Roaming\SlayTheSpire2\logs\godot.log can also be sent to the dev team if you experienced a game crash you think is related to this mod. Some basic identifying information is in the godot.log like your computer name, hardware, and install path. Send at your discretion. (combat_log.txt and combat_log_ui_verbose.txt both do not contain identifying information!)

##Installation##

1. Go to your STS2 install directory:
STEAM\steamapps\common\Slay the Spire 2\

2. Create a folder called "mods" if it doesn't exist.

3. Choose your version and extract into that folder:

Full version:
mods\STS2CombatLogMod\STS2CombatLogMod.dll
mods\STS2CombatLogMod\STS2CombatLogMod.json

4. Launch the game — it will detect the mod and ask you to restart in modded mode.

Please read the save file info above since STS2 uses separate saves for modded
and unmodded. If you want your progress to carry over, copy it as
described.

###CURRENT BUGS###
If the host disconnects and auto reconnects before it exits to the home screen, the in-battle log looks weird but fixes itself when the next combat starts

I do most of my testing in single player using my AutoSlay mod (https://www.nexusmods.com/slaythespire2/mods/216). If anything multiplayer feels off or wrong, please submit a post/issue with the combat_log.txt and/or the combat_log_ui_verbose.txt if you would. (These log files have no identifying information)

Future features:
Healing received - added 1.6.0 - some values show as Unknown, working to resolve
Cards played/drawn/discarded/exhausted - added 1.6.0
orb passive vs evoked - added 1.6.0
block sources - added 1.6.0
relic trigger counts - added 1.6.0
status effects applied tracker - added 1.6.0 - some values show as Unknown, working to resolve
percent damage contribution - transforming into interactive graphs, later version
damage taken from enemies - not sure on this one
per player comparison in selected combats instead of just overall run - added in 1.6.0. All tabs are local player and the Per Player tab is the whole team
Simplified view