Is your feature request related to a problem? Please describe.
I'm often frustrated when my ship is destroyed via a soft death (e.g., the ship is disabled or critically damaged), and I can't tell which player caused it. The current version of the SC-Kill-Monitor only shows the final killer after my character dies, but not the one responsible for disabling my ship.
Describe the solution you'd like
I would like SC-Kill-Monitor to detect and display the player who caused a soft death event to my ship. Ideally, this would include parsing the game.log for critical damage events, ship disablement logs, or similar indicators before the actual kill occurs — specifically related to ship combat situations.
Describe alternatives you've considered
I have considered manually scanning the logs myself for relevant combat or damage entries, but this is time-consuming and unreliable. Another option might be using third-party recording tools to review engagements, but that doesn't integrate with the monitoring workflow provided by this tool.
Additional context
This feature would be especially helpful for tracking ship combat dynamics and identifying griefers or stream snipers even if they don’t land the final killing blow. It would also be useful for analyzing PvP engagements more thoroughly.
Is your feature request related to a problem? Please describe.
I'm often frustrated when my ship is destroyed via a soft death (e.g., the ship is disabled or critically damaged), and I can't tell which player caused it. The current version of the SC-Kill-Monitor only shows the final killer after my character dies, but not the one responsible for disabling my ship.
Describe the solution you'd like
I would like SC-Kill-Monitor to detect and display the player who caused a soft death event to my ship. Ideally, this would include parsing the game.log for critical damage events, ship disablement logs, or similar indicators before the actual kill occurs — specifically related to ship combat situations.
Describe alternatives you've considered
I have considered manually scanning the logs myself for relevant combat or damage entries, but this is time-consuming and unreliable. Another option might be using third-party recording tools to review engagements, but that doesn't integrate with the monitoring workflow provided by this tool.
Additional context
This feature would be especially helpful for tracking ship combat dynamics and identifying griefers or stream snipers even if they don’t land the final killing blow. It would also be useful for analyzing PvP engagements more thoroughly.