Skip to content

GTNewHorizons/bdlib

 
 

Repository files navigation

GTNH Code of Conduct

This Code of Conduct applies to anyone representing or contributing to the GTNH project, including on GitHub, Discord, and any other GTNH-related space.


Expected Behavior

GTNH developers and contributors are expected to treat others with respect.

In short: do not be a jerk.

This includes, but is not limited to:

  • Being respectful toward other developers, contributors, players, and community members.
  • Giving feedback constructively.
  • Disagreeing with ideas without insulting the person proposing them.
  • Assuming good faith when possible.
  • Being open to criticism and review.
  • Remembering that comments made on GitHub or Discord reflect on the GTNH project as a whole.

Behind every pull request, issue, or review comment is a person who has invested time and effort into the project. A single rude or dismissive comment can discourage someone from contributing again. Today’s new contributor may become tomorrow’s project lead.


Unacceptable Behavior

The following behavior is not acceptable:

  • Insulting, harassing, or belittling other developers, contributors, players, or community members.
  • Malicious trolling.
  • Looking down on others because they disagree with you, know less than you, or made a mistake.
  • Attacking people instead of discussing their ideas or changes.
  • Repeatedly creating hostile, dismissive, or unconstructive discussions.
  • Representing GTNH in a way that damages the project or discourages contribution.

Disagreement is allowed. Strong technical opinions are allowed. Personal attacks are not.


Review Conduct

When reviewing pull requests, keep feedback constructive, actionable, and respectful.

Good review behavior includes:

  • Explaining what should change and why.
  • Asking questions when something is unclear.
  • Highlighting what was done well, not only what needs improvement.
  • Framing concerns as genuine discussion rather than personal criticism.
  • Helping contributors improve instead of discouraging them.

If a pull request is unclear, incomplete, or incorrect, say so respectfully and explain what is needed.


Criticism and Project Direction

Contributors should be open to criticism. Sometimes a change you worked hard on may not be accepted in its current form. That is part of the development process.

Likewise, reviewers and maintainers should give criticism in a way that helps the contributor understand the concern and improve the work.


Enforcement

Violations of this Code of Conduct may result in moderator or maintainer action.

Depending on severity and history, this may include warnings, removal from a discussion, loss of developer permissions, or demotion from GTNH roles.

Major contributions to the pack do not exempt anyone from following the Code of Conduct.

About

A library for minecraft modding

Code of conduct

Contributing

Stars

Watchers

Forks

Releases

Packages

Used by

Contributors

Languages