#1.21.11 Snapshots

4486 messages ยท Page 5 of 5 (latest)

rare lynx
#

26.10, 26.11, 26.20

split oak
#

this is gigas point

#

if u can get the launchers to agree then I think itd be nice

jade plume
#

just do year.major.neo without mc hotfix

hybrid perch
#

what if drops were represented by letters

split oak
#

since launchers have to switch it up anyways

devout vault
#

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

near ice
#

I don't think MC hotfix is necessary yeah

hybrid perch
#

so 26A<hotfix><neo>

lethal ice
#

yeardrop.hotfix.neo !!!

261.0.45 -> 26.1.0 neo version 45

jade plume
#

what if they do eleven drops in one year

devout vault
#

account for double digits

split oak
#

ew

devout vault
#

2601

#

windows build style

split oak
#

and when they drop 100 drops in a year then what ||/s||

whole tinsel
near ice
jade plume
devout vault
#

Papaya-SNAPSHOT

split oak
#

NeoForge Oreo when

rare lynx
whole tinsel
near ice
#

๐Ÿ˜”

devout vault
#

There ARE lots of fruits

#

And for snapshots we use Vegetables.

whole tinsel
#

confusing

echo pendant
split oak
#

lowk i kinda fw the item idea

hybrid perch
#

ngl hex might be better for neo patches lol. you wont get 3 digit versions anymore

split oak
#

its a funny concept

lethal ice
rare lynx
#

a mod may be compatible with the first hotfix and not the second

whole tinsel
#

we will get into debate if this is fruit or vegetable

near ice
#

realistically we should use something like fish for snapshots, I don't think we'll be able to come up with that many vegetables

jade plume
rare lynx
#

the launcher HAS to have you update the mc version

devout vault
#

more engagement ๐Ÿ˜„

#

you underestimate the number of obscure vegetables:D

lethal ice
hybrid perch
#

needs to be minecraft items imo

split oak
#

We wouldve had NeoForge Resin, NeoForge Firefly Bush, NeoForge Dried Ghast, NeoForge Waxed Lightly Weathered Copper Golem Statue, and NeoForge Spear

devout vault
#

NeoForge Cantaloupe Calamari

lethal ice
#

NeoForge B... Blobfish
can't think of a B veggie

frosty knot
#

Beetroot

split oak
#

Butternut Squash

lethal ice
#

pls brain burger is not a vegetable

frosty knot
#

But... banana even if it's a fruit instead

devout vault
#

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.

split oak
#

isnt banana a berry

lethal ice
#

4-component versions, then, as much as they hurt

split oak
#

hotfixes can be breaking for mods

lethal ice
#

26.3.1.132

devout vault
#

They can be, even if they just update a 3rd party library due to a security vuln

split oak
#

but honestly players should never see a hotfix version

devout vault
#

They do, and they do in the Vanilla launcher too

split oak
#

i think if launchers also had u select a drop thatd be great

devout vault
#

You can go and ask them all ๐Ÿ˜„

#

I will not

rare lynx
#

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

near ice
#

yep, point taken

#

four point version numbers it is then

turbid wedge
#

Kinda wish it was snapshot.1 instead of -1, but whatever

devout vault
#

That still parses as semver

next wolf
#

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

devout vault
#

only annoying since the numeric part isn't using the dot-notation for segments

turbid wedge
#

Yeah

turbid wedge
devout vault
#

It says nothing about "should"

#

it just defines an order more formally for dot-separated parts

whole tinsel
#

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

rare lynx
#

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

devout vault
#

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

next wolf
#

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

devout vault
#

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

turbid wedge
devout vault
#

even if you drop the definition of what major/minor/patch do

crystal plumeBOT
#

Maven versioning: 25.10.5 < 25.10.6-snapshot-1

rare lynx
#

yeah.... ugh

devout vault
devout vault
#

so: 25.10.6.1-snapshot-1-<neo-version>

whole tinsel
split oak
rare lynx
#

(.0 not .1)

#

.1 can be the release

turbid wedge
#

It would be nice to be able to use existing libraries for the format is the thing

