#26.1 Snapshots

7303 messages · Page 8 of 8 (latest)

bitter gorge
#

why do you WANT it to be obfuscated?

inner creek
#

"nostalgia"

craggy river
#

Do we have an article?

hazy wind
bitter gorge
#

If we are going that route, obfuscated, no mojang mappings, full stripping

#

lets go

hazy wind
#

Next year

inner creek
#

also maybe #general instead of here

bitter gorge
#

nah we'll be expecting it now

hazy wind
#

Long enough where everyone forgot how the tooling worked

untold cypress
#

This reminds me, I haven't played any of the past snapshots kek

#

well, the past couple that is

craggy river
#

Is there an article for this April Fools?

final pollen
#

ugh them addressing the inventory problem and doing jack shit is so infuriating

round pike
craggy river
#

Found it.

final pollen
arctic sierra
#

I call it "Tiny Blockover"

plucky hollow
#

Ahhh man ofc mojang drops the snapshot right as I leave the house and head for the movie theatre

bitter gorge
#

we should probably make a thread as this is the apirl fools snapshot

final pollen
#

do they care to solve them?

#

because if all they want to do until the end of time is release 4 sulfur cubes per year, i'm storming stockholm (HYPERBOLE)

old pier
#

I think the difference might be in how “pressing” they find it compared to you. Like if it were me I’d be in no rush to overhaul something as foundational as the inventory.

visual basin
#

minecraft is for entertainment purposes only

old pier
#

Like it’s not perfect by any means but it’s also not so bad that it’s gotten in the way of it being the best selling game ever.

craggy river
final pollen
# visual basin minecraft is for entertainment purposes only

yes. but the game has glaring, mounting issues that are not only untouched, but worsened with every disjointed update they release.
of course, these issues are pressing to me because i truly, truly care about this game as a paradigm of game design

#

it gets so many things right

runic anchor
final pollen
#

27 slots is not some holy constant

#

it was decided at a time when the game had way, way less items

craggy river
runic anchor
#

More slots is also more visual clutter and choice paralysis for players

final pollen
#

i'm not saying it's the one solution

craggy river
#

Also, have you considered that a limited inventory size might be intended?

final pollen
#

hence why i designed the luminary like that

craggy river
final pollen
#

what isn't fair, is one glow lichen taking up as much space as 64 iron blocks

craggy river
#

That’s what bundles help with.

raven wharf
final pollen
craggy river
#

In what way? Basically, they allow the mixed slots you seem to be asking for.

final pollen
#

hence why i added the capacity enchantment

craggy river
#

So bundles can hold more than one stack? I could see that being useful, but that would also start encroaching on the niche of shulker boxes—while being even more convenient since you don’t have to place them.

#

It seems to me that, if Mojang wants inventory expansion to be an endgame item, bundles shouldn’t allow that after just hitting a cow and a spider.

final pollen
#

(4 diamonds, and many allays to be effective)

runic anchor
#

Mojang could allow unlimited stack size by inventory as a whole, keep the 27 slots, and add a 1,728 item count limit in corner. So if you have a stack of 100 item A and 32 item B, the corner shows 132/1,728.

less stack splitting for same item in theory while maintaining same max total inventory item count limit we have today.

final pollen
#

and extend the hotbar to 12 slots

compact swan
runic anchor
#

I don’t play mods

final pollen
runic anchor
#

I don’t even play Mc

craggy river
final pollen
old pier
#

Honestly I think I’d just be happy with vanilla adding an auto-sort button

plucky hollow
final pollen
plucky hollow
#

In the movie theatre now won’t be able get the usual snapshot pin out till I get back home

craggy river
# final pollen there

Why 32 and 12? Also, consider that scrolling through the whole inventory would be really annoying.

final pollen
craggy river
final pollen
#

it'd need a whole custom UI that would require significant design work

craggy river
final pollen
final pollen
runic anchor
#

1-0 is 10 buttons

craggy river
craggy river
old wind
smoky sigil
#

the '-' and '=' key 🤣

final pollen
raven wharf
#

You have to type the number 10, 11, 12 in quick succession 🤣

runic anchor
#

1-9 makes most sense as then the slot is numbered automatically mentally. I want slot 8, therefore I press 8

craggy river
#

Except for zero-indexers, of course.

#

If I want slot zero, I have to press 1.

