Rules of the section

[Nain57]

Basic Rules

• English only, you can use AI for translations
• One feature per conversation.
• Ensure the feature is not already implemented in last Klick'r version (read the wiki)
• Before publishing a new feature request, please ensure you have browsed existing ones and didn't find anything related.
• Feature requests cannot all be implemented in Klick'r. As much as we'd like to please all users, it is impossible to satisfy everybody and we have to keep a certain consistency between the features. Final word will be given to the main maintainer of the project.

Feature Request format

When opening a feature request thread, you must describe the feature you'd like to see added to Klick'r. At minimum, include a clear explanation of what the feature does and the problem it solves. If you want to go further, you're welcome to provide a more complete proposal including UI/UX flow ideas, suggested behaviour in the engine, or any other implementation details you have in mind; the more context, the better.

The thread is then open for discussion: other users and developers may ask questions, suggest alternatives, or build on your idea. The goal is to collaboratively refine the request until it is clear and well-defined enough to be turned into a ticket and added to the project board.

Keep in mind that opening a feature request does not guarantee it will be implemented; please refer to the basic rules above.