crystal plumeBOT
#

Maven versioning: 25.10.6.1-snapshot-1-1 < 25.10.6.1

whole tinsel
rare lynx
#

eh, I guess

turbid wedge
#

Although rc < snapshot

rare lynx
#

.1 feels weird tho

#

starting with .1 that is

devout vault
# rare lynx .1 can be the release

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-...

crystal plumeBOT
#

Maven versioning: 25.10.6.1-snapshot-1-1 > 25.10.6.1-rc-1-1

rare lynx
#

oh fuck you mojang

devout vault
#

yep

rare lynx
#

scratch that

#

alpha, beta?

split oak
#

snapshot, alpha, beta

devout vault
#

gradle doesnt even necessarily sort the same lol

split oak
#

you need one for pres

crystal plumeBOT
#

Maven versioning: 25.10.6.1-snapshot-1-1 > 25.10.6.1-alpha-1-1

split oak
#

alpha, beta, charlie geeked

#

idk the greek C

devout vault
#

how does it handle .1

split oak
#

i stole the military one

gloomy axle
crystal plumeBOT
#

Maven versioning: 26.10.6-snapshot-1.1 < 26.10.6.1

lethal ice
devout vault
#

- is not really intended to go in the middle of the version

lethal ice
#

26.10.6-snapshot-1.1

#

.1 being neo build

devout vault
#
    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.
rare lynx
#

we can do alpha, beta, rc

#

alpha for snapshot, beta for pre, rc for release candidate

devout vault
#

So. Good luck getting that in line with what gradle does, which is not the same

rare lynx
#

that solves the ordering between versions at least

gloomy axle
#

thonk what was wrong with <year>.<major>.<hotfix_or_0>.<neo>?

echo pendant
rare lynx
#

now as to where to put it

summer pivot
rare lynx
#

SNAPSHOT has a different meaning

whole tinsel
#

will we get new channel for every drop?

split oak
gloomy axle
#

sure, but neither is solved?

devout vault
#

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

split oak
wise dune
devout vault
#

nothing is decided

#

the mainters will do that later

#

but figuring out options for snapshots/etc. would be good

crystal plumeBOT
#

Maven versioning: 26.11.5 > 26.11-alpha-1.5

devout vault
#

it'd be far easier if mojang had dropped snapshots/pre/rc distinction ๐Ÿ˜„

#

and just did -pre.1 to -pre.n

crystal plumeBOT
#

Maven versioning: 26.11-beta-1.5 > 26.11-alpha-1.5

#

Maven versioning: 26.11-beta-1.5 < 26.11-rc-1.5

rare lynx
#

at least there's that

devout vault
#

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 ๐Ÿ˜„

rare lynx
#

because it's nice to sort them screm

devout vault
#

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

rare lynx
#

in version ranges too

devout vault
#

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 ๐Ÿ˜„

frank hull
#

would probably make sense to align with fabric here and do 26.1-alpha.1 for snapshots

devout vault
#

i dont see any reason to align version numbers with fabric

lethal ice
#

wouldn't that be more confusing?

devout vault
#

other than fabric having a good idea we can copy

frank hull
#

i mean if yours are off by 1 character that would certainly be confusing

#

why not help everyone's brains a little

lethal ice
lethal ice
#

heh.

devout vault
#

26.1-blyat.1

lethal ice
#

26.1.a1pha.1

jade plume
#

I hate how semver owns the trademark on semantic versioning

echo pendant
austere zinc
#

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...

split oak
#

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

vestal tundra
#

my day is ruined

austere zinc
#

They're fixing a problem they created

split oak
#

eh not really

edgy river
#

Every change fits in the major version

split oak
#

hotfixes are not minor updates

#

like 1.16.1 adding the piglin brute

#

wouldve been a drop

#

or part of one

fallow dagger
#

CalVer โค๏ธ

echo pendant
#

0ver squirrelhat

fallow dagger
#

2025ver

wintry fossil
wise lion
#

it seems snapshots versioning is also changing thinkies

lethal ice
#

yes

#

it will be named after the version the snapshots are toward

