Skip to content

Haiyan451/zh_ch-4-tetra

 
 

Repository files navigation

Tetra

Source and issue tracker for tetra.

Contribution

If you're interested in contributing to the project there is lots of work that does not require any artistic skill or experience with development, I'd be super happy if I could get more help with the following:

  • Help to validate or improve the "How to reproduce steps" in bug issues.
  • Look at incoming issues and compare them to existing issues to see if they are duplicates.
  • Help to clarify feature requests so that it is clear how/when they would be considered done.
  • Check out advancements and descriptions for new features and let us know (preferably on discord) if that helped you understand how it works
  • Compare balancing between different types of content and mechanics to

If you're a developer or if you're good with pixel art and would like to contribute then look for the help appreciated label on issues, or hop onto discord and wave if there are none!

By contributing code or assets this repository you grant the project full rights over your contributions. If you do not agree with that, do not contribute.

License & Use

The points below outline what you can, cannot and must do when dealing with the contents of this repository.

You CAN

  • Fork and modify the code.
  • Submit Pull Requests to this repository.
  • Copy portions of this code for use in other projects.
  • Write your own code that uses this code as a dependency. (addons, mod integration or datapacks)

You CANNOT

  • Change, use or remove content or assets related to the Perk system.
  • Redistribute this in its entirety as source or compiled code.
  • Create or distribute code which contains 50% or more Functionally Equivalent Statements* from this repository.

You MUST

  • Not be a dick. Treat others, and the work of others, with kindness, humility and respect. If you can't do that then you can't use anything from this repository.
  • Check in on discord before overwriting existing content.

Notes, License & Use

*A Functionally Equivalent Statement is a code fragment which, regardless of whitespace and object names, achieves the same result within the context of a Minecraft mod or addon.

Since this project uses Mojang mappings and most assets are heavily based on Minecraft assets it's probably a very bad idea to use anything from this repository outside the context of Minecraft modding.

Essentially, look at this and learn from it. Create addon mods that expand upon it, hook up your own mods to integrate with it or tweak how it works for your modpack. If you see something that can be improved, please create an issue, discuss it on discord or submit a pull request. A lot of effort has gone into making this, do not take significant parts of this and pass it off as your own.

©2018-2022 Mikael Eriksson Vikner

Releases

No releases published

Packages

No packages published

Languages

  • Java 100.0%