#1.21.11 Snapshots
4486 messages ยท Page 5 of 5 (latest)
just do year.major.neo without mc hotfix
what if drops were represented by letters
since launchers have to switch it up anyways
It will still be a new MC version for all launchers and that means people will have no idea that .125 is the first version for any given hotfix
I don't think MC hotfix is necessary yeah
so 26A<hotfix><neo>
yeardrop.hotfix.neo !!!
261.0.45 -> 26.1.0 neo version 45
what if they do eleven drops in one year
account for double digits
ew
and when they drop 100 drops in a year then what ||/s||
looks awful
can we just expect launchers to also use the latest hotfix?
then we switch to hexidecimal
Papaya-SNAPSHOT
NeoForge Oreo when
no, launchers have to check mod compatibility against the mc version
u will need lot of fruits
๐
confusing
that'd be about a drop every 3/4 days
I don't think Mojang is that speedy
lowk i kinda fw the item idea
ngl hex might be better for neo patches lol. you wont get 3 digit versions anymore
its a funny concept
let's reserve 4 digits for drops then,
yyyyddddhhhh.neo
202500010000.45
a mod may be compatible with the first hotfix and not the second
we will get into debate if this is fruit or vegetable
realistically we should use something like fish for snapshots, I don't think we'll be able to come up with that many vegetables
but just for numbers > 100
the launcher HAS to have you update the mc version
yes. excellent.
more engagement ๐
you underestimate the number of obscure vegetables:D
fish + veggie, same initial
Tomato Trout
Cabbage Cod
needs to be minecraft items imo
We wouldve had NeoForge Resin, NeoForge Firefly Bush, NeoForge Dried Ghast, NeoForge Waxed Lightly Weathered Copper Golem Statue, and NeoForge Spear
NeoForge Cantaloupe Calamari
NeoForge B... Blobfish
can't think of a B veggie
Beetroot
Butternut Squash
pls brain burger is not a vegetable
But... banana even if it's a fruit instead
Anyhow. Any change in MC version should result in a new .1 from Neo, since we can 1) never guarantee backwards compatibility and 2) they'll always be completely separate sets of versions for launchers.
isnt banana a berry
4-component versions, then, as much as they hurt
hotfixes can be breaking for mods
26.3.1.132
They can be, even if they just update a 3rd party library due to a security vuln
but honestly players should never see a hotfix version
They do, and they do in the Vanilla launcher too
i think if launchers also had u select a drop thatd be great
and as I said, it's important noting that mod hosting sites will still run compatibility checks against the exact mc version. launchers cannot simply update the mc version, hotfix or not
they will see the hotfix
Kinda wish it was snapshot.1 instead of -1, but whatever
That still parses as semver
its not -1 tho, its snapshot-1 they are using the - to join the different parts into 1 str
look at left vs right in that image
only annoying since the numeric part isn't using the dot-notation for segments
Yeah
I know. Semver says the number should use a . not a - as a separator
It says nothing about "should"
it just defines an order more formally for dot-separated parts
i will reask this
so about neoforge when will the neoforge drop the support and backport new features?
like 1.21.1 is still getting backports
the good part is that neo can actually release builds for snapshots. we can <whatever represents the drop>.<neo version>-snapshot-1
(append mc's suffix)
although, not really comparable as far as release vs snapshot goes hmm
For parts that have dashes it says Identifiers with letters or hyphens are compared lexically in ASCII sort order., but it doesnt give an example if 1.0.0-pre-1 is < 1.0.0-pre-11 or not
havnt we also just not been following proper semver for a while?
something, something.. dont we include lib to allow weird version numbers or something
yeah no we'd have to append to the -snapshot-1
it's not about really following semver
but the version ordering semantics of semver are very nicely defined
It would be, but -pre-11 < -pre-2
even if you drop the definition of what major/minor/patch do
Maven versioning: 25.10.5 < 25.10.6-snapshot-1
yeah.... ugh
yeah very annoying
you'd likely have to treat it as a pre-release of the first neo release for that version
so: 25.10.6.1-snapshot-1-<neo-version>
snapshots are meant to be used internally so it should be fine
they accept backports to whichever versions people wanna backport to
yeah I guess
(.0 not .1)
.1 can be the release
It would be nice to be able to use existing libraries for the format is the thing
Maven versioning: 25.10.6.1-snapshot-1-1 < 25.10.6.1
that might be too much work after a few more versions
eh, I guess
Although rc < snapshot
it just has to be a pre-release for what the first neo version would be, if .0 can be the first, then yes, it has to be .0-snapshot-...
Maven versioning: 25.10.6.1-snapshot-1-1 > 25.10.6.1-rc-1-1
oh fuck you mojang
yep
snapshot, alpha, beta
gradle doesnt even necessarily sort the same lol
you need one for pres
Maven versioning: 25.10.6.1-snapshot-1-1 > 25.10.6.1-alpha-1-1
how does it handle .1
i stole the military one
why stop at hex?
Maven versioning: 26.10.6-snapshot-1.1 < 26.10.6.1
gamma
shouldn't our build always go at the end?
- is not really intended to go in the middle of the version
mixing of '-' (dash) and '.' (dot) separators,
transition between characters and digits also constitutes a separator: 1.0alpha1 => [1, 0, alpha, 1]
unlimited number of version components,
version components in the text can be digits or strings,
strings are checked for well-known qualifiers and the qualifier ordering is used for version ordering. Well-known qualifiers (case insensitive) are:
alpha or a
beta or b
milestone or m
rc or cr
snapshot
(the empty string) or ga or final
sp
Unknown qualifiers are considered after known qualifiers, with lexical order (always case insensitive),
a dash usually precedes a qualifier, and is always less important than something preceded with a dot.
So. Good luck getting that in line with what gradle does, which is not the same
that solves the ordering between versions at least
what was wrong with <year>.<major>.<hotfix_or_0>.<neo>?
smh, not knowing your Greek alphabet
now as to where to put it
uppercase SNAPSHOT seem to work
SNAPSHOT has a different meaning
will we get new channel for every drop?
thats for releases this is for non-releases
sure, but neither is solved?
technically we might get away with str-replace - -> .
Since... whatever a dash usually precedes a qualifier, and is always less important than something preceded with a dot. actually means
i think it was decided to do <year>.<drop/update>.<hotfix_or_0>.<neo>
what is this, ubuntu?
nothing is decided
the mainters will do that later
but figuring out options for snapshots/etc. would be good
Maven versioning: 26.11.5 > 26.11-alpha-1.5
it'd be far easier if mojang had dropped snapshots/pre/rc distinction ๐
and just did -pre.1 to -pre.n
Maven versioning: 26.11-beta-1.5 > 26.11-alpha-1.5
Maven versioning: 26.11-beta-1.5 < 26.11-rc-1.5
at least there's that
well yes obviously that's what that says, but you have to check gradle too
technically you dont have to do that either
why do you even care about that order specifically ๐
because it's nice to sort them 
as long as any "-qualifier" is < relative to the final, i don't really care that snapshot < pre < rc
you can sort them for our websites using custom logic
you dont have to rely on Maven crap
in version ranges too
it matters for version ranges in mod metadata
yes, and lets be honest
people trying to cut a version range between snapshot/pre/Rc
are lunatics
and deserve what they get ๐
would probably make sense to align with fabric here and do 26.1-alpha.1 for snapshots
i dont see any reason to align version numbers with fabric
wouldn't that be more confusing?
other than fabric having a good idea we can copy
i mean if yours are off by 1 character that would certainly be confusing
why not help everyone's brains a little
-# โฉ slicedlime (@slicedlime.bsky.social)
And for everyone constantly yelling about semver, semver is a library / API versioning system. It literally requires that you declare a public API and *that* is what you're versioning. Not applicable.
So 26.1-blpha.1?
heh.
26.1-blyat.1
26.1.a1pha.1
I hate how semver owns the trademark on semantic versioning
what if they use semver for datapacks and resourcepacks /j
What if they just had game drops take over the old versions? Next drop is 1.22, after that is 1.23, and so on...
expectations for major features
they want to have a fresh new version format
to separate size from version
now the only thing that the last number should matter for is hotfixes
my day is ruined
That was how it was before the drops incrementing the last number too tho
They're fixing a problem they created
eh not really
They don't need it
Every change fits in the major version
hotfixes are not minor updates
like 1.16.1 adding the piglin brute
wouldve been a drop
or part of one
CalVer โค๏ธ
0ver 
2025ver
that's pretty much what they do with the datapack minor versions now lol
it seems snapshots versioning is also changing 
[Reference to](#1425127445803045186 message) #1425127445803045186 [โค ](#1425127445803045186 message)https://x.com/slicedlime/status/1995886660417192442
yeah
I can actually see what version the snapshot is for by looking at the snapshot version now
It was endearing, but effectively no better than git hash
well, it was better in the sense that it wasn't effectively random 
1.10 laughs somewhere
(It was smaller than some of the recent drops)
So, where the modding will stick then after 1.21.1 btw?
neo can't decide that, it's up to individual modders to pick the versions they want to mod
I think the idea of picking the last one of a year-series makes sense
1.21.11+hotfix (possibly 1.21.12) would be last of the 1.21 series, so that should be the next target based on that idea
then the last 26.x hotfix would be the next, and the last 27.x hotfix the one after
all roughly coinciding with the end of the year and winter holidays
(summer for australians)
Or maybe take the first one of the year?
Since it's the one that finally changes the major number
yes but that sounds like unstable, doesn't it?
taking the first? like what about all the other fixes?
and early in the year people tend to be busier
meanwhile it's so easy to tell people that ask "I support the latest of the 26.x series, whatever that latest may be today"
vs "you have to get 26.1 but the biggest number within the 26.1 sub-versions"
coa otherwise people will grab 26.1.0.0 and suffer
cos it's not really the first of the year it's the last of the first
Yeah I mean taking latest hotfix for the first drop of the year
Though looks like everything depends on what will large mods do (AE2, RS2, Create, etc)
what do you mean by that 
I just wait for the day that 1.2.5 becomes popular again
The version that will get many popular mods ported may become next milestone
that is much more confusing for the players than "latest of the 26 series" :P
Jokes on you, I am playing b 1.7.3 with BTA
26.1.X
why Mojang stole Apple's versioning 
because apple stole it from something else as well
Windows 95. ๐
having year as the version is a very common approach
looks at version 2025.12.01
that's a date :V
no that is a version number in our nuget feed at work
at least it is not 2025,01,12
parchment 
will be dead
@ Mojang
to clarify the first non obfuscated snapshot will be 26.1-snapshot.1 skipping any hotfix 1.21.12
1.21.11 Snapshots

the worse part is that now our versions will become funny numbers
because effectively you need their 4 parts + our 2/3?
or you know, we'll just add .neo+githash 
my brain tried to parse that as APL 
Why ็๏ผ instead of ๏ผ็? Since you are not using it as a counter
Oooo
โฆ.
can we reach double digits pre-releases?
New version detected: 1.21.11-pre5.
what is highest pre reached before?
I hope not they have less than a week to ship it
pre8, for 1.16 and 1.18
ty
1.21.11 - Pre Release 5
- Primer: https://github.com/ChampionAsh5357/neoforged-github/blob/primer/2111-or-22/primers/1.21.11/index.md
- Article: https://www.minecraft.net/en-us/article/minecraft-1-21-11-pre-release-5
- Changelog: https://misode.github.io/versions/?id=1.21.11-pre5
- Notion: https://apexmodder.notion.site/2524f070f88880648482e3cbdcba566a?v=2524f070f88880b29f60000c52785ecb&p=2be4f070f888802f9bddefd653bfca32&pm=c
- SnowMan: https://github.com/neoforged/Snowman/commit/5df8be572efaa818239145eb7c8d4734580d36f7
SlicedLimes Videos:
- Main: N/A
- Pack: N/A
Boo, no rc ๐
so, rc1 tomorrow is still possible

funniest solution to neoforge needing a new way to structure the loader version - add back the 1 prefix
neo never cared about that anyways tho
Ubuntu?
ubuntu uses YY.MM, so no
ie: ubuntu 26.04 is the next release, which will release in April 2026
My favourite versioning scheme is salt's, which switched to date versioning (2024.04), and then back to semver, so now is on version 3007.9. We can only hope that Mojang don't do that.
I'm sorry what, did the bump straight to 3000 after switching back to semver or did they somehow shove nearly 80 major versions in there?
980*
which is even more wild, lol
Yeah, exactly that. I think to make it very obvious it was no longer using date versioning.
Just with end result of having a hilariously over-inflated version number.
Unity did similar
5.x -> year -> 6000.x
unity 6.0 has versions 6000.0.x, 6.2 has versions 6000.2.x, and so on
mid week pre makes me think its either todaty/this week, or next tuesday
i'd bet on rc today/tomorrow and releaes tuesday, if i were a bettin man
been no mojira issues closed either
lol, i'm good
isn't tuesday the planned release date?
is the release date announced?
Not afaik
I thought it's the 9th confirmed because they need time for a potential hotfix before the winter break
Guess we will see, but Iโve not seen any announcements for date
Time for another Minecraft Monthly episode, and Vu has fully embraced the role of ring (and mayhem) announcer! Perhaps heโs even gone a bit overboard, if you ask Agnes Larsson and her eardrums. Hopefully, heโll calm down and tell you more about everything from boxing, AI, lots of Mounts of Mayhem features, and so much more:
00:00 โ 01:04 ...
didnt know the date was announced in any way
yep
so I was right Tuesday
New version detected: 1.21.11-rc1.
1.21.11 - Release Candidate 1
- Primer: https://github.com/ChampionAsh5357/neoforged-github/blob/primer/2111-or-22/primers/1.21.11/index.md
- Article: https://www.minecraft.net/en-us/article/minecraft-1-21-11-release-candidate-1
- Changelog: https://misode.github.io/versions/?id=1.21.11-rc1
- Notion: https://apexmodder.notion.site/2524f070f88880648482e3cbdcba566a?v=2524f070f88880b29f60000c52785ecb&p=2be4f070f88880b88735e8c587898f83&pm=c
- SnowMan: https://github.com/neoforged/Snowman/commit/2e940ecc98dca79a750dd05d0bb859541721cf08
SlicedLimes Videos:
- Main: https://www.youtube.com/watch?v=fthuoV6jwE0
- Pack: N/A
||<@&1067092163520909374>||
The Mounts of Mayhem Drop has a Release Candidate that brings us knockback tweaks! Here's a video showcase! #minecraftemployee
slicedlime works as a Technical Director for Minecraft at Mojang, but the YouTube and Twitch channels are personal projects run entirely in his spare time. This is an unofficial update video that aims to be the most com...
Note: The official lz4-java project has been discontinued. A community fork is available here. To address CVE-2025-12183, Sonatype has added a redirect from org.lz4:lz4-java:1.8.1 to the new group ID.
Out-of-bounds memory operations in org.lz4:lz4-java 1.8.0 and earlier allow remote attackers to cause denial of service and read adjacent memory via untrusted compressed input.
Where does Minecraft use LZ4? Network?
i think so?
or was it chunks, i thought chunks were gzip
yep, region files are lz4
compressed nbt were gzip last time I looked, no idea about chunks
No primer changes
oh hang on thats the wrong link
whoops
The Mounts of Mayhem Drop has a Release Candidate that brings us knockback tweaks! Here's a video showcase! #minecraftemployee
slicedlime works as a Technical Director for Minecraft at Mojang, but the YouTube and Twitch channels are personal projects run entirely in his spare time. This is an unofficial update video that aims to be the most com...
is Neo gonna keep the same versioning format when Mojang changes to the new YY.drop.bugfix format?
it was being discussed somewhere
i'll see if i can find it in search
ah no it was in the backchannels 
rude /j
there was a little bit of discussion here, but most of it is back channels
we can't do four numbers because log redacters might think the build versions are IP addresses and redact them 
I still think we should and then yell at bad filters as they already will filter JEI
and like a couple other mods at least
When will 1.21.1 drop support?
never
neoforge backporting bot makes backporting PRs very easy and we have breaking change checker bots. Up to anyone to handle making the backport
see y'all in 2035
doesnt packporting everything to 1.21.1 increases development time and will be more and more as more versions are out
unless u are only porting to 1.21.1 and not all versions in between
we develop for latest. Up to the person if they want to backport or not. We wont block it basically
has someone worked on local remapping for when unobf begins?
that will break backported patches otherwise
1.21.11 - Release Candidate 2
- Primer: https://github.com/ChampionAsh5357/neoforged-github/blob/primer/2111-or-22/primers/1.21.11/index.md
- Article: https://www.minecraft.net/en-us/article/minecraft-1-21-11-release-candidate-2
- Changelog: https://misode.github.io/versions/?id=1.21.11-rc2
- Notion: https://apexmodder.notion.site/2524f070f88880648482e3cbdcba566a?v=2524f070f88880b29f60000c52785ecb&p=2c04f070f88880eaa180d8f32d477a4b&pm=c
- SnowMan: https://github.com/neoforged/Snowman/commit/dba57227544fe247d5cd9284b68679dcce29ce82
SlicedLimes Videos:
- Main: https://www.youtube.com/watch?v=rVrdRT4HjaI
- Pack: N/A
||<@&1067092163520909374>||
Oh boy an exciting second Release Candidate for Mounts of Mayhem, I can't wait to make a high quality update video with all the news! #minecraftemployee
slicedlime works as a Technical Director for Minecraft at Mojang, but the YouTube and Twitch channels are personal projects run entirely in his spare time. This is an unofficial update video th...
๐จ RC2
New version detected: 1.21.11-rc2.
Best changelog ever
every change has a chance not to apply to previous versions. the more this happens the less things will get backported automatically until nothing is
if automatic backpots are not present the community can still do them manually but that relies on both the community doing the backport and the team being interested in reviewing that backport
ok so only automatic one is backporting without community?
thats a good thing to have then
i thought everything is done my team manually
which was not a good idea
but thats not the case
we have to review manually regardless
just in case the automatic did it wrong
Will it be possible to have a NeoForge prototype for the deobfuscated version in the future?
from 26.1 there will be only drobfuscated version
Take your primer: https://github.com/neoforged/.github/pull/37/commits/6619059bd0388209d8a0a0d6e6c1841755367b42
Some utility methods for max coordinate checking
Oh boy an exciting second Release Candidate for Mounts of Mayhem, I can't wait to make a high quality update video with all the news! #minecraftemployee
slicedlime works as a Technical Director for Minecraft at Mojang, but the YouTube and Twitch channels are personal projects run entirely in his spare time. This is an unofficial update video th...
best update video yet, "if you like crashes dont update" xD
literally playable
i mean, more playable than last snapshot at least
clearly a game breaking update, we should revert the change /s
What crash did they fix, out of curiosity?
something related to blockentity management
involves Level and ChunkPos
I'm not being intentionally vague, the code changes are spread over many lines and are just not super obvious
They shuffled some maths
TODO: entities and renderers and other minor package moves
this is for the blog post; can you give me a list of changes @dreamy frost ?
Entities and directly connected classes like variants were moved to more specific sub-packages, the same applies to entity renderers. The other move I remember is Util getting moved to the util package.
I can't look at the code till tomorrow, so that's all I can tell you for now
ok thanks
the primer starts with that so I suppose I won't bother writing a dedicated section
too fast
Minecraft tomorrow
@next wolf
โฆ itโs not Tuesday
rc3
Mojang what you playing at
New version detected: 1.21.11-rc3.
1.21.11 - Release Candidate 3
- Primer: https://github.com/ChampionAsh5357/neoforged-github/blob/primer/2111-or-22/primers/1.21.11/index.md
- Article: https://www.minecraft.net/en-us/article/minecraft-1-21-11-release-candidate-3
- Changelog: https://misode.github.io/versions/?id=1.21.11-rc3
- Notion: https://apexmodder.notion.site/2524f070f88880648482e3cbdcba566a?v=2524f070f88880b29f60000c52785ecb&p=2c34f070f88880f89521c6c66d60fe09&pm=c
- SnowMan: https://github.com/neoforged/Snowman/commit/c8707743ad27c16911980f34716ec06c26082378
SlicedLimes Videos:
- Main: https://www.youtube.com/watch?v=qc0iUNutF5E
- Pack: N/A
||<@&1067092163520909374>||
Third time's the charm - maybe Mobs burning from torches is just a little too much Mayhem?! Here's a quick video about Release Candidate 3 #minecraftemployee
slicedlime works as a Technical Director for Minecraft at Mojang, but the YouTube and Twitch channels are personal projects run entirely in his spare time. This is an unofficial update vid...
(I forgot you also ping, whoop)
re added that crash we removed
/s
When will NeoForge's TODOs for 1.21.11 be done?
Whenever people volunteer their time to do it
There is a primer change, but it's just logic cleanup, so no primer change
HEY
?
?
lolo did respond saying some bug was fixed, but they deleted their message
"The bug that is claimed to be fixed is not fixed."
Third time's the charm - maybe Mobs burning from torches is just a little too much Mayhem?! Here's a quick video about Release Candidate 3 #minecraftemployee
slicedlime works as a Technical Director for Minecraft at Mojang, but the YouTube and Twitch channels are personal projects run entirely in his spare time. This is an unofficial update vid...
T-?? until 1.21.11
if my guess is right and they use the same hour as snapshots it is T-46 minutes
given that limes video scheduled for 2hrs from now
https://www.youtube.com/watch?v=Zqm0v3qaqG4
ima say gonna drop around then
that's 2h 45min
6pm mojang time
youtube just says "premieres in 2 hours" for me
and underneath that the time when it is
you expect me to do time-math when theres a estimate 
an estimate rounded down to the next hour
anywhos so is this the first unobf version? and last 1. version?
not unobf, maybe not last 1. if there is a hotfix
I'm hoping for 1.21.12
ah yeah, mojang has to end it on a funny number like that
It's still possible if they release 2 hotfixes
Soonโข..?
When will the TODOs for NeoForge 1.21.11 be fixed?
New version detected: 1.21.11.
1.21.11 - Mounts of Mayhem
- Primer: https://github.com/ChampionAsh5357/neoforged-github/blob/primer/2111-or-22/primers/1.21.11/index.md
- Article: https://www.minecraft.net/en-us/article/minecraft-java-edition-1-21-11
- Changelog: https://misode.github.io/versions/?id=1.21.11
- Notion: https://apexmodder.notion.site/2524f070f88880648482e3cbdcba566a?v=2524f070f88880b29f60000c52785ecb&p=2c44f070f8888055ad50c3fb70ba0284&pm=c
- SnowMan: https://github.com/neoforged/Snowman/commit/2b20261ce2875fed454fddad2091fb1a126153ea
SlicedLimes Videos:
||<@&1067092163520909374>||
Mounts of Mayhem is around the corner - Minecraft 1.21.11 is set to bring us the Spears, Nautilus, Zombie Nautilus, Zombie Horse, Camel Husk, Parched... and more! Here's the ultimate guide to all the news! #minecraftemployee
This guide was made for Minecraft Java Edition. Many new features and some smaller changes also apply to Bedrock Edition....
Minecraft 1.21.11 brings us plenty of new technical functionality in new Pack versions - including Environment Attributes and Timelines! Here's a comprehensive guide to all the news! #minecraftemployee
This guide applies for Minecraft Java Edition. Technical details are unlikely to apply to Bedrock.
slicedlime works as a Technical Director for...
๐ ๐ ๐
UPDATE
yee
I'm like 7 updates behind 
TODO:
- make resourcepack renaming the spear to lance
finally
I'm super excited for the next snapshot
just now have to wait for neoforge 21.11
Unobfuscated snapshot
next update will be like 2026.1
The toolchain team doesn't have maintain permissions on the gradle mc dependencies repo
yes, that is MC, not neoforge
@devout vault can you fix this?
if there is no hotfix it will be 26.1
ah
yers
oergm which team
Enable authentication from web browsers
Yess I can finally finish my management UI
fixed
[Reference to](#moddevgradle-dev message) #moddevgradle-dev [โค ](#moddevgradle-dev message)seems like it's a problem with the api foojay uses maybe given
Cannot find a Java installation on your machine (Linux 6.11.0-1018-azure amd64) matching: {languageVersion=22, vendor=any vendor, implementation=vendor-specific, nativeImageCapable=false}. Some toolchain resolvers had provisioning failures: foojay (Unable to download toolchain matching the requirements ({languageVersion=22, vendor=any vendor, implementation=vendor-specific, nativeImageCapable=false}) from 'https://api.foojay.io/disco/v3.0/ids/df123e9402ff3c8a379b26a63661533a/redirect', due to: Unpacked JDK archive does not contain a Java home: /home/runner/.gradle/.tmp/jdks/OpenJDK22U-static-libs-glibc_x64_linux_hotspot_22-any#20vendor-228239499774231373457.tmp).
in https://github.com/neoforged/NeoForm/actions/runs/20069974191/job/57570101687
we use java 22?
ah
oh snap, had to look it up. i want J22 just for the "calls before super" improvement
we'll get that if mojang moves to j25 in the next version
๐ค
I feel that, to me, the potential for java25 is much more interesting than the unobf code
probably because there was nothing else past 21 yet? ๐
and we wanted to test that you could change the JRE?
just set it to 25
for those intrested, limes video just went live
https://www.youtube.com/watch?v=Zqm0v3qaqG4
Mounts of Mayhem is around the corner - Minecraft 1.21.11 is set to bring us the Spears, Nautilus, Zombie Nautilus, Zombie Horse, Camel Husk, Parched... and more! Here's the ultimate guide to all the news! #minecraftemployee
This guide was made for Minecraft Java Edition. Many new features and some smaller changes also apply to Bedrock Edition....
one messing with neoform later, starting the decomp for release
Go find those rces then
I wanted 1.21.21 but I don't think there will be that many hotfixes :P


