Leaderboard
-
cpw
Members6Points195Posts -
LexManos
Forge Code God3Points9283Posts -
CreativeMD
Members1Points100Posts -
Minecraftschurli
Members1Points2Posts
Popular Content
Showing content with the highest reputation on 12/21/22 in all areas
-
6 pointsDon't ask awkward questions. Mojang code is PERFECT, and NEVER NEEDS FIXING.6 points
-
3 pointsAs a note, the plan is to have 1.19.3's first RB be January 1st. Because I like that date and it gives people time to look at things during Christmas break. So this poll will stay open until that time and be what we do.3 points
-
1 pointI feel like making the .0 version LTS is risky because judging by the past .0 versions contain more bugs than other versions. My suggestion would be having the latest version of the previous major version (1.18.2) as LTS and the latest of the current major version (1.19.3) as current and adding the previous minor version (1.19.2) as a sort of MTS that gets unsupported as soon as a new version (major or minor) drops.1 point
-
1 pointIt feels quite weird. I think it would be really confusing for people to treat 1.19.2 and 1.19.3 as separate versions. On the other hand from a programming perspective it makes a lot of sense. I wish all modders could just update to 1.19.3 asap and we forget about 1.19.2. There are quite some changes, but it is doable.1 point
-
1 pointI'd say in general that dropping 1.18 is the better option. Not because 1.18 is an old version that needs to die, but rather because I think the LTS should serve as a gap between technical changes between versions. It probably seems more likely for someone stuck on 1.19.2 to have trouble moving onto 1.19.3 if the LTS version didn't stick with it and provide updates that can help the modder in question bridge their mod to the newer version. But yeah, incredibly scuffed versioning schema from Mojang nonetheless.1 point
-
Issue with the ModelFix mod. Check you have the latest version then contact the mod author.1 point
