Closed breadbyte closed 4 months ago
The issue here is that we cache MCC's executable for the scripting system. When updating the MCC version, the cache is not updated. We just check if the executable already exists in the temp folder, and trying to fetch a new library that didn't exist in the previous version (Sentry in this case), returns an error since it doesn't exist in the cached version.
A temporary fix is to clear the user's temp folder (as that's where MCC's scripting cache is located). Ideally we would re-cache the executable when MCC is updated.
Discussed in https://github.com/MCCTeam/Minecraft-Console-Client/discussions/2753