Skip to content

Application Tab: Tools Settings

Jump to bottom
Todd Taylor edited this page Sep 27, 2024 · 11 revisions

Interface Layout

Tools

  • Download Latest Map Detection Settings: You can use this to button to automatically download and import the latest CombatMapDetectionSettings.json file from the STOCombatAnalyzer.Settings repo.

  • Import Map Detection Settings: You can use this to button to manually import the latest CombatMapDetectionSettings.json file from the STOCombatAnalyzer.Settings repo, or from another source.

  • Reset Map Detection Settings: If you manually imported a newer version of the CombatMapDetectionSettings.json file, you can use this button to revert back to the application default.

    • Note: The application default typically gets updated with each new release, with the latest CombatMapDetectionSettings.json file from STOCombatAnalyzer.Settings repo.

  • Export Selected Combat: This button is used to export and JSON representation of a combat instance. This is primarily for troubleshooting purposes.

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.

  • (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.

Figure 1: A screen shot of the Tools/Settings tab. Tools/Settings tab

Clone this wiki locally