This might just be me, but after reading this, telling the differences in what you can and can't do as a contributor and developer seems kind of hard to tell
When I made the beacon, @SumianVoice contributed the mesh (+ blender file)
Got a few minor suggestions, I noticed them a while ago, yet never saw the need to create a seperate PR just for those
Assuming everyone who's mod migrated into mcl mcl is worth adding here:
debiankaios's name starts with a lower case 'd' (been in contact with him since 2020)
Should wuzzy be in here? It's not like he wasn't a maintainer from 2017 - late 2020
Sorry for force-pushing 2 times in a row, what I just did altered some files that it wasn't supposed to, others were reduces in filesize (like intended), and some even increased, thats why I went…
378b413986
Merge pull request 'OptiPNG a bunch of textures' (#3816) from optimize_textures into master
Sure, this is why #define in C and C++ exists, however, in that situation, it makes no difference as the compiler takes care of it...
Anyways, I agree, in the end, it is just 8 bytes of RAM…
Damage dealt by a skeleton using a bow in MineCraft (according to this article on the wiki):
I got a (very nitpicky) suggestion
It seems like this variable ONLY get used once, unless you consider adding a setting for the replace rate, it should stay hardcoded in my opinion