awawawawawawa :3
#i got bored and made a little debugger using my multiversion rendering apis (1.8 - 1.21.9)
lilac ether
south trout
awawawawaawawawa
late estuary
1.8 to 1.21.9 is absolutely insane compat
slender pulsar
1.7 when
slender pulsar
Make your own kek
lilac ether
compatibility nightmare
slender pulsar
But I think 1.8 may have been a rendering rewrite, not sure tho, I don't remember shit about old versions
lilac ether
All of the 1.7 modders have moved to whatever custom loaders now
And have all of their own libs for stuff like rendering and render states
lilac ether
But I think 1.8 may have been a rendering rewrite, not sure tho, I don't remembe...
Yes, 1.8 was a big rendering and data overhaul
slender pulsar
All of the 1.7 modders have moved to whatever custom loaders now
The 1.7 modders have basically rewritten 1.7
lilac ether
yeah lol
slender pulsar
I remember a 1.7 guy who would refuse the usefulness of BlockPos (idk yarn name) and PoseStack (aka MatrixStack) and he'd manually do vertex transformations saying that it's just as easy but requires no extra object 
lilac ether
I remember a 1.7 guy who would refuse the usefulness of BlockPos (idk yarn name)...
It's also BlockPos in Yarn
slender pulsar
It's also BlockPos in Yarn
Oh nice
lilac ether
And he was just straight lying
I backported MatrixStack to 1.8
for a reason
My abstraction would work in 1.7 too
slender pulsar
MatrixStacks are fucking amazing (you may notice that by my name)
lilac ether
lmao
My library backports MatrixStack, RenderPipeline and a good bit of DrawContext
And has a custom texture manager
slender pulsar
MatrixStacks are fucking amazing (you may notice that by my name)
Like I sometimes use them even just to scale some points (e.g. mouse cursor position) when working with scaled UIs lol
slender pulsar
My library backports MatrixStack, RenderPipeline and a good bit of DrawContext
Sounds like it's time to backport 1.21 to 1.7
lilac ether
Horrible
I've considered it
Or said publicly that I'd accept the PR if someone wanted to contribute it
It'd be a pain to maintain though
slender pulsar
From my experience, it's a pain to maintain anything multi-version
lilac ether
My entire job is maintaining multiversion multiloader
"1.8.9-forge",
"1.8.9-fabric",
"1.12.2-forge",
"1.12.2-fabric",
"1.16.5-forge",
"1.16.5-fabric",
"1.17.1-forge",
"1.17.1-fabric",
"1.18.2-forge",
"1.18.2-fabric",
"1.19.2-forge",
"1.19.2-fabric",
"1.19.4-forge",
"1.19.4-fabric",
"1.20.1-forge",
"1.20.1-fabric",
"1.20.4-forge",
"1.20.4-neoforge",
"1.20.4-fabric",
"1.20.6-neoforge",
"1.20.6-fabric",
"1.21.1-neoforge",
"1.21.1-fabric",
"1.21.2-neoforge",
"1.21.2-fabric",
"1.21.3-neoforge",
"1.21.3-fabric",
"1.21.4-neoforge",
"1.21.4-fabric",
"1.21.5-neoforge",
"1.21.5-fabric",
"1.21.6-neoforge",
"1.21.6-fabric",
"1.21.7-neoforge",
"1.21.7-fabric",
"1.21.8-neoforge",
"1.21.8-fabric",
"1.21.9-neoforge",
"1.21.9-fabric",
Do you do stonecutter or git branches?
slender pulsar
huh
lilac ether
A 1.7 backport would be hard
But not only because of rendering
It also wraps a ton of other things and backports/forwardports a lot of other features
(like forward porting immediate tessellation to 1.21.6+)
storm plank
1.1 backport when????? 💯
south trout
lol
south trout
https://tenor.com/view/rage-rat-rage-anger-grr-fist-gif-22836324
b1.7.3 backport
lilac ether
Wait, is it [OmniCore](https://github.com/Deftu/OmniCore)?
Yes
north vigil
I remember a 1.7 guy who would refuse the usefulness of BlockPos (idk yarn name)...
isn't it AABB in mojmap but BlockPos in yarn
slender pulsar
isn't it AABB in mojmap but BlockPos in yarn
AABB and BlockPos are two entirely different things
lilac ether
isn't it AABB in mojmap but BlockPos in yarn
AABB = Box
BlockPos = BlockPos
north vigil
ah