MOD API THE FOREST 2018 MOD
MOD API THE FOREST 2018 FULL
MOD API THE FOREST 2018 MODS

Nested list support, should have all the same capabilities as the existing system.

Annotations for config will kind of stay.

Event to get config values from a TOML object.

TOML will also be used for the modloader.

Format will be TOML (Luckily it's not YAML).

They would like FluidStack to be immutable and be more like ItemStack.

There will probably be a new entry/event for registering liquids.

Might not make the rewrite straight away since mojang is not 100% done with the new fluid system.

They need to probably rethink everyone about how fluid works.

World generation is now THREADED!! (Not multi threaded).

Grum: don't use 2^31 blockstates please hehehe, you are going to have a bad time.

Grum: Recipes should be reloadable in 1.13.

They want a world cleanup tool that prunes dead ids.

Block id will persist even if you remove the block that had that id, leaving dead id's.

Bad practice to have enable/disable flags for items/blocks in config.Tweakers removed, New loader system uses serviceloaders.

MOD API THE FOREST 2018 MOD

No Annotations processor, is dead and the mod annotation only have one value.

Java will always be the language that Forge supports.

Language support should only have to be -> Require a lang support mod from curse, and start developing.

Clojure/Kotlin/Javascript/Scala/Groovy support planned (loaded with loaders specified in the mod toml file).

They don't know if it's feasible yet (probably referring to syncing datapacks to the client).

Not much info on how datapacks will be utilized.

Forge might take over to init gears/nuggets/iron and all those common occuring ingredients that have tags.

(Forge did it first, mojang is thieeeeves)

OreDict will be deprecated, Replaced with the new tag system.

Forge team is looking for someone to do rendering.

Grum on entity data models: Not planned by mojang atm.

The more modders that adapt 1.13, the better.

1.13 is cooler and more enticing than 1.8 ever where when moving from 1.7.

MOD API THE FOREST 2018 FULL

Forge's official stance is always use the latest version, but 1.12 will have full support until 1.13 have a stable version that Lex is happy with.Forge will have a full audit for every line of code, so a lot of things are breaking. Breakings changes in forge for 1.13? Yeeeeees.Login needs support for longer handshakes since the block registry is ~16 times larger, and needs to be synced.

Giving more feedback on how close it is to connecting to the server.

More Event driven networking for simplmpl.

DataFixers: Could theoretically support porting modded worlds from version to version, but will probably not be a thing.

MOD API THE FOREST 2018 MODS

Lot of new World generation util that should help for mods like Twilight forest & Betweenlands.

Vanilla command system rewritten, a lot more structured.

1.13 updates to LWJGе…ѓ which has support for multithreaded rendering, so they still want someone who does rendering to speed that up.

Multicore systems should receive a big speed increase (for the loader?).

Mod system should not scare bukkit plugin devs so much after the rewrite(but forge will never be bukkit/sponge since it's not an abstraction).

New system might support swapping mod versions while the game is running.

JavaScript system to modify base classes.

New coremod system for 1.13, coremods are necessary for forge, but people tend to overuse them right now.

Forge will receive a full audit for 1.13, going over all of the classes for redundancies.

Java 10 & 11 support depends on Mojang using it.

The mod loader carries a lot of technical debt, which is the reason the load speed is a bit slow, they're working towards improving the performance of the loader.

cpw is rewriting the mod loader and it's going to be merged into 1.13 forge.

Notes should be taken with a grain of salt as it's just notes I took during the livestream and since I'm no contributor to forge I cannot attest to the accuracy of facts.

Mod api the forest 2018