Q: What's the story of the Squirrel?
A: ?
Q: Will the support for 1.12.2 end? And will we get another recommended build for 1.12?
A: The support will end once 1.14 gets a recommendet build. And there should be another Recommended build.
Q: Will 1.13.2 be left as it is, or be continued parallel to 1.14?
A: It will propably be left as it is, as 1.13 is to unstable in the first place.
Backporting major features from 1.14 would be to much work, but 1.13 is a good stepping stone.
Q: Will the example project ever do anything meaningful? (Like register a block, or implement an entity)
A: No it will not, it's purpose is to show how to make a mod, everything else depends on the API provided.
Q: Is it possible to/how hard would it be to cache resource loading to improve launch times?
A: Some of that already happens in 1.13 (caching deobfuscated code).
It's hard to know what else can be cached, they are doing the best they can to speed up loading.
Q: What exactly is Forges scope? (Like an energy api would be out of scope)
A: The scope is evolving, but Forge can be considered as a compatibility layer.
It would be better to have Forge do it one time correctly, than having hundret mods doing it differently.
Q: How does Forge work? Original: how does forge work as it does? why can forge almost only let minecraft java be modded?
A:
Q: What happens behind the facades during Game version updates?
A:
Q: What type of tests are used in Forge Development, and what do they cover?
A:
Q: Why is MCP licensing so restrictive compared to other mapping projects?
A:
Q: Who is in charge of PRs and stuff?
A:
Q: Will the major Forge rewrite be finished with 1.14 or can we expect more large changes in the future?
A:
Q: Will the fluid system be rewritten?
A:
Q: Will it be possible to have a "waterlogged" state for multiple fluids? If not, are there plans to make this possible)
A:
Q: Will dimension get a rewrite?
A:
Q: What kind of internal changes have been made to worldgen, and how will they affect modders?
A:
Q: What are the nicest/most convenient changes in Vanilla 1.13/1.14
A:
Q: With the texture update in 1.14 will anything else besides the Forge bucket be affected?
A:
Q: Wouldn't it be a good time to restructure event packages? (Like does the FurnaceFuelBurnTimeEvent really require its own package)?
A:
Q: Will Forges block id limit be removed in 1.14?
A:
Q: Are biome ids unlimited in 1.13/1.14 now? (Were any other ID limits removed?)
A:
Q: Will Forge for 1.14 be compatible with Optifine?
A:
Q: What about the texture issues with the Forge blockstates?
A:
Q: When will Config anotations return?
A:
Q: Will the Forge Animation System be extended to also work with Entities?
A:
Q: May we get a way to allow loading/unloading/reloading Mods after startup.
A:
Q: Will we ever get Mixin (or something similar) in Forge?
A:
Q: Is there a standard on how to coremod with Forge?
A:
Q: Could we get docs for core modding on readthedocs?
A:
Q: What is Forges stance for fixing vanilla bugs? Could fixing such bugs cause side affects?
A:
Q: Why doesn't Mojang code Minecraft in a way that it would be mod friendlier.
A:
Q: Could Mojang integrate Forge into the Java Edition at one point?
A:
Q: Thoughts on the Modding API for the Bedrock edition? Could it overtake us?
A:
Q: Why does Mojang still bother with obfuscators?
A:
Q: Will Forge be able to load Fabric mods?
A:
Q: Could you imagine a partnership with the Fabric devs?
A:
Q: Why can Fabric provide updates/Prs/feature improvements at a faster rate than Forge?
A: