Is your feature request related to a problem? Please describe.
Yes, my current problem is that I am having some dependency conflict issues with the TSAPI package where for some reason Visual Studio keeps force referencing my more up-to-date version of TShockAPI.dll to the published Nuget version instead, and if I could just update the package it would save me a lot of trouble. The change made to TSPlayer.GodMode some time ago is breaking all my code because the runtime sees it as a property and the compiler sees it as a field. Basically, building it myself and referencing it as a dll is giving me issues due to transitive dependencies and it would be easier to just sidestep this.
Describe the solution you'd like
Long term a continuously published version each time a PR is submitted would be nice. As a short term solution, a one-off manual publishing of a new version would suffice.
Describe alternatives you've considered
If this doesn't happen soon, I could have direct dll references in my project and purge any TShock Nuget references, but that would certainly defeat the point of having the Nuget package at all, and I worry that I'd still have to clear the Nuget cache to get it to reference the right thing. Other developers are on my project and I wouldn't want to have to ask them to take some extra step to fix their workspace.
Is your feature request related to a problem? Please describe. Yes, my current problem is that I am having some dependency conflict issues with the TSAPI package where for some reason Visual Studio keeps force referencing my more up-to-date version of TShockAPI.dll to the published Nuget version instead, and if I could just update the package it would save me a lot of trouble. The change made to TSPlayer.GodMode some time ago is breaking all my code because the runtime sees it as a property and the compiler sees it as a field. Basically, building it myself and referencing it as a dll is giving me issues due to transitive dependencies and it would be easier to just sidestep this.
Describe the solution you'd like Long term a continuously published version each time a PR is submitted would be nice. As a short term solution, a one-off manual publishing of a new version would suffice.
Describe alternatives you've considered If this doesn't happen soon, I could have direct dll references in my project and purge any TShock Nuget references, but that would certainly defeat the point of having the Nuget package at all, and I worry that I'd still have to clear the Nuget cache to get it to reference the right thing. Other developers are on my project and I wouldn't want to have to ask them to take some extra step to fix their workspace.