i509VCB

v1	official	intermediary
CLASS	a	net/minecraft/class_1
FIELD	a	Ljava/lang/String;	a	field_1
FIELD	a	Ljava/lang/Throwable;	b	field_2
FIELD	a	Ljava/util/Map;	c	field_3
FIELD	a	Ljava/io/File;	d	field_4
METHOD	a	()Ljava/lang/String;	a	method_1
METHOD	a	(Ljava/io/File;)Z	a	method_2
METHOD	a	(Ljava/lang/String;Ljava/lang/Object;)V	a	method_3
METHOD	a	(Ljava/lang/String;Ljava/lang/Throwable;)V	a	method_4

i509VCB

        - Forge mods are remapped, patched, and loaded as full-class Fabric mods.
        - Forge mods can be placed in the "mods" folder directly without any issues.
        - Forge mods are not replaced, but instead the patched mods are kept in a cache somewhere else.
What we need:
        - Two new stages that happen before mixins are applied: "discovery" and "addition" (todo better name for the latter)
        discovery: 
                - Happens after all valid Fabric mods are put on the classpath, but before non-fabric mods are added to the classpath
                - Patchwork specifically needs an option to exclude certain jars from being added to the classpath.
                - Called "discovery" because this is the stage both Patchwork and Spungbric will use to find the jar files they need to do something with.
        addition:

i509VCB

PLEASE NOTE:
The information here may be outdated.
For up to date information please see the new repository here:
https://github.com/i509VCB/Fabric-Templates/blob/master/README.md

Fabric Example Mod 
[Java, Groovy DSL] 
[Loom 0.2.6, 1.15.1]
[CC0 1.0 Universal]
Includes Fabric API

i509VCB

package me.i509.tests.worldgen;

import java.util.Random;
import java.util.SplittableRandom;

import org.bukkit.Material;
import org.bukkit.World;
import org.bukkit.block.Biome;
import org.bukkit.block.data.BlockData;
import org.bukkit.block.data.type.Snow;