#1.21 Snapshots
4351 messages · Page 5 of 5 (latest)
Most things show mm/dd/yyyy because I'm in America, but my settings are all yyyy-mm-dd
and the region settings didn't let me choose separate options for date format and time format
and number format
aaaaaaany second now
I just recently reworked my shader system to bake expressions relying on dynamic values into custom bytecode and interpret it on a gpu driven simd interpreter, which then populates a cbuffer and have a static shader read it
Bam, consistent input format and dynamic value support
Rule 5 is make sure Tree Generation has been changed within the last 6 months
And highly performant too
I want to see which bets are off 🙃
Still gotta rework it to make use of mesh shaders though
Instead of a traditional vertex pipeline
I am one of the masochists that love rendering

there's a "window of correctness", actually; at any given point in time a maximum of two bets are closest to it
so I could add a "if release happened now these people would win" display
Wait, multiple winners?
no, only one will win
oldest bet always takes priority
lemme see if I can implement that
Is it still possible to do weird stuff in the new vertex system?
like undersized quads
hey gegy could you guys release in 16 minutes so I win the release bet /s /j
I have no idea what this term means
like baked quads with less than 32 entries
Is Sweden +1 or +2 atm?
+2
yea it's currently 16:28
Like France
20 minutes on my bet, please Mojang xD
why is jinja not behaving 
imagine if they got wind of us doing this betting thing, and are rigging it /jk

Did any mojang employee place a bet?
Note: Minecraft 1.21 will probably be released between 5pm and 7pm, as this is Mojira's maintenance period.
I don't believe so :P (times in UTC, you do your own conversions)
oop, just caught a bug: seems like I was prioritizing newest instead of oldest
Good catch
that should now be fixed
and now the person with the closest bet gets a green timestamp
if release were to happen Right Now, schurli would win
apparently my mental idea of "ascending" and "descending" was wrong :p
You should get a bot added here so you can read nicknames and roles
Roles so you can prevent Problem Causers from placing bets
And you could add the winning role automatically too
they're not gonna let me do that lmao
at best I'll get a webhook
sci's already said, and I agree, that the role handing out should be done manually
as for nicks and roles, I could probably read those with an additional oauth scope
might look into it later
(you can PR to Camelot)
for what :p
The rest could be automated with a bot though. The needed permissions would be very minimal (default perms only)
Does that have an HTTP API already?
Because reading nicknames off it would require an API
it can at least read (aka send get requests) afaik
like I said, I'm fairly sure I could do this with an additional oauth scope
I doubt it tbh
That would allow you to read nicknames and roles for a user on every server their in
where?
that is correct, which is why I'm not doing it right now
removed it and replaced it with the single green one, since that's more informative
I swear I turned ping off
The green's not there for me
c'mon release now
?????????? why did the green move to that other person
it should still be on schurli
Have you not pushed that yet?
nope 16:52:30
the exact mid point
wait 17:00:00
it briefly moved to gravyboat
Why can everybody else see this green indicator?
I still don't see what you mean
looks fine to me
Everybody but me and you ig
nope
Maintenance break (13.06.2024) from 17:00-19:00 CET. Bug tracker will be unavailable during the Maintenance break.
ugh, being lazy with my sorting is biting me in the ass
Me when I make a fancy trailer announcing the release, and then don't release it
A decent amount of tomfoolery
good thing firefox has a disable cache button
There, it's on CDA
it's gonna come out at 11:59 in the last timezone that is still Jun 13th
I've gotten called CDA at least 3 times, fun fact
so near sci
Its unlikely itll be me unless they are legit hitting the button right now 😄
sci was a day too early
likely to release in 3-10 minutes
I too, because it changed it back
either that or an hour more :P
I may have to manually override the winner, since there's another bug and it's gonna take me a bit to fix
Can you please add an option to sort by time bet on?
nothing like seat-of-my-pants hotfixes in production :3
Well, there's been no #mojira activity, so id be surprised if that was it
(you have to go to cache settings and delete the cache manually, then refresh)
Then again, not surprised at the same time, because that would be something mojang would do day of
After not doing an rc2
while you're at it give me my credit for RC1 lol
ginger be sure to check when people made the bets so nobody who made the bet after mojang workday started today wins
everyone's a critic
you have the f*ing role
I have a solution; it's extremely cursed, but it should work
Your site's great
for now. in a few minutes It will only be a memory

