- Reinstated the original version checker to maintain compatibility.
- Reworked the export approach: the new export method and the legacy one are now split rather than merged.
- Patch‑note data is handled separately, as seen in the example structure at resources.json (e.g. https://github.com/MrNewb/patchnotes/blob/main/resources.json).
- Minimized variable passing by leveraging JSON template references directly, reducing redundancy.
- Added CompareVersions function for accurate semantic version comparison.
- Refactored patch notes fetching into fetchPatchNotes, supporting both GitHub and Tebex sources.
- Improved error handling for invalid repository formats and missing version metadata.
- Enhanced update notification logic to use latest GitHub release and display patch notes for newer versions.
- Now triggers version check on resource start using updated logic.
- Fully backwards compatible
I have been getting tickets/dms when the api is down, to prevent this I have just disabled the failure portion. This isnt ideal but I dont see alerting a server owner the api is down as a solution either.
---Pass a github username and repo name to check for the latest version of the resource.
---
---
---Tebex is a optional boolean to determine if the message should be for a escrowed resource or not.
---
---
---Example Version.VersionChecker("The-Order-Of-The-Sacred-Framework/community_bridge")
---@param repoPath string
---@param tebex boolean | nil
---@return nil
MrNewb