> For the complete documentation index, see [llms.txt](https://ss3d.gitbook.io/management/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ss3d.gitbook.io/management/finances/bounties/dev-bounties.md). # Dev Bounties ## Eligibility Conditions for a task to have a bounty are : * It's part of the current milestone. * It must be clearly detailed. - If it's a bug, some attempt must be done to fix it before. ## Bounty price The price of the bounty will be fixed by a Centcom member, by estimating how time consuming it will be : * **Full new system (90 dollars)** : * Implementing every aspect of a complete major system design doc. * **Major rework / Major feature (60 dollars)** : * Major rework : Heavy changes on an existing system, full reorganization, significant boost in performance/readability/re-usability. * Major feature : Adding some lengthy and complex classes/struct/prefabs, complex methods. * **Minor rework / Minor feature / Major fix (30 dollars)** : * Minor rework : Changing a chunk of an existing system, a few classes/methods. * Minor feature : Changing a few classes, adding small classes. * Major fix : Fix impacting multiple systems and hard to solve. * **Minor Bug fix / Small feature (15 dollars)** : * Minor Feature : Small change to existing code. * Minor bug fix : bug that doesn't affect multiple system, that can be solved in a few changes (usually a few lines). ## Claiming a Bounty Anyone can claim a bounty. Bounty claimers have to show regularity in their progress to keep the bounty claim. After two weeks of inactivity (no substantial commit or change to a design doc), and if no justification is provided, anyone else can claim the bounty, on a decision of a Centcom member. One person can't claim two bounties at the same time, they can only work on one bounty task at once. ## Bounty price modification Bounty price can be modified when a pull request is ready and only upon accepting a pull request. The bounty price can only go up. As an example, if what was believed to be a simple bug fix, actually needed a major rework, then the bounty price will be adjusted to reflect fairly the work of the contributor. The decision is taken by a Centcom member. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://ss3d.gitbook.io/management/finances/bounties/dev-bounties.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.