When's 1.16? #253
Comments
|
Yes, but not yet. MCP mappings aren't encompassing enough right now - we need better mappings or we'll have to do a lot of redundant work that we'll just have to reverse later. |
|
aaah ok, thank for the information & responding. Its very much appreciated. :) |
|
Just curious, is there a rough eta? |
|
I'm afraid not.
|
|
What need to be coded in terms of MCP mapping. Is that another project that could use help ? |
|
MCP's proprietary nature makes it difficult to contribute to. We have no choice but to wait for their mappings to improve - and that likely won't happen until after 1.16.2 is released. |
|
Now that 1.16.2 has been released is it likely that a 1.16+ version will be released sometime soon? |
|
Unfortunately not, 1.16.2 was a far worse release for modding-related changes than anyone expected. |
|
What has made 1.16 so difficult to work with? |
|
It's mostly mappings changes and the refactoring of some features by Mojang - it's much harder to hook into some parts of Minecraft without writing coremods now, so the Forge team is having to look into expanding the APIs they add to facilitate mod development. |
|
once a recommended version of forge is release whats the effort needed to bring Journeymap to a new version |
|
There's no way to predict that. |
|
Maybe I missed something, but I thought the current way to use mappings is using MCP-Reborn, which supports minecraft up to version 1.16.3, right? https://github.com/Hexeption/MCP-Reborn |
|
MCP Reborn seems like it's probably not relevant for us, considering we have to work with Forge (which isn't really compatible with alternate mappings at the moment) |
|
Will older versions of JourneyMap work on Minecraft 1.16+? |
|
No. |
|
I just checked forge download page for 16.3 and they released a recommended version recently 34.1.0 . Are the mcp binding done in a good enough way ?
Jean-René (JR) Bourque
… Le 27 sept. 2020 à 07:09, Gareth Coles ***@***.***> a écrit :
No.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
|
I'll have to talk to mystic about it, but he's super busy atm |
|
Any updates? |
|
Afraid not |
|
Hate to be the person to ask but with the final version of MC (1.16.4) being out (until next major version 1.17), any updates on Journey Maps release? |
|
what about if you move to fabric? I know it would requiere you to take new learnings but there's a lot of documentations since yarn and mixins are FOSS, also you can get help from the fabric project discord server |
|
I would support a move to Fabric, and it's something we've talked about at length. That said, it would be a monumental undertaking — there's a whole ton of work to do in order to achieve something like that and, while it's true that a lot of the things we do could potentially be made easier via the mixin system, it's not a small job. On the other hand, such a project would probably need to be a complete rewrite — I guess it could be done if we had the right team. As for the politics of the issue, I'm actually one of the moderators on the Fabric Discord server (come say hi sometime!). Fabric provides an environment that is far less developer-hostile and far more future-proof, and I would support anyone that wishes to move to it. |
|
Please do not move to Fabric...there are tons of mods on 1.164 Forge (we have over 200 in our modpack) and Journey Map is the superior minimap mod. It is very frustrating that Fabric/Forge is splitting the modding community. |
|
It was always going to happen. The solution is definitely not trying to make developers stick to the... very broken status quo, though. What we really need are projects like Patchwork and Yarnforge that make writing mods that target both modloaders easier (or simply convert mods between each), but we're a long way off. That said, a mod like JourneyMap would be far easier to maintain using Fabric's mixin system. Either way though, nobody really has any time to work on it, and we're unable to bring any more people in without @techbrew-mc's approval either - not a lot can be done right now. |
|
aren't there also solutions for mixin in Forge (I thought I had seen one or two mods about it on curseforge) Also, sorry to be the annoying person to ask again, but any chance of an eta for a 1.16.4 version by now? |
|
99% of our problems are caused by:
We never provide ETAs unless we're close to a release - at this point we'll likely be skipping 1.16. Regarding mixins, yes, they're possible in Forge, but Lex hates them so much that you get banned for talking about that in most parts of the Forge community. |
that's sad to hear. JM was always the best Map mod out there.... What is the best alternative then? |
|
Personally I use Just Map for Fabric. Not sure what the current meta is like with Forge. |
|
did the copyright holding developer give any reason for not open-sourcing the mod? |
|
The last time I asked, it was because the project is basically a bunch of jenga code - it's a seven year old project that's never had a full rewrite, and he wanted to rewrite it before open-sourcing it so that the code would be at a standard he was happy with. Unfortunately, since then, he's been unavailable. |
|
Currently Xaero's World/Mini Map is the default Forge map mod for 1.16.4. |
|
Maybe consider waiting for Patchwork to start 1.16 ;) |
|
1.16 version is out and available to download on curse. |
Any chance for a MC-v1.16+ forge version ?
As the current choices for maps are not cutting it right now.
The text was updated successfully, but these errors were encountered: