-
Notifications
You must be signed in to change notification settings - Fork 0
Home
Star Trek Online Combat Analyzer began as a project to squelch extreme boredom. I had seen videos and various blurbs from other STO players using combat parsers. I was curious, so after a little research, I found the following reddit post concerning the STO combat log file. Reddit Link
It started as a small research project in April 2024, and it's become an app I use constantly to explore my adventures in STO.
Feel free to download and play with the app. See the Installer section if you're interested.
I've done quite a bit to document the application here on the wiki. If you can't find what you're look for here on the wiki, feel free to check out Github discussions for this project. Feel free to pop in to peruse or ask your questions.
Note: This is a personal project, and I work full-time. Please keep this in mind when hitting up discussions. It might be a few hours or longer before I reply.
The installer uses Click-Once technology. This means you should only have to download and install this app once.
Thanks to Click-Once technology, the app checks with the server each time it's launched, and gives the user the option to automatically download and update the app in the background. This saves the user from constantly having to manually download and install newer versions.
Notes:
- The installer is signed with a test certificate, so Windows will pop up warnings about the installer not be trusted.
- If you don't have the .NET 8 runtime installed, it will install it for you.
.NET 8 runtime
After successfully building the app from source, or downloading and installed it from above, do the following to get started using the app.
-
Start the application
-
Under the Settings tab, set the following settings:
-
CombatLogPath: Set this to match the STO log folder on your local machine.
- If you click the select button, a folder select dialog will appear to help you select a folder.
- If you click the detect button, the application will attempt to get the STO install folder from the windows registry. A dialog box will appear to let you know if it was successful, and will update the field with the STO log folder if it was.
-
CombatLogPathFilePattern: Set a file pattern used to select one or more combat log files.
- This search pattern supports wildcards, so you can set this to return more then one file.
-
(Optional) MyCharacter: An identifier used to select a player when a new combat instance is chosen.
- This comes in handy when browsing through multiple combat instances via the Combat List dropdown. For example, I have mine set to @zxeltor so it will pick all of my characters, instead of specific character.
-
(Optional) HowFarBackForCombat: How far back in hours to pull combat log data.
- Note: Setting this parameter can reduce the time the application takes to parse the STO combat log file(s).
-
(Optional) PurgeCombatLogs: Enable combat log folder purge at application startup.
- Note: If only one combat log exists, it won't be purged regardless of how old it is.
- (Optional) Purge Now button: You can click this button to trigger the purge of you log folder.
- Note: This works regardless of PurgeCombatLogs being enabled, but will use HowLongToKeepLogs to determine what to purge.
- (Conditional) HowLongToKeepLogs: How long to keep logs in days, before they are purged.
-
(Optional) DebugLogging: Enables debug logging. This also enables/disables a few information dialogs in the UI.
- Open Log File: This button attempts to open the log file for the application in your default text file viewer/editor.
-
(Optional) DetectionsSettingsVisibleInUi: This is an experimental feature. This makes the Detection Setting Editor tab in the UI visible.
- See the wiki page concerning this feature Map Detection Settings
-
(Optional) CombinePets: By default, the application will display each unique pet by it's GameId. This can clutter the pet only display option in the UI. If this is enabled, it groups pets with the same label/type.
-
(Optional) DisplayParseResults: If enabled, a dialog will appear after the Parse Logs button is clicked in the UI, and will display results on what files were parsed and other stats.
-
(Optional) EnableInactiveTimeAdjustments: If enabled, the application will attempt to detect Inactive time(s) for a Player. Inactive time(s) are displayed in the UI, and will be used to adjust DPS and HPS values.
- (Conditional) MinDelayInSecondsBeforeInactive: A Player needs to be inactive for this many seconds, before a timespan can be marked as Inactive. Inactive means the user was in combat, and not attacking.
-
-
Switch to the Log File Analyzer tab:
-
Click the "Parse Log(s)" button. This parses the STO combat logs. If a failure occurs, there should be details on what to do.
-
After a successful parse, you can choose a combat instance from the Combat Select dropdown.
-
If all goes well, you should see something similar to what's displayed in Figure 1.
Figure 1: What the UI looks like after a successful parse, and a combat instance was selected in the Combat List dropdown.
Figure 2: The tools and settings tab
Figure 3: Detection Settings Editor tab
Figure 4: The about tab