Hi @NickFox007, thanks for building and maintaining PlayerSettingsCS2 — persistent per-player preferences shared across plugins is one of those things players never notice until it's missing.
We run a game-server hosting service and would love to offer your libraries through our curated CS2 plugin catalog — unmodified, SHA-256-pinned to your official release ZIPs, always credited and linked back to this repo, and kept up to date for users automatically whenever you publish a new release.
Right now the repository has no LICENSE file, which legally means "all rights reserved" — so redistributing it isn't actually permitted, no matter how clearly the releases are meant to be used. For a shared library this matters more than for a standalone plugin, because it gets shipped alongside every plugin that depends on it. Would you consider adding a license? MIT and GPL-3.0 are the common choices in the CS2/CSSharp plugin ecosystem (GitHub can add the file in two clicks via "Add file → Choose a license template").
We're asking the same question on AnyBaseLibCS2 and MenuManagerCS2 — sorry for the three notifications. A single license decision would cover all three, so please feel free to answer in whichever issue is most convenient and ignore the others.
If you'd rather not, that's completely fine too — we'll simply keep them as manual-install options for our customers. Either way, thanks for your work!
Hi @NickFox007, thanks for building and maintaining PlayerSettingsCS2 — persistent per-player preferences shared across plugins is one of those things players never notice until it's missing.
We run a game-server hosting service and would love to offer your libraries through our curated CS2 plugin catalog — unmodified, SHA-256-pinned to your official release ZIPs, always credited and linked back to this repo, and kept up to date for users automatically whenever you publish a new release.
Right now the repository has no LICENSE file, which legally means "all rights reserved" — so redistributing it isn't actually permitted, no matter how clearly the releases are meant to be used. For a shared library this matters more than for a standalone plugin, because it gets shipped alongside every plugin that depends on it. Would you consider adding a license? MIT and GPL-3.0 are the common choices in the CS2/CSSharp plugin ecosystem (GitHub can add the file in two clicks via "Add file → Choose a license template").
We're asking the same question on AnyBaseLibCS2 and MenuManagerCS2 — sorry for the three notifications. A single license decision would cover all three, so please feel free to answer in whichever issue is most convenient and ignore the others.
If you'd rather not, that's completely fine too — we'll simply keep them as manual-install options for our customers. Either way, thanks for your work!