Oscr-ui

Latest version: v2024.10.12.1

Safety actively analyzes 682251 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 3

2024.9b50

- Fixed Parsing of Log Files that have blank lines in them.
- Temporary Log Files are no longer put in your current working directory.
- OSCR's settings file is no longer put in your current working directory on Linux, but uses QSettings instead to better align with what Linux expects for a config location: https://doc.qt.io/qt-6/qsettings.html#platform-specific-notes
- Windows may incorporate this in the future, however it still currently creates a dotfile at your current working directory.
- Default Time Between Combats is now 45 seconds.
- OBS Can now capture OSCR's Live Parser
![image](https://github.com/user-attachments/assets/ea1606b4-3dae-4eb2-8955-ffe03917eaa2)
- OSCR-UI's Reported Version is now 0.4.


Known Issues

- Multiple-Language Support does not work in the .msi build.

v

2024.8b210

- Added Multiple-Language Support
- Resolved Problems where trim Dialog Box would not Trim Combat Logs properly.
- Added Repair Log Functionality
- Repurposed 'Build' In the League Standings Page to be 'Highest Damage Ability'.
- Added the Ability to view uploaded Combat Logs on oscr.stobuilds.com through the Upload Results Dialog.
- Cleaned Up Error Reporting for the Upload Results Dialog.
- Added Better Difficulty Detection For Maps
- It should no longer be possible to upload Partially Completed ISE runs.
- Added a new Map Difficulty called "Any"
- Partially Completed Logs may be submitted to the Any Difficulty for specific maps. This is to allow us to manually review specific results which were not previously reviewable.


During a migration of these changes to our backend, there was a critical loss of data resulting in all previous combat logs being lost. We are restoring from SCM's database, however any logs not stored on SCM are lost. We are sorry for any inconvenience this has caused and will take additional steps in the future to prevent this from happening.


Known Issues

- OSCR still reports as Version 0.2

2024.07b250

Changes

- Double Clicking a Combat Log will view it.
- Double Clicking a Map on the League Standings Page will now select it.
- Broken Out the League Standings Page to now have two sections.
- The Default League for each map
- Seasonal Leagues for each map
- Damage is now included when copying results to the clipboard.
- Added option to automatically start the Live Parser
- Adjusted the Minimum Window Size to 1280x720.

2024.06b91

UI (OSCR-UI)

- OSCR is now packaged as an MSI installer on Windows.
- Fixed Resizing Scaling on the Live Parser.

![image](https://github.com/STOCD/OSCR-UI/assets/6548135/bb0c6ccc-9b58-4eed-8076-d60fb844b441)

2024.5b271

The wrong tag was created in the previous release. Notes repeated below:

---

UI (OSCR-UI)

- Added UI Scaling
- Changed the "Copy to Clipboard" output to be Discord-friendly (includes backticks to prevent accidental -mentions.
- Resolved a Division by Zero error when trying to plot empty combats.
- Added OSCR Backend Support. 30 31 32
- Added new Upload Confirmation Dialog

Parser (OSCR)

- Removed Display Name from Live Parser

Server (OSCR-server)

- OSCR's backend has reached general availability. Both the site [oscr.stobuilds.com](https://oscr.stobuilds.com/ui/) and backend support in both [OSCR](https://github.com/STOCD/OSCR-UI) and [CLA](https://github.com/AnotherNathan/STO_CombatLogAnalyzer) are now available.

Known Issues

- High End BHE runs will fail to upload due to overkill.

2024.4b131

UI (OSCR-UI)

- Added UI Scaling
- Changed the "Copy to Clipboard" output to be Discord-friendly (includes backticks to prevent accidental -mentions.
- Resolved a Division by Zero error when trying to plot empty combats.
- Added OSCR Backend Support. 30 31 32
- Added new Upload Confirmation Dialog

Parser (OSCR)

- Removed Display Name from Live Parser

Server (OSCR-server)

- OSCR's backend has reached general availability. Both the site [oscr.stobuilds.com](https://oscr.stobuilds.com/ui/) and backend support in both [OSCR](https://github.com/STOCD/OSCR-UI) and [CLA](https://github.com/AnotherNathan/STO_CombatLogAnalyzer) are now available.

Known Issues

- High End BHE runs will fail to upload due to overkill.

Page 1 of 3

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.