untold cypress
old pier
robust pike
gray frigate
lethal onyx
#

What version is the snapshot based on?

final pollen
lethal onyx
#

Ok someone generate a snowman

old wind
plucky hollow
plucky hollow
#

and from what im reading the fools update is based on 26.1?

untold oyster
#

yea

#

I should probably just do the changes to Shrimp's PR myself and then merge it in

#

unless you want to do that thinkies

plucky hollow
#

this should be the config then?

"april-fools/26w14a": {
        "type": "all",
        "start": "26.1",
        "end": "26w14a",
        "includeVersions": [ "26w14a" ],
        "excludeVersions": [ ]
    }
plucky hollow
#

i just know how to use it blobxd

#

either my script is wrong or theres a bug in snowblower, why is it saying the output branch is dev when it should be april-fools/26w14a

snowblower() {
  local branch=$1 # required

  java -Xmx8G -jar "snowblower-$SNOWBLOWER_VERSION-all.jar" \
    --output "output/$branch" \
    --branch "$branch" \
    --start-over-if-required \
    --exclude "**.nbt" \
    --exclude "**.png" \
    --push \
    --checkout \
    --remote "https://x-access-token:$SNOWBLOWER_PAT@github.com/forgecraft/minecraft-sources.git"
}

snowblower "april-fools/26w14a"
image.png
#

oh no nvm, apprently my network share was not propegating changes correctly
ssh into and nano'ing the file now it used the right branch

image.png
#

got april fools branch pushed for forgecraft but im unsure how to fix it being included into the dev branch

#

fairly certain thats not supposed to happen

#

26w14a - HerdCraft

SlicedLimes Videos:

  • Main: N/A
  • Pack: N/A
plucky hollow
plucky hollow
#

while im at this, since i just ported over the handy manual run workflow from forgecraft to neoforge
gonna have it gen all the other april fools versions and update the readme to match forgecraft (listing them all)
cause why not, its a simple workflow trigger

#

also little in order to gen 26w14a i had to add --cfg to the additional snowblower repo var
to include a config that defines todays april fools version, this should be removed once the PR is updated to include the config

untold oyster
#

I think I'm gonna work on Snowblower then

#

so we can get it into the main branch

#

hey @steady oxide, i'm gonna be poking your Snowblower PR so we can get it in the main branch thinkies hope that's okay with ya

plucky hollow
untold oyster
#

we could check that one line they changed in 26.1.1, if that's still the same

plucky hollow
#

i mean 26.1.1 is a very small hotfix so i cant imagine it being a issue if that history is wrong but would like it to be right

untold oyster
#

it has the fix from 26.1.1-rc-1, so it is confirmed to branch off from 26.1.1

#

(if it didn't include the fix, the commit for the april fools snapshot would've 'reverted' the fix)

plucky hollow
#

aight so the branch config i used (commented on the pr) is correct nice

steady oxide
untold oyster
#

alright thinkies

plucky hollow
#

oh boy i just tried to run latest pr build

root@94ae66d19251:/home/root/snowman# ./run.sh 
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 22.6M    0 22.6M    0     0  7717k      0 --:--:--  0:00:03 --:--:-- 8538k
Error: LinkageError occurred while loading main class net.neoforged.snowblower.Main
        java.lang.UnsupportedClassVersionError: net/neoforged/snowblower/Main has been compiled by a more recent version of the Java Runtime (class file version 69.0), this version of the Java Runtime only recognizes class file versions up to 65.0

guess i need to bump java

untold oyster
#

@bold forge go review the Snowblower PR and/or tell me to dismiss your review

untold oyster
plucky hollow
#

gonna need to remember to do that in snowmans workflows

untold oyster
#

we should probably bump the major version as well

plucky hollow
#

that setups up java iirc

#

uhh

Exception in thread "main" com.google.gson.JsonSyntaxException: com.google.gson.stream.MalformedJsonException: Expected name at line 32 column 6 path $.branches..versions
See https://github.com/google/gson/blob/main/Troubleshooting.md#malformed-json
        at com.google.gson.Gson.fromJson(Gson.java:1375)
        at com.google.gson.Gson.fromJson(Gson.java:1262)
        at com.google.gson.Gson.fromJson(Gson.java:1199)
        at net.neoforged.snowblower.Main.main(Main.java:120)
