Skip to content

Latest commit

 

History

History
76 lines (50 loc) · 4.17 KB

File metadata and controls

76 lines (50 loc) · 4.17 KB

Contributing to Vencord

Vencord is a community project and welcomes any kind of contribution from anyone!

We have development documentation for new contributors, which can be found at https://docs.vencord.dev.

AI Policy

Vencord has strict rules for AI usage:

  • AI slop will result in a block. If code or text you submit is clearly generated by AI without human review and cleanup, you will be blocked from contributing to the project. Examples of slop include overly verbose text, unnecessary comments, overcomplicated code, failure to follow project conventions, and other signs of minimal human involvement.

  • All AI usage in any form must be disclosed. You must state the tool you used (e.g. Claude Code, Codex) along with the extent that the work was AI-assisted.

  • The human-in-the-loop must fully understand all code. If you can't explain what your changes do and how they interact with the greater system without the aid of AI tools, do not contribute to this project.

  • Don't post AI generated texts in issues, discussions or PRs. AI is very good at being overly verbose and including noise that distracts from the main point. You can use AI to assist you, but you must trim it down and ensure it is concise and relevant.

How to contribute

Contributions can be sent via pull requests. If you're new to Git, check this guide.

Pull requests can be made either to the main or the dev branch. However, unless you're an advanced user, I recommend sticking to main. This is because the dev branch might contain unstable changes and be force pushed frequently, which could cause conflicts in your pull request.

Before working on a major change, I highly recommend opening a feature request for it, making sure to check "I am willing to work on this myself", so we can discuss before you invest time. Alternatively, you can also do so in our Discord server's development channels. This saves you a lot of time in case your feature is considered too niche or rejected for any other reason.

Write a plugin

Writing a plugin is the primary way to contribute.

Before starting your plugin:

  • Consider if this plugin would be useful to a large portion of the userbase. We do not accept niche plugins
  • Check existing pull requests to see if someone is already working on a similar plugin
  • Familarise yourself with our plugin rules below to ensure your plugin is not banned

Plugin Rules

  • No simple slash command plugins like /cat. Instead, make a user installable Discord bot
  • No simple text replace plugins like Let me Google that for you. The TextReplace plugin can do this
  • No raw DOM manipulation. Use proper patches and React
  • No FakeDeafen or FakeMute
  • No StereoMic
  • No plugins that simply hide or redesign ui elements. This can be done with CSS
  • No plugins that interact with specific Discord bots (official Discord apps like Youtube WatchTogether are okay)
  • No selfbots or API spam (animated status, message pruner, auto reply, nitro snipers, etc)
  • No untrusted third party APIs. Popular services like Google or GitHub are fine, but absolutely no self hosted ones
  • No plugins that require the user to enter their own API key
  • Do not introduce new dependencies unless absolutely necessary and warranted

Improve Vencord itself

If you have any ideas on how to improve Vencord itself, or want to propose a new plugin API, feel free to open a feature request so we can discuss.

Or if you notice any bugs or typos, feel free to fix them!

Contribute to our Documentation

The source code of our documentation is available at https://github.com/Vencord/Docs

If you see anything outdated, incorrect or lacking, please fix it! If you think a new page should be added, feel free to suggest it via an issue and we can discuss.

Help out users in our Discord community

We have an open support channel in our Discord community. Helping out users there is always appreciated! The more, the merrier.