- Kotlin 98.6%
- Java 1.4%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
| build-logic | ||
| common | ||
| fabric | ||
| forge | ||
| gradle | ||
| neoforge | ||
| .editorconfig | ||
| .gitignore | ||
| gradle.properties | ||
| gradlew | ||
| gradlew.bat | ||
| LICENSE | ||
| README.md | ||
| settings.gradle.kts | ||
| stonecutter.gradle.kts | ||
| stonecutter.properties.toml | ||
Origins: Legacy
Origins: Legacy was previously an unofficial forward port of the original Origins mod, but is now a full rewrite of the entire mod from the ground up, while still entirely providing backwards compatibility for Origins datapacks that were created for Minecraft 1.20.1 and prior.
If you need help with creating data packs for the mod, you can visit the official wiki. The official wiki is still sufficient for
making datapacks, as long as you are under the 1.10.0 branch, which is what this fork is based on.
If you want to report a bug, please visit the issue tracker. Make sure to check other existing issues first, and post detailed information about which mods and which version you are using, what you would expect to happen, and what happens instead. Also always include the log of your client and the server if possible.
Does this support custom origins made for Origins 1.21.1?
Not really, since the codebases, feature sets and even the main data formats have changed quite significantly in the new codebase. On the other hand, Origins: Legacy tries to retain compatibility with the 1.20.1 origins datapacks as best as possible, usually only requiring changes at the regular Minecraft datapack level, which is usually much better documented.
Is this AI generated? Why on earth would you rewrite it like this?!
Nope, no AI used whatsoever. The code of Origins was starting to break more and more the longer I was working on newer versions, and it was incredibly difficult to realize that any data formats were broken in the first place, because the previous serialization library, Calio, did a lot of unsafe reflection. This version on the other hand uses Mojang's official codec system, which works significantly better. Additionally, this rewrite fully removes all usage of another major pain point, Cardinal Components API, in favour of the Data Attachments API that is natively in Fabric and NeoForge. With the removal of CCA, NeoForge is also able to be supported with slightly less pain.
Will any addons be compatible with this?
To put simply, nope. Only the origins themselves. This is filled entirely with breaking changes. However, I have chosen to mainline certain addons into Origins: Legacy so we can have much more features as well, namely:
- Origins Extra Keybinds
- Licensed ARR, so we're cleanroom rewriting this.
- Apugli
- This is licensed under MIT, but is mostly rewritten similarly to how this rewrite is being done, which is referencing the documentation and reimplementing it like that, with the occasional looking at the original source code when stuck.