crystal plumeBOT
whole tinsel
#

i liked the week number scheme

#

but well

lethal ice
#

yeah

jade plume
#

I can actually see what version the snapshot is for by looking at the snapshot version now

ember oracle
#

It was endearing, but effectively no better than git hash

gloomy axle
#

well, it was better in the sense that it wasn't effectively random thinkies

polar kernel
#

(It was smaller than some of the recent drops)

polar kernel
#

So, where the modding will stick then after 1.21.1 btw?

spare hearth
#

neo can't decide that, it's up to individual modders to pick the versions they want to mod

lethal ice
#

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)

polar kernel
#

Since it's the one that finally changes the major number

lethal ice
#

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

polar kernel
#

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)

echo pendant
#

what do you mean by that thinkies

lone cairn
#

I just wait for the day that 1.2.5 becomes popular again

polar kernel
lethal ice
polar kernel
gritty moat
#

why Mojang stole Apple's versioning moyai_wahhhh

lone cairn
#

because apple stole it from something else as well

devout vault
#

Windows 95. ๐Ÿ˜„

lethal ice
#

having year as the version is a very common approach

lethal ice
#

:P

thorn hatch
#

looks at version 2025.12.01

lethal ice
#

that's a date :V

thorn hatch
lone cairn
gritty moat
lone cairn
#

will be dead

thorn hatch
#

@ Mojang
to clarify the first non obfuscated snapshot will be 26.1-snapshot.1 skipping any hotfix 1.21.12

#

1.21.11 Snapshots

muted fable
#

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 harold

lone cairn
#

orrrr

#

neo just creates anoter versioning system

gritty moat
#

It's time to use emojis in versioning

#

Like 25.1+๐ŸฆŠ5

muted fable
#

25ๅนด1ๅผพ5ไฟฎ+็‹5 Clueless

#

@solemn violet amirite?

gloomy axle
solemn violet
atomic fern
#

oboy pre5

#

@next wolf

rare lynx
#

@urban geode sorry tabbed too early

#

<@&1067092163520909374>

#

damn it

stark crane
#

Oooo

stark crane
gloomy axle
#

can we reach double digits pre-releases?

dark nacelleBOT
#

New version detected: 1.21.11-pre5.

lyric shell
#

what is highest pre reached before?

split oak
#

I hope not they have less than a week to ship it

atomic fern
lyric shell
#

ty

devout vault
#

Boo, no rc ๐Ÿ˜„

dark nacelleBOT
#

The Mayhem is Mounting with our fifth Pre-Release for Minecraft 1.21.11, bringing you another round of fixes. Happy mining!Fixed bugs in 1.21.11 Pre-Release 5MC-304409 The enchantment glint is extremely bright on items with animated texturesMC-304593 Charg...

lethal ice
#

so, rc1 tomorrow is still possible

gritty moat
lime oyster
#

Bug fixes and a method addition

spare hearth
#

funniest solution to neoforge needing a new way to structure the loader version - add back the 1 prefix

gloomy axle
#

neo never cared about that anyways tho

polar kernel
plush mortar
#

ie: ubuntu 26.04 is the next release, which will release in April 2026

untold coral
#

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.

split oak
#

wtf ๐Ÿ˜ญ

#

semver starting from the year

obtuse igloo
gleaming ore
#

which is even more wild, lol

untold coral
#

Just with end result of having a hilariously over-inflated version number.

lethal ice
#

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

next wolf
#

So we expecting rc today

#

Must be getting close to release at least

atomic fern
#

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

atomic fern
#

lol, i'm good

thorn hatch
atomic fern
#

is the release date announced?

next wolf
#

Not afaik

thorn hatch
#

I thought it's the 9th confirmed because they need time for a potential hotfix before the winter break

next wolf
#

Guess we will see, but Iโ€™ve not seen any announcements for date

ocean flower
shrewd violet
#

If I am not mistaken

atomic fern
#

didnt know the date was announced in any way

next wolf
thorn hatch
#

so I was right Tuesday

dark nacelleBOT
#

New version detected: 1.21.11-rc1.

