PATCH v3.1.6 (Fixed ValorantCC not opening when Riot client is not running)

• This is a hotfix for v3.1.5

MINOR v3.1.4 (Rewrite Attempt+Features)

- Reverted rending
- Added offset for community profiles.
- First Processor.cs rewrite attempt.

Stuff might be buggy but deal with it for now as I am looking for better ways of implementing stuff.

PATCH v3.0.4 (Temporarily Disabled sharing and profile change listener)

PATCH v3.0.4 (Temporarily Disabled sharing and profile change listener)

Due to the Firebase's limitations, We temporarily put our backend to maintenance. This caused ValorantCC's request to fail and close itself.
This patch disabled all vTools API related temporarily while everything is being fixed.

PATCH v3.0.3 (Null handling fix)

For some reason, There are null objects on community profiles.

• Added some null handling.
• 3rd attempt to fix the single crosshair profile issue.

PATCH v3.0.2 (Re-Fixed Single crosshair profile Error)

PATCH v3.0.2 (Re-Fixed Single crosshair profile Error)

PATCH v3.0.1 (Force Login added)

• Added a button to force login for those who have problems with Riot Client Logs, have to wait for 20 seconds for the button to appear after login on Valorant

MAJOR v3.0.0 (UI Changes and New Features)

New Features

• Community Profiles List
• Profile Sharing
• Hide/Public Listed profile.

Improved

• API Backend
• Authentication
• Main Window Design
• MessageBox Window
• Compatibility
• Updater
• Logging
• Performance
• Stability

This update should lessen the bugs and allows users (Targeting those who uses windows themes) to use even under cases like this.
For issues, Please open an issue here or join our Discord so we can help you fix it.

PATCH v2.6.10 (Haruki Fixed a huge future problem)

PATCH v2.6.10 (Fixed a huge future problem thanks to Haruki)

PATCH v2.6.9 (Unauthorized Access error handled; 2.6.8's Crash fix.)

• Shows a message box if user used ValorantCC in Admin folder and asks whether to run as admin or just move to other folder.
• Admin rights no longer required (Unless if ValorantCC is in an Admin folder.)

Skipped 2.6.8's release as 2.6.8 commit has a lot of logged-only errors. so we decided to create a new tag with the fixes of 2.6.8's newly surfaced bugs so users are not required to download/update twice.

Explanation on the Crashing error. After 2.6.8's fix. The newly surfaced bug was the lack of access error. 2.6.7 removed the Admin access and that caused some updating problem. This release checks if write access is granted before updating so unknown error should be less than what it should be.

PATCH v2.6.7 (Added more logging specifically for app crashes.)

• Added Stacktraces for logging on App start
• Removed Admin privilege (was used before)