Caused by: com.google.gson.stream.MalformedJsonException: Expected name at line 32 column 6 path $.branches..versions
See https://github.com/google/gson/blob/main/Troubleshooting.md#malformed-json
        at com.google.gson.stream.JsonReader.syntaxError(JsonReader.java:1800)
        at com.google.gson.stream.JsonReader.doPeek(JsonReader.java:628)
        at com.google.gson.stream.JsonReader.hasNext(JsonReader.java:538)
        at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdapterFactory.java:510)
        at com.google.gson.internal.bind.TypeAdapterRuntimeTypeWrapper.read(TypeAdapterRuntimeTypeWrapper.java:40)
        at com.google.gson.internal.bind.MapTypeAdapterFactory$Adapter.read(MapTypeAdapterFactory.java:200)
        at com.google.gson.internal.bind.MapTypeAdapterFactory$Adapter.read(MapTypeAdapterFactory.java:158)
        at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$2.readIntoArray(ReflectiveTypeAdapterFactory.java:253)
        at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$RecordAdapter.readField(ReflectiveTypeAdapterFactory.java:638)
        at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$RecordAdapter.readField(ReflectiveTypeAdapterFactory.java:567)
        at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdapterFactory.java:516)
        at com.google.gson.Gson.fromJson(Gson.java:1361)
        ... 3 more
untold oyster
#

whoops!

#

messed up a trailing comma

plucky hollow
#

running 2.0.63

untold oyster
#

pushed a new commit, wait for PR build pls

plucky hollow
#

wonder if its worth adding a workflow or something to trigger it to decompile 1 version?

#

to ensure its functioning

untold oyster
#

btw, I changed the 26w14a branch config to this:

"april-fools/26w14a": {
  "type": "all",
  "versions": ["26.1.1", "26w14a"]
}
plucky hollow
#

ah yeah that does look better

#

ay .64 ran without issue

plucky hollow
#

dev is still including 26w14a tho

untold oyster
#

I was about to say

plucky hollow
#

might need to exclude 26w14a specificlly in the dev branch config?

bold forge
untold oyster
#

ah! it's because it follows the conventional (old) format for snapshots, so MinecraftVersion treats it as a snapshot version rather than a special version

#

screm I wish Mojang did it like 26w14herdcraft

plucky hollow
#

that actually makes sense, it is a valid version in the old format blobxd

#

could i also request maybe changing dev "branch" to snapshots in this pr?
fine if we dont just dev is abit misleading on what its doing

untold oyster
#

snapshot, to fit release?
or should I make it snapshots and releases?

#

@plucky hollow thinkies

plucky hollow
#

id say stick to a naming convention
so either all plural or none plural

untold oyster
#

Might as well go plural, then

plucky hollow
#

so what triggers snowmans dev/release ymls cause that will need updating

untold oyster
#

done, pls check

plucky hollow
#

i think?

untold oyster
#

that would be n8n

#

I can do that easily-ish, just poke me once you've done the changes to the workflows so I can apply changes to n8n

plucky hollow
#

could it trigger the new manual i added
just would need to trigger with the right branch name as input

#

thats better than a workflow per branch imo

untold oyster
#

potentially, I'd need to check how to trigger it via the API IIRC

#

err, should it point to Manual Decompile or to regular Decompile

plucky hollow
#

if you can get it to trigger with the input im gonna merge it all down to 1 workflow which would then be decompile
no need to have multiple ymls at that point

#

which i belive should work

#

allows manual trigger and should be callable

untold oyster
#

gonna have to belay that for now, since the creds to n8n is in the vault and it's currently down

plucky hollow
#

im good to delete the old dev/release ymls?

untold oyster
#

I think you should keep them for now, until we can definitely change n8n

#

just so we don't forget

plucky hollow
#

aight, updated them to call the new decompile with the corrected branch names

#

well i can confirm the manual triggering still works

#

tried yeeting the output dir and deleting the remote branch
but that error keeps happening

anywhos thats enough tinkering for tonight

Edit: turns out i had broken caches for that version
yeeted those and the error went away

bright atlas
#

Will anyone try add SSBO to UniformType?

limpid siren
#

Is there simple replacement for BlockRenderer#renderSingleBlock?

inner creek
#

this is not the place to ask support questions

#

#modder-26․1-support

limpid siren
#

Sorry I didn't saw that channel, it was hidden 🤔