next wolf
#

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...

โ–ถ Play video
atomic fern
#

interesting, lz4 lib was swapped out..

#

i wonder what exploded..

devout vault
#

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?

atomic fern
#

i think so?

#

or was it chunks, i thought chunks were gzip

#

yep, region files are lz4

lethal ice
#

compressed nbt were gzip last time I looked, no idea about chunks

dark nacelleBOT
#

As we are getting ready for the release of the Mounts of Mayhem drop on December 9th, today we are shipping the first Release Candidate. If there are no critical issues, this will be the version that we release on Tuesday.ChangesSpear WeaponIncreased the d...

devout vault
#

Now I wonder if old manifests got updated

#

Doesn't look like it

lime oyster
#

No primer changes

next wolf
#

oh hang on thats the wrong link

#

whoops

dapper spade
#

is Neo gonna keep the same versioning format when Mojang changes to the new YY.drop.bugfix format?

jade plume
#

it was being discussed somewhere

dapper spade
#

i'll see if i can find it in search

jade plume
#

ah no it was in the backchannels harold

dapper spade
#

rude /j

twin viper
#

there was a little bit of discussion here, but most of it is back channels

deep wadi
#

We will do abc versioning

#

Starting with A.A.A. Then next Neo version is A.A.B

jade plume
#

we can't do four numbers because log redacters might think the build versions are IP addresses and redact them harold

deep wadi
#

I still think we should and then yell at bad filters as they already will filter JEI

gloomy axle
#

and like a couple other mods at least

solemn edge
#

When will 1.21.1 drop support?

deep wadi
#

never

#

neoforge backporting bot makes backporting PRs very easy and we have breaking change checker bots. Up to anyone to handle making the backport

gleaming ore
whole tinsel
#

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

deep wadi
#

we develop for latest. Up to the person if they want to backport or not. We wont block it basically

twin viper
#

that will break backported patches otherwise

next wolf
#

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...

โ–ถ Play video
thorn hatch
#

๐Ÿšจ RC2

dark nacelleBOT
#

New version detected: 1.21.11-rc2.

grim cargo
#

Fixed a crash

#

Thanks mojang

frosty knot
#

Best changelog ever

dark nacelleBOT
lethal ice
#

ooh rc2

#

we don't get rc2s very often

lethal ice
#

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

whole tinsel
#

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

lethal ice
#

just in case the automatic did it wrong

solemn furnace
#

Will it be possible to have a NeoForge prototype for the deobfuscated version in the future?

whole tinsel
#

from 26.1 there will be only drobfuscated version

lime oyster
next wolf
# next wolf # 1.21.11 - Release Candidate 2 - **Primer**: <https://github.com/ChampionAsh53...

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...

โ–ถ Play video
#

best update video yet, "if you like crashes dont update" xD

echo pendant
#

literally playable

next wolf
#

i mean, more playable than last snapshot at least

atomic fern
#

clearly a game breaking update, we should revert the change /s

worthy ember
#

What crash did they fix, out of curiosity?

lethal ice
#

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

edgy river
#

They shuffled some maths

fallow dagger
#

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 ?

dreamy frost
fallow dagger
#

ok thanks

next wolf
#

could take a look at the primer?

fallow dagger
#

the primer starts with that so I suppose I won't bother writing a dedicated section

dusty fractal
split oak
#

Minecraft tomorrow

atomic fern
#

@next wolf

next wolf
#

โ€ฆ itโ€™s not Tuesday

atomic fern
#

rc3

next wolf
#

Mojang what you playing at

dark nacelleBOT
#

New version detected: 1.21.11-rc3.

echo pendant
#

<@&1067092163520909374>

next wolf
#

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...

โ–ถ Play video
echo pendant
#

(I forgot you also ping, whoop)

next wolf
#

oh sci already pinged

#

...

echo pendant
#

ah well kek

#

let people be surprised

low kraken
solemn furnace
#

When will NeoForge's TODOs for 1.21.11 be done?

dark nacelleBOT
#

