Development

JVM 21 for gradle, but can use JVM 17 for building

Code Conventions

• don't use external libraries for things we can easily do ourselves
• try to keep code that will probably have to be modified in a minecraft update, in one place
• write as much code as possible in kotlin
• use "standard" Kotlin code conventions
• remember that kotlin files can contain multiple classes, so DONT CREATE 200 FILES FOR ONE FEATURE

Performance:

• use packed data types: Vec3s, Aabb3s, ... wherever possible
• use blitz RefVec<T> over List<T>

Mixins:

• give mixins either descriptive names, or put them into a descriptive package
• create separate mixin classes for separate features, even if they mixin into the same class

Also:

• make the code JVM 17 compatible.
• release builds have to use JVM 17