Minecraft 1.20.2 update
KosmX opened this issue ยท 23 comments
Minecraft 1.20.2 is out, update when?
There are only some breaking change in this update, most importantly a configuration phase.
This will allow fixing some reliability issues, but it will break compatibility with ViaVersion
Also, I'll either drop Forge support or migrate to NeoForge (TBA)
Emotecraft also needs an internal refactor, it'll take a while, but will make future ports easier.
No official ETA for this, but it'll take a while.
Sorry for being a moron who knows very little about code, but every time I try to build the 1.20.2 branch I get an empty .jar with only the Manifest file inside. Any chance I could get some help or a working .jar to use?
Hi, I understand that the 1.20.4 version is still unfinished, but still, when using emotions on the server, the texture of the player's head breaks. (Quilt client, Purpur server). In single player mode, everything works without problems. Would like to see the fix as soon as possible)
Mb, it's was broken because I'm used custom head shaders...
I'll work on updates bext week, but emotecraft might take a little longer because I have to rewrite a few parts of its networking and GUI
I'll work on updates bext week, but emotecraft might take a little longer because I have to rewrite a few parts of its networking and GUI
I suppose it's time to update it for 1.20.4 already :D
@KosmX still no approximate release time for 1.20.2?
I'll work on updates bext week, but emotecraft might take a little longer because I have to rewrite a few parts of its networking and GUI
Give it all time, we know already that it takes longer based on this answer.
So, after a half of the year we still don't have any news about 1.20.2-1.20.4 emotecraft update lol
What about 1.20.4? Seems now it's the latest version of the game and all plugins/server jars use it, but not outdated versions
1.20.2 tree has 1.20.4 support
also when I build it itself I had issue what I can't play singleplayer (just loading stops at 100%)
1.20.2 tree has 1.20.4 support
sorry, I should rename the branch but i don't want to
When I write this, Fabric finally works, neoforge ... f*ck forge. I'll make it work, but I don't like using the legacy code called Forge or NeoForge.
neoforge
This should explain why you can't create a common network:
https://hackmd.io/@neoforged/rkQ8WCW_T#Analysis
I saw that you did "hacks" to neoforge, but I don't think it makes sense as long as they break compatibility with the Dinnerbone's protocol
Forge hacks aren't network protocol workarounds (I had to do that in Forge, but NeoForge is already much better)
The hacks are against the NeoForge API. The API isn't really ready for advanced usage (like the server needs to store some info from the client)