inner creek
#

you should go to the "Channels & Roles" section near the top of the channel list

#

and look through the channels list

#

in case you have missed others

#

anyhow, I'm locking this thread. it will be reopened if there happens to be a new hotfix.
any additional discussion of the april fools snapshot can happen in #general

plucky hollow
#

26.1.2 - Release Candidate 1

SlicedLimes Videos:

  • Main: N/A
  • Pack: N/A

||<@&1067092163520909374>||

plucky hollow
steady heath
#

Nice

untold oyster
#

hecc, Snowman's a mess since it relies on sequentiality of commits
so 26.1.2-rc-1 'reverts' all the changes from 26.2-snapshot-1

plucky hollow
#

yeah thats gonna be fun to figure out

indigo venture
inner creek
#

ah, we have no way to specify a branching hierarchy, do we?

#

we could use a heuristic

untold oyster
#

well, technically it would be possible to specify a branch config which does that

#

but that's done afterwards

inner creek
#

that is: if there's a release with the same year.drop, use that as basis, otherwise use the closest release before it

strong wing
untold oyster
#

right! we can compare commits directly

#

Apex, switch it to that squirr

plucky hollow
strong wing
#

Should probably switch snapshot to the 26.1.2-rc-1 commit hash

sharp ermine
#

is it fr just another chat reports fix 😭

indigo venture
strong wing
#

Isn't that due to the snapshot flag

untold oyster
#

that's normal, the snapshot bit gets set on non-releases

indigo venture
#

ah

#

i thought it might be a high bit changing

untold oyster
#

(1 << 30 ) + 307
= 1073742131

indigo venture
#

o a fix for players in spectator attacking

strong wing
untold oyster
#

oh yeah

indigo venture
strong wing
#

*since snapshot would point to the head of the branch

inner creek
#

oop didn't mean to ping

indigo venture
#

the Identifier change seems like just a decomp artifact changing from manual array varargs to varargs

inner creek
#

ah yeah

#

true

plucky hollow
#

well neo updated to the rc just fine

untold cypress
inner creek
#

I'll be honest I don't know wtf the logic for the checkbox tooltip is meant to be, it doesn't look correct

#

the new method checks the contents of the checkbox label,
but the tooltip displays whatever they set as the tooltip

image.png
#

doesn't this break all other tooltips in all other checkboxes?

robust pike
#

I already have one primer to write, when did it become two?!?

inner creek
#

not much to write

#

this change is the only meaningful thing

#

the attack packet is just an exploit fix

robust pike
#

Hmm okay

#

I’ll have to wait a few hours to check myself since snowman commits are wacked

plucky hollow
bold forge
#

I guess mojang can finally do non-linear releases with the new versioning format

plucky hollow
#

@untold oyster you know if i did something wrong in this branch config
it still included 26.2-snapshot-1

"26.1.x": {
      "type": "all",
      "excludedVersions": [ "26.2-snapshot-1" ]
    }
image.png
#

tried making a 26.1.x on fc snowman to exclude 26.2

#

wait.. blobfacepalm its excludeVersions not excludedVersions

untold oyster
inner creek
#

does excludeVersions support patterns?

plucky hollow
#

unsure

inner creek
#

cos you'd ideally want to exclude 26.2.*

plucky hollow
#

yeah i would like to exclude all .2 snapshots

#

but what i have works for now

#

well thats gonna take a little while

inner creek
plucky hollow
#

i could maybe have started from 26.1.1 or something but ehh its running now

inner creek
#

it doesn't know how to start from the last commit it already has at hand?

plucky hollow
#

brand new branch

#

there was no previous run

inner creek
#

but you created the branch from 26.1.1 no?

#

or is there no sharing?

plucky hollow
#

it shares the generated cache files which is why its not decompiling everything

#

but not the output

inner creek
#

ah

#

it works differently than I would have expected / coded

#

I guess the current system is flexible with regards to updating the decompiler

#

my approach would only apply new decompilers to new releases :P

plucky hollow
#

wonder if snowblower is smart enough to drop commits
like if i copied the snapshots branch to 26.1.x before hand
would it be smart enough to drop commits back to 26.1.1 and start from there

#

i know its smart enough to start from most recent commit if possible
but here we need to drop the .2 snapshot

untold oyster
plucky hollow
#

everything changed in the rc, ignore the version and constants files, they change every update

