Lordfirespeed
commented
2 months ago I intended for this repository to be able to manage the reference assemblies for a whole host of games, i.e. automating the process with little need for intervention.
however, I ran into a few issues -
- License requirements (I use a steam account to power the workflows, and that account needs a game license for the workflow to work)
- Steam concurrency limitations (at most 8 active sessions)
I would be happy to overcome the former issue by purchasing licenses, but the latter issue dissuades me from doing so.
Hi! I'm a developer interested in publishing reference assemblies for our game (Phantom Brigade) on NuGet. We have a mod system and code modding support (through Harmony 2 patching and loading .dlls from mod folders, similar to Oxygen Not Included), but making code mods always involved a local install of the game and directly referencing its assemblies.
Some folks in our modding community brought the idea of the reference assembly package to my attention and this sounds like a great way to make code modding easier. I wasn't familiar with this approach before and was pointed to this repository as a source of some reference assemblies for games like Content Warning.
The workflow you set up sounds great! However, I'm not entirely familiar with the tools involved, so I'm not sure how to make use of it to publish the reference assemblies from our game. Is this a repository only used by you through your personal Steam library installs, a repository intended to be checked out by other people as is (with other people installing games into a local subfolder and some sort of an intended workflow for manual local builds and PRs), or a template repository intended to be forked into a new GitHub project and modified by different game developers to automate publishing for one game at a time?
If you have a moment to reply, I'd appreciate any info! Apologies if this was already covered elsewhere!