Today we are shipping Release Candidate 3 for 1.21.11, addressing three issues discovered after the recent update.Happy mining!Fixed bugs in 1.21.11 Release Candidate 3MC-304790 Transparent item models are rendered incorrectlyMC-304797 Zombie nautiluses ge...

deep wadi
lime oyster
#

There is a primer change, but it's just logic cleanup, so no primer change

solemn furnace
#

HEY

lone cairn
#

?

deep wadi
#

?

next wolf
#

lolo did respond saying some bug was fixed, but they deleted their message

vestal tundra
#

"The bug that is claimed to be fixed is not fixed."

next wolf
# next wolf # 1.21.11 - Release Candidate 3 - **Primer**: <https://github.com/ChampionAsh53...

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...

โ–ถ Play video
thorn hatch
#

T-?? until 1.21.11

lethal ice
#

1 hour probably

#

maybe 2

#

well -10 minutes

thorn hatch
#

if my guess is right and they use the same hour as snapshots it is T-46 minutes

next wolf
thorn hatch
#

6pm mojang time

next wolf
#

youtube just says "premieres in 2 hours" for me

thorn hatch
next wolf
#

you expect me to do time-math when theres a estimate blobxd

thorn hatch
next wolf
#

anywhos so is this the first unobf version? and last 1. version?

thorn hatch
#

I'm hoping for 1.21.12

next wolf
#

ah yeah, mojang has to end it on a funny number like that

lethal ice
#

yeah

#

I wish they had got to 1.21.21

#

but oh well

split oak
#

I want 1.21.13 ๐Ÿ™

#

lucky number

polar kernel
next wolf
#

Soonโ„ข..?

lethal ice
#

35min

#

I guess

solemn furnace
#

When will the TODOs for NeoForge 1.21.11 be fixed?

devout vault
#

I mean PRs welcome ๐Ÿ˜„

#

Or are you expecting a roadmap/timeline?

dark nacelleBOT
#

New version detected: 1.21.11.

next wolf
#

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....

โ–ถ Play video

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...

โ–ถ Play video
lethal ice
#

๐ŸŽ‰ ๐ŸŽ‰ ๐ŸŽ‰

thorn hatch
#

UPDATE

dusty fractal
#

yee

gloomy axle
#

I'm like 7 updates behind kek

thorn hatch
#

TODO:

  • make resourcepack renaming the spear to lance
dusk egret
#

finally

turbid wedge
#

I'm super excited for the next snapshot

dusk egret
#

just now have to wait for neoforge 21.11

turbid wedge
#

Unobfuscated snapshot

lone cairn
#

this is not a snapshot

#

oh wait

stark crane
fallow dagger
#

The toolchain team doesn't have maintain permissions on the gradle mc dependencies repo

lone cairn
fallow dagger
#

@devout vault can you fix this?

thorn hatch
stark crane
devout vault
devout vault
dark nacelleBOT
#

Today Mounts of Mayhem charges into Minecraft, bringing a new weapon to wield, mounts to tame, foes to face, and strategies to master! Challengers await beneath scorching suns, night skies, and deep in the oceanโ€™s depths โ€“ and each clash will demand a fres...

thorn hatch
#

Enable authentication from web browsers
Yess I can finally finish my management UI

devout vault
crystal plumeBOT
#

[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

lethal ice
#

we use java 22?

rare lynx
#

the neoform tests do

#

for reasons

lethal ice
#

ah

dapper spade
#

oh snap, had to look it up. i want J22 just for the "calls before super" improvement

lethal ice
#

we'll get that if mojang moves to j25 in the next version

dapper spade
#

๐Ÿคž

lethal ice
#

I feel that, to me, the potential for java25 is much more interesting than the unobf code

devout vault
#

and we wanted to test that you could change the JRE?

#

just set it to 25

next wolf
# next wolf # 1.21.11 - Mounts of Mayhem - **Primer**: <https://github.com/ChampionAsh5357/...

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....

โ–ถ Play video
rare lynx
#

one messing with neoform later, starting the decomp for release

edgy river
lethal ice
#

I wanted 1.21.21 but I don't think there will be that many hotfixes :P