thanks :D
I think it's gonna be CDAGaming
when, exactly, did the workday start :p
It's already too late for him
Poke Sci to make a "Previous Snapshot Guesser Champion"
:P
Yee, its already too late for me I think
nope that bet was made in the last few minutes
Oh hey, it is out
Oh o.o
<@&1067092163520909374>
1.21
https://mdcfe.dev/mc-changes?ver=1.21
https://www.minecraft.net/en-us/article/minecraft-java-edition-1-21
oop
why not v2?
There is v2?
When does the site poll for releases?
Fuck I missed it by 2 hours
none
and with this I'm locking the channel
okay, t-minus one minute until the winner check runs

wha, wait a second, we still need a release
Why locking it 
that implies the release has been built since 10:24 CEST
Justbtename
6.5 hours ago lol
https://bugs.mojang.com/browse/MC-273281?jql=(assignee is not EMPTY AND project %3D MC AND "Confirmation Status" !%3D Unconfirmed AND resolution %3D Unresolved )AND fixVersion is EMPTY A list of all the bugs that will be fixed in a future version
uhhhhh
doesn't the webhook have higher perms than @everyone
New version detected: 1.21.
Wouldn't be opposed
I should prooooobably note that the site uses the release time to calculate a winner
just happened lol
so. yeah
bruuuuh xD
New version detected: 1.21.
it's so random
it should've seen the release by now
you won that bet was made after the mojang workday today started
hang on, I think something's broken...
why are you so insistent on this?? I don't understand what the point is
ITS HERE
Ah nice, yippee 😄

