-
Notifications
You must be signed in to change notification settings - Fork 740
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
All Optional Modules on Steam Workshop #7834
Comments
I am no lawyer, but from our side, you can re-upload as much as you want to as long as you make it clear it's not official. :) Many units do that. Managing multiple optionals gets tedious, that's why we only keep it to the most popular ones. |
@jonpas Is your deployment system (pushing to Steam Workshop) entirely manual then? I see that you're already using GitHub Workflows/Actions for the build/release; it wouldn't be too difficult to add an automatic publish to Steam Workshop to that workflow (automatically publishing each optional module as well). I'd be happy to help with that if you like. |
No, Automatic publish from GitHub directly doesn't help until you have a full binarized build on that system. |
Got it. So after creating the initial publish manually and the IDs to the build/deploy config, is it any extra work to maintain? It would sure be a massive help to a lot of us who rely on workshop templates. |
There are a lot of optionals, we are thinking of leaving many of them "Unlisted" on the workshop so they don't cause too much clutter. But anyone would still be able to see and subscribe via the url (which would be published somewhere) |
Works for me. Perhaps on the Wiki page for each optional, you can add the URL to it in the Workshop. |
Is your enhancement related to a problem?
I think this is a pretty common one. Our community wants to use several of the optional modules for our events. We use Steam Workshop with HTML templates for importing the mod configuration. Since enabling optional modules requires manually moving those folders from the
optionals
directory to the main install directory, this makes it much harder to use Steam (has to be re-done by each player with each new release).Solution you'd like:
Similarly to how you have the various compat optionals (e.g. RHS compat) as separate releases on Steam Workshop, I would like the other optional modules (noactionmenu, nocrosshair, particles, etc.) to also be separate releases that can be specified in an HTML template.
Alternatives you've considered:
Re-packaging ACE3 with optional PBOs copied into the main
addons
directory, but we can't publish that on Steam Workshop without violating the TOS.Additional context:
The need for this is already known, since it's already done with the RHS compat optionals, so I'd be surprised to see opposition to this.
The text was updated successfully, but these errors were encountered: