CS2Plugins Guidelines

Last updated June 6, 2026

Community Guidelines

These rules apply anywhere CS2Plugins hosts or moderates discussion, including the website, project pages, organization spaces, Discord, GitHub issues, pull requests, and official support channels.

Core Expectations

CS2Plugins is a development community for Counter-Strike 2 server operators, plugin authors, and maintainers. The short version is simple: be decent to other people and follow staff direction.

Treat other users, authors, maintainers, moderators, and newcomers with respect.
Listen to CS2Plugins staff and moderators when they step in to keep the site, Discord, GitHub, or support spaces usable.
Assume good faith where possible, but do not use that as cover for harassment, sealioning, or exhausting people who are trying to help.

Disallowed Conduct

Do not post discriminatory, hateful, pornographic, excessively violent, or intentionally disturbing content.
Do not spam, flood channels, repeatedly repost the same question, or cross-post the same request in many places to force attention.
Do not impersonate other users, plugin authors, CS2Plugins staff, Valve, Counter-Strike, GitHub, or any other person or organization.
Do not use usernames, profile fields, project names, or descriptions to harass people, advertise unrelated services, evade moderation, or make conversation difficult.
Do not ping staff, maintainers, or contributors just to get faster support. Use the proper support or reporting channels.
Do not turn support spaces into arguments about politics, culture-war topics, or unrelated controversies.
Do not discuss piracy, cracked software, stolen assets, bypassing platform protections, or methods for evading bans, anti-cheat systems, ownership checks, or accountability.

Zero Tolerance

Some behavior is incompatible with the community and may result in immediate removal without warning.

Racist, sexist, homophobic, transphobic, ableist, or otherwise hateful slurs or speech.
Doxxing, threats, targeted harassment, personal attacks, stalking, or encouraging others to abuse someone.
Malicious uploads, malware distribution, credential theft, backdoors, destructive server actions, or attempts to compromise CS2Plugins or its users.
Ban evasion, coordinated abuse, or using alternate accounts to continue behavior that was already moderated.

Support Spaces

Keep topic-specific channels and project discussions on topic so people asking for help can be heard.
Do not mock people for using a framework, dependency, server setup, plugin, or older version you dislike. You may recommend better options without being hostile.
Be clear when something is unsupported, deprecated, risky, or outside your knowledge, but do not shame people for asking.
If a conversation is no longer productive, step away or ask staff to help instead of escalating.

Project Guidelines

These rules apply to plugin listings, claims, releases, descriptions, links, downloads, metadata, and any other project content published on CS2Plugins.

Project Updates

Publish updates when they are meaningful: bug fixes, compatibility updates, new features, security fixes, or documentation changes.
Do not push repeated low-value releases just to bump your project, manipulate recent-update sorting, or flood users who follow your project.
Hotfixes are fine when needed. Abuse of release cadence may result in rate limits, hidden releases, or moderation.

Stats and Ranking

Do not artificially inflate downloads, stars, views, claims, search rank, or other project signals.
Do not create alternate accounts, use bots, script repeated downloads, or make auto-updaters redownload the same version to manipulate statistics.
If you believe someone else is botting or attacking your project metrics, contact support instead of retaliating.

Monetization and Advertising

Core plugin functionality may not be hidden behind a paywall, private license key, or off-site paid “full version” when the CS2Plugins listing presents itself as the public release.
Compatibility hooks into paid services are allowed when the plugin also has meaningful functionality that is not similarly restricted.
Advertisements, unrelated promotions, and deceptive sponsorship copy are not allowed in project content.
You may link to related projects, documentation, tutorials, source code, support communities, donation pages, and paid preview subscriptions for future free releases.

Code Transparency

Projects should make their source, release artifacts, and dependency information easy to inspect.
Do not submit intentionally obfuscated plugins or packed releases that prevent reasonable review of what the plugin does.
Minification, bundling, or compiled output is acceptable when normal for the language or toolchain, but it must not be used to hide malicious behavior.

External Downloads

Release links should point as directly as possible to the specific version being offered, not to a vague landing page or unrelated marketplace listing.
Do not use ad-wall, revenue-gated, password-protected, invite-only, or account-required download links for public releases.
External downloads must match the version, platform, and description shown on CS2Plugins.

Forks and Reuploads

Do not reupload another author’s plugin as-is or claim someone else’s work as your own.
Forks are allowed when they make significant changes, continue an abandoned project in good faith, or are otherwise clearly distinct from the original.
Credit the original project and developers when your project is based on or continues their work.
CS2Plugins staff may decide whether a fork is sufficiently distinct or whether a listing should be removed, merged, transferred, or renamed.

Names, Categories, and Platforms

Project names should be clear, readable, unique, and not misleading. Do not imply that your plugin is official CS2Plugins, Valve, Counter-Strike, Metamod, CounterStrikeSharp, or Swiftly software unless that is true.
Avoid stuffing platform names, version numbers, taglines, or marketing slogans into the project name when those details belong in metadata or the description.
Choose the most accurate category for your project. If nothing fits, use the closest general category rather than mislabeling the plugin.
Only select frameworks or platforms that your release can actually load and run on when dependencies and configuration are set up correctly.

Malicious or Unsafe Behavior

Plugins must not secretly grant special access, commands, permissions, cosmetics, admin powers, or gameplay advantages to the author or selected users.
Plugins must not delete server data, damage configuration, ban or kick players arbitrarily, exfiltrate credentials, weaken server security, or hide unwanted network behavior.
Plugins must not facilitate cheating, ban evasion, anti-cheat bypasses, server abuse, or other behavior that harms server operators or players.
Security-sensitive behavior must be clearly documented and justified by the plugin’s purpose.

Moderation

These guidelines are not exhaustive. CS2Plugins staff may allow or disallow behavior not explicitly listed when needed to protect users, authors, server operators, or the service.
Projects may be edited, hidden, unpublished, removed, transferred, or locked while ownership, safety, copyright, or policy issues are reviewed.
Accounts may be warned, limited, suspended, or banned depending on severity and history.

Contact

Report guideline violations, unsafe downloads, ownership disputes, or moderation concerns through our support channel.

Contact support GitHub