so nobody does any last minute betting just minutes before it actually releases
Which is what happened here
Good bot 😄
Well an rc is literally a candidate to be a release
I can't say I understand why that's a bad thing
it's also going to suck to implement because the site doesn't know when release day is
I would have to manually key in a lockout time, and I don't want to do that
unlike any other release we know what day the release is coming, so it's unfair except to people who wait to vote. I could in theory wait until it's released then put my vote in at the exact minute and win on a technicality
Any changes not present in the RCs?
or retroactively disqualify bets
no
Old screenshot (wrong channel :()
that doesn't look good https://github.com/neoforged/Snowman/actions/runs/9502090963/job/26189261161
this I can and probably will do, at least for ten minutes around the release time or so
1.21 is out go to #general or #squirrels-🦊 for general discussion about it, to #modder-1․21․1-support for support for modding it and #neoforge-github for bugs
hmm, i cancelled it
christ schruli wait a damn second, we haven't even released yet
why are you so excited to lock the thread
also Peter making a new thread already
we don't need the snapshot discussion thread when we have a released version
my brother in christ hold it up until release LMAO
@hard ivy you may want to check this 
We still use the thread for finalizing the port
hey I like making threads
And I didn't lock this
Once the 1.21 PR is merged/released would be the point in time to lock this
the pattern so far was to use the snapshot thread until we are out from kits and have it re-based to the latest decomp
while neoform is doing i'll go update the blog post and remove the mention of enum extensions
why?
cause they aren't merged?
The snapshot thread will be locked when we have a neoforge for this release
that is how we did it last time
yes, that's why i don't see why schurli was so insistent on locking it, feels more like wanting to do something for the sake of procedure 😛
i love the waiting stage of the process
we do have snow at least now
https://github.com/neoforged/Snowman/commit/52ba843fed609963cfc897f777d0e7da6fcc360e
Also added it to the pinned message
lo, #1250829990195626115
why's that thread in #general
why did that push, Maty cancelled the Action
neoform failed
Also
at dev branch not having a similar commit
one comp error? really?
No code changes, so primer is now public: https://gist.github.com/ChampionAsh5357/d895a7b1a34341e19c80870720f9880f
J22 failing
that's the release branch
are there seriously no code changes?
Excluding the version bumps, yes
why not just rename the thread 
what on earth then
or is discord dumb enough that it can't be done
Which was the Action you cancelled, think it managed to finish and push just before you cancelled it
i don't understand how the release is failing but the rc isn't
nothing more than these
pulled in a newer build of J22?
Isn't 1.21 using J21?
what do you mean
We build neoform on multiple JDKs
Ah
alright, @austere ocean who's getting the role

starting the local decomp for the port
around 4pm (cest) so if you decide to give it to someone else I would completely understand that
I think, because you made the bet so close to the time when a good portion of bets were made, it would be slightly unfair to those who bet in advance 
anyone have any other opinions?
Since we didn't establish any rules beforehand, I think it's fine
it's just a role :p
Personally, it does feel a bit unfair, but if Ginger says the bet was made like hours ago rather then same time as bot,
then that's fair enough 😄
Give it to both
However, bets on the day of should not count in the future
the only rule I had established was no insider info 
Also agreed with this, if we know the exact date, then bets should be blocked on said date
Just make sure the rules on when betting is allowed are clearer for future
well we also don't know the date of most of the releases
majors are the only days we know the date of
yeah that seems fair enough
{ _id: ObjectId('666b0125088240ce0e7dbaa0'), bet: ISODate('2024-06-13T15:03:00.000Z'), created: ISODate('2024-06-13T14:24:37.530Z'), release: null, user: Long('336764548017291265') }
there's your answer
Yeah, but usually it's wednesday
that looks borked lol
they have not had such a consistent track record recently
after all it's betting
For snapshots up to release candidates, sure we dont know the date with absolute certainty -- but for most of MCs releases, they have always given a date
And yeah that does look borked
created: ISODate('2024-06-13T15:16:47.662Z'),
that's the important bit
Especially with timings, as they've been doing releases much earlier in the morning this time around
but y'all are, imo, taking this far too seriously :p
it's just a role
why on earth did NG make me download 5 minutes of assets
i already had them downloaded
I'm going to make the backend disqualify bets placed within three hours of when the release is detected (and add a note to that effect to the site)
is this acceptable :p
that sounds fine to me
^^
do we apply that retroactively 

eh. I'll lean towards lenience and give em the role anyway
hooray!
Yippee

give me a few hours and I'll have the site unborked, reality keeps interrupting me
waiting on decomp is so boring
Also, I'll mention for CF authors: CF staff is adding in the 1.21 label for you guys, give them a bit and It'll be there 😄
can't say I didn't expect it to break, at least
I can delete the Neo repo to make things exciting for you
would adding a leaderboard be a bad idea :3c
I believe I suggested that a few days ago, for the amount of times being correct, or for a general accuracy rating system 😄
no rush 
anyway, it's nearing midnight for me, so I might go to bed within the next hour or so
decomp done
pushed update to port branch, let's see if it builds
#neoforge-github message can someone else test this 
[Reference to](#neoforge-github message) #neoforge-github [➤ ](#neoforge-github message)oh then it's simple
CI finished running on Java 21
protections lifted
branch pushed
tag pushed, branch made default
(re)starting build 
lol
i accidentally pressed delete in #builds
instead of copy link
eh, it's fine™️
fresh releases take a while 
f5 goes really hard
well its cool that neo keeps its pase with the version release, i think that everyone likes that
habemus 21.0.0-beta
now lets wait for stable #1 
You might be waiting a month
close the thread
there's a note on stability in the blog post
so yes it'll probably be a month or longer
but not shorter than a month
Has anyone tried making the main page on the website list the latest Neo of each MC version instead of just the latest and legacy?
Which blog post?
Found it
well, we always have https://projects.neoforged.net/neoforged/neoforge
On that page yes, but I mean the regular non-projects. homepage thing
e.g. something like this:
makes no sense to have 1.20.2/.4/.6 there
almost no one will be using them starting today :P
Fair. Mainly trying to think what a decent way could be to quickly access the latest of each MC verison without having to fiddle around with dropdowns that aren't on the main page.
Question, why can’t we stick a drop-down selector there?
And you select the Mc version and the orange buttons switches to that version’s downloads
Drop-down is on latest by default
Hmm, that could be interesting
mods may take some time to update, which could keep people on .6 for a bit
i really hate the redundancy, if you want to manually download a non latest, you just need to click here
Hmm, maybe I'm just feeling strange about Other Versions being below the legacy version considering they're newer than the legacy one
I love how quick this release was. Feels great to have my mods all updated already.
so how long do we have to continue making breaking changes like #1183818213134446742

