Closed FreedomFaighter closed 2 months ago
Thanks for the PR! However, there is a reason why WebsocketSharp is not used as a package, and Triggernometry tries to use as few packages as possible. ACT loads assemblies only once, and the version that gets loaded depends on which plugin gets loaded first. That can cause ACT to load a version of an assembly which may conflict with other ACT plugins if they happen to reference other versions, and that can cause assembly version hell.
WebsocketSharp is also a repository have you considered submoduling the same version that align on the commit information that is custom to your plugin
Yeah that's probably a good idea, will look into it
Create build-plugin.yml
Revert "websocketsharp as nuget package"
This reverts commit f937ec1c53b727d374e6434acfbeeb194de02e6b.
websocketsharp as nuget package
readded websocketsharp loose files
updated project file with relative path to Program Files x86 directory
readded mathparser
Create build-plugin-and-release-on-tag.yml
removed mathparser for the package from nuget
added websocket-sharp package
removed files brought in by package