We welcome everyone to contribute towards the Tebex Project, but doing so will require you to follow specific rules to keep a consistent and welcoming way of contributing.
Tebex has dedicated tracking of feature requests and user suggestions depending on the platform you're inquiring about. If you have a suggestion, please use the appropriate link below to let us know.
Any suggestions created as issues will be closed and forwarded to our Feedback Form.
- Relating to the Minecraft plugin, commands, its functionality, etc.
- Please use the feedback form to tell us your feature request or suggestion.
- Relating to the webstore, packages, coupons, sales, etc on https://tebex.io/
- Please use our product suggestions site to submit your feature request.
- We do not provide customer support via GitHub issues.
- Please contact our support team at support@tebex.io
Issues are intended to document bugs or problems that occur within our project. To report a bug, please open an issue and follow the rules below.
We may have issue templates to help us get the required information more easily. Please follow the provided template when either filing a bug report or feature request.
When it comes to bug reports should you always check first that you're using the latest release of Tebex. It is likely that a bug you're experiencing may have already been fixed if a newer version of the plugin is available.
Make sure that there aren't any existing issues relating to the problem, which are still open, or are closed with a solution/explanation.
We encourage you to leave a comment or reaction if an issue already exists. Comment with your bug report info or even leave just a 👍 if the issue is relevant for you. This helps our team prioritize which issues we approach.
As an open source project are we welcoming all contributions to improve Tebex, being it changes to its code, or contributions to its documentation such as the Wiki or the Javadocs.
When contributing towards the code of Tebex, be it new features or just bug fixes, your changes should follow the general code styling used in the project. Use complete comments and Javadoc where applicable.