image.png
robust pike
#

Okay, looking like no primer is necessary for 26.1.2

#

Thanks @plucky hollow for the fixed snowman commit

plucky hollow
#

your welcome, i tend to live by, if i want it someone else prob does too
so might aswell make it available rather than just sitting privately on my machine

robust pike
#

It helps a lot since I’m currently at an airport

plucky hollow
#

oh, if i may ask, going anywhere exciting
or coming back from somewhere fun

robust pike
#

Just visited my parents with the gators and now heading back home

plucky hollow
#

gators blobconcerned are yall in florida or something

#

unless you dont mean the animal

robust pike
#

Yeah they’re in Florida

untold oyster
#

...were you a florida man, by any chance /j

robust pike
#

well, I did know a lot of Florida men and women

inner creek
#

I searched "florida man" in the gif search. many regrets.

untold oyster
#

what has been seen
cannot be unseen

plucky hollow
#

better snowman link

quartz spadeBOT
#

New version detected: 26.1.2.

plucky hollow
#

26.1.2 - Hotfix

SlicedLimes Videos:

||<@&1067092163520909374>||

YouTube
slicedlime
Exploits and Checkboxes - What's New in Minecraft 26.1.2?

There's a second Hotfix for Tiny Takeover - 26.1.2. It hasn't got all the exciting news you wanted, but if you're really interested, here's 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...

▶ Play video
plucky hollow
quartz spadeBOT
#
Minecraft: Java Edition 26.1.2

Happy Thursday from the shipping room! We're releasing 26.1.2, a hotfix that addresses a couple of critical issues found in the release....

hazy wind
#

uwu

plucky hollow
inner creek
#

Applying the patch to com/mojang/blaze3d/opengl/GlCommandEncoder.java} failed.

Applying the patch to net/minecraft/client/gui/components/ChatComponent.java} failed.
Applying the patch to net/minecraft/util/CubicSpline.java} failed.
The file targeted by /home/runner/work/NeoForm/NeoForm/src/patches/com/mojang/blaze3d/vulkan/glsl/GlslCompiler.java.patch does not exist.

#

uh, neoform is confused about the codebase

plucky hollow
#

did it run on the right branch pretty sure @wintry flower made a 26.1.x branch for neoform?

inner creek
#

no idea how to check and it's time for me to leave work so I can't look

plucky hollow
#

well i can confirm cloning 26.1.x neoform branch worked fine after bumping to 26.1.2
so id assume it used main instead of 26.1.x
how do we trigger neoform on a different branch?

plucky hollow
#

looks like someone with perms just needs to trigger the update workflow on the 26.1.x branch instead of main where it auto triggered

shy valve
#

Since it seems like we are getting 26.2 and 26.1 updates at the same time, is my understanding correct that the recommended versions for mods is 26.1.latest until 26.2 drops at which point 26.2.latest becomes the version to support?

indigo venture
#

well 26.1.latest will probably still get backports for a while

shy valve
#

right, in the same way i might maintain support for 1.20.1 or 1.21.1, i would expect that. i'm just making sure there isn't some micro-version lock that is being settled on for some reason

indigo venture
#

If a breaking .latest happened we would need to decide on what to do

#

but we can hope that doesnt happen

inner creek
#

there's a chance the community will continue sticking to 26.1.x until 27.1, cos I have heard more than one person express that intention

#

I'll personally do things like always and port to whatever is latest if I have the time

#

and maintain whatever seems worth the effort, which at the moment means 26.1 main, 1.21.1 bugfixing, 1.20.1 occasional pity fixes

#

once 26.2+ release I may fully drop 1.20.1 and 1.21.1 will be the one getting pity fixes

bold forge
#

I think people will stick to 26.1 because of the likely instability of 26.2/3 for a few months because of the vulkaning

inner creek
#

yeah it's more likely now with vulkan being in testing phase, but it may have happened regardless

shy valve
#

🤔 if everyone focused on year.1.x as the sole modding version per year, that would probably make modpacks and mods better overall since you'd have more time to curate and perfect your products for the users.

plucky hollow
quartz spadeBOT
#

New version detected: 26.2-snapshot-2.

visual basin
#

All the Mods' team wants to stay on 26.1 until 27.1 afaik

zenith dove
#

can proably close this one now i suppose

indigo venture
#

again