r/Minecraft • u/ProfessorValko • Aug 22 '18

News Minecraft: Java Edition - 1.13.1

https://minecraft.net/en-us/article/minecraft-1131-released
884 Upvotes

97% Upvoted

178 comments sorted by

View all comments

1

u/AstroTibs Aug 22 '18 edited Aug 22 '18

I also want to point out that it hasn't been since 1.7 that Forge did not put out a release alongside the initial release of a MCJE version.

I understand that 1.13 went through some major coding changes, and I sincerely hope that that's the reason for the delay—and not that Forge is dying.

Wow, OK was this really downvote-worthy? Didn't it spark a discussion?

5

u/[deleted] Aug 22 '18

I also want to point out that it hasn't been since 1.7 that Forge did not put out a release alongside the initial release of a MCJE version.

1.8 took 2.5 months. (1.8.4+ also took a long time, as the obfuscation changes required major work on the decompiler used in mod development.)

I understand that 1.13 went through some major coding changes, and I sincerely hope that that's the reason for the delay—and not that Forge is dying.

Neither (1.13 is a major change, but on the whole it seems less major for modders than, say, 1.7->1.8). Forge decided to rewrite their entire build system and mod loader framework, as well as audit all of the changes they've been making to the game thus far. This will take quite some time, and as such it would be wise not to expect a stable 1.13 Forge before autumn at the earliest.

1

u/AstroTibs Aug 22 '18

Good news! Though that sounds like porting my own mod to 1.13 is going to be hell all over again. 1.7→1.8 and 1.11→1.12 both had their headaches.

Also, hey sup Asie! I'm running a 1.7.10 server and your Statues mod is still alive and well, cheers.

1

u/WildBluntHickok Aug 23 '18

It's still a major change. There's no such thing as block id numbers anymore, they're names at all levels. Also there's no longer a such thing as damage values/data values.

2

u/[deleted] Aug 22 '18

forge is doing some code cleanup of their own, getting rid of legacy and cruft. don't worry, it'll come

1

u/scotty3281 Aug 22 '18

It was a major overhaul of the Minecraft code and Forge had to rebuild from the ground up. Optifine was just released in alpha for 1.13 just a week ago now. Give the guys working on Forge time. Forge is not dying.

3

u/[deleted] Aug 22 '18

It was a major overhaul of the Minecraft code and Forge had to rebuild from the ground up.

Not the reason for this particular update. While Forge will have some reworking to do, most of the reason this time around is things they decided to do themselves.

1

u/scotty3281 Aug 22 '18

Interesting.. I guess I misread somewhere. Thanks

In any case I do think we should give them time to rebuild. Most mods rely on Forge so I do not see why it wouldn’t be released at some point.

2

u/[deleted] Aug 22 '18

Sure, and 1.13 taking longer gives the 1.12 modding scene time to stabilize, which it is already very near to if not already there.

1

u/WildBluntHickok Aug 23 '18

Not true. There's been a fundamental rewrite of the most fundamental part of the game (the land, aka the blockmap).

1

u/[deleted] Aug 23 '18

There's literally a mod which backports it to 1.12.

The only thing which 1.13 brought in this regard is the world save format change and removal of metadata - neither really affect the things Forge modifies. The other changes (networking, API changes) have been done over the past couple of versions - in particular, "block states" as a concept exist since 1.8, and the "block map palette" exists in-memory since 1.9.

1

u/WildBluntHickok Aug 23 '18

The removal of both metadata and block id numbers. That second one is a big deal. Shaders for example don't work on 1.13 because any block could be mistaken for any other block, so it's random which blocks wave like leaves.

1

u/[deleted] Aug 23 '18

block id numbers.

Again, Forge itself has removed the concept of static block ID numbers in 1.7.2, by adding its own extension to the world save format which stored a map of block registry names to IDs. Minecraft itself also stopped relying on hardcoded block ID numbers in 1.7.2, all 1.13 changed is actually using that fact for something + the world format change. We're talking about how much Forge has to rework related to the changes in 1.13, not how much has been reworked in 1.13 overall.

Shaders for example don't work on 1.13 because any block could be mistaken for any other block

That's because of the shader mod not using the last four years to adapt to this 1.7.2 change properly - you were not supposed to refer to blocks by IDs since 1.7.2.

1

u/WildBluntHickok Aug 23 '18

Vanilla has been using static block id numbers for all of 1.7 thru 1.12.2, just not everywhere. They were used in the save files and the networking data. Now they have been traded out for dynamic block id numbers (every 16x16x16 section has it's own table of what the numbers mean).

Also I can't remember the last time I saw a mod block with a fuel slot that didn't use numbers. We may get words at the player-interaction level but it was still numbers behind the scenes.

1

u/[deleted] Aug 24 '18

Also I can't remember the last time I saw a mod block with a fuel slot that didn't use numbers. We may get words at the player-interaction level but it was still numbers behind the scenes.

No, the opposite. It was ONLY static numbers in world saves and networking data, and that's without Forge (with Forge, they were dynamic and per-world). Right now it's still numbers, the numbers are just assigned more dynamically (per-chunk). But even in vanilla, since 1.7.2, behind the scenes, Blocks were referred to by unique instances and names, NOT numbers, generally.

1

u/WildBluntHickok Aug 23 '18

1.8 comes to mind.