By
@MarioS271
A minecraft mod which gives you Night Vision, even if you aren't a server operator. Inspired by CatEyes by Tee6! :) Version 3 is again a complete rewrite aimed to bring support to all versions from 1.16.5 up to the latest one.
Hi!
Welcome to my minecraft mod, CatVision.
(well its just a rewrite of a rewrite but still)
This is CatVision v3.0, the third rewrite.
Disclaimer: If you do not own minecraft, I suggest you skip reviewing this (with the little skip button at the top of the page), as you won’t be able to try this properly.
Default Keybinds:
[F12] Open Config Menu (also possible via the Mod Menu)
[ , ] Toggle Night Vision
Why rewrite it that often?
Well the first version (CatVision Legacy) only supported minecraft 1.21 and later on the fabric loader. Version 2 (aka CatVision Architectury) used the Architectury Loom to support Fabric, Forge and NeoForge on versions 1.16.5, 1.20.1, 1.21.1 and 1.21.11.
However, I wanted support for WAY more versions, bringing us to now. Version 3 uses Stonecutter (a gradle preprocessor for building multi-version and multi-loader mods in one codebase). By doing so, v3 supports 1.16.5, 1.17.1 and all later versions, on Fabric, Forge and NeoForge.
I hope you have fun playing around with the mod!
2h 28m 7s logged
Support for 26.1, 26.1.1, 26.1.2 and 26.2 is finally here.
After fixing a mistake in the fabric build config, everything finally works and compiles.
Yesterday, the 1.21.9 build on github failed… because the maven server of one dependency decided not to respond :)
2h 1m 34s logged
1h 0m 2s logged
I’ll be doing 1.21.x now, not sure if I’ll finish it today. Tomorrow, hopefully everything will be finished and I can start rewriting my other three mods in this format :)
moddev-gradle to resolve them properly)
2h 22m 54s logged
So get this: In NeoForge 20.4 and earlier (which maps to MC version 1.20.4 and prior, I’m on MC 1.20.4), the metadata file should be under META-INF/mods.toml.
Exactly ONE version later (NeoForge 20.5+, aka MC 1.20.5+), that changed to META-INF/neoforge.mods.toml. Of course, my build toolchain was generating neoforge.mods.toml and NeoForge wasn’t recognizing that, it wanted mods.toml.
1h 30m 27s logged
1h 56m 13s logged
2h 35m 56s logged
it is 3h after midnight why do i do this to myself
AAND the final boss… cloth config issue #2
Problem: The dev instance of minecraft uses the mojang mappings, but cloth config uses SRG mappings. Of course, SRG mappings and mojang mappings aren’t compatible, and as soon as you opened the config menu, the game would crash (but only in dev builds!). The problem is, this issue would’ve likely stayed for EVERY forge version of the mod, meaning debugging would’ve gotten VERY ANNOYING (build, import into real minecraft instance, test there).
Simple: just remap cloth config from SRG to mojmap when in the dev env! Simple task!
…except the remapper needs a “dictionary” jar in the same mappings as the thing it’s remapping. Cloth is SRG. The dev env only has mojmap. So there was no SRG dictionary to hand it.
How do I solve this now? SIMPLE!!! Remap Minecraft itself BACK to SRG just to use it as the dictionary, then remap cloth against that!!!!!!!!!!!! All that to fix ONE GODDAMN FIELD NAME
I would like to thank Claude for the technical (and moral) support in this thank you thank you thank you thank you thank you thank you
56m 33s logged
Published on GitHub, under review on Modrinth and Curseforge :)
1.16.5-fabric done and released1.16.5-forge done and released1.16.5-forge specifically
NFRT (the runtime behind net.neoforged.moddev.legacyforge) can only build Minecraft versions that ship official Mojang mappings (which start at 1.17), which of course aren’t shipped for 1.16.5. This required the switch to Architectury Loom for that one version+loader combo. (thank you claude for your token-sacrifise for that 🫡)
36m 22s logged
3h 56m 2s logged
I didn’t like the project structure (seperate branch per minecraft version, hard to maintain, every version has to be managed independently, hard to scale) and I wanted compatibility for 1.16.5 up to the latest version and all inbetween with support for fabric, forge and neoforge.
Stonecutter is a gradle plugin that lets you maintain a single codebase for a multi-version and multi-loader project. You just annotate your code with version and loader conditions, and at compile time, stonecutter just “preprocesses” the annotated code.
On a slight side note to preprocessing (if you’re interested): Preprocessing is the act of temporarily changing the source code (the human readable code that you write, NOT the machine code) before compilation. This is done by the preprocessor, a special program written for this one purpose. It is usually the first step in a program’s compilation (example: the C preprocessor, with instructions like
#include,#defineand more)
Currently, I’ve got the template up and running with the 1.16.5-fabric version of the mod already functional. I’ve also set up the GitHub repo and the modrinth and curseforge projects.
