GenLoader

Overview

GenLoader is a modification designed to achieve two main goals: providing players with the ability to customize and add world generation according to their preferences, and simplifying the process of customizing ore generation for other mods. Development began during the period when CoFH mods were unavailable for version 1.8.9, to offer pack creators an alternative solution. Despite subsequent announcements about CoFH releases for this version, the project was published thanks to unique features and a carefully developed API.

Key Features

The mod has several key features:

• API for integration with other mods, allowing easy customization of ore generation
• Disabling standard Minecraft generation with the ability to completely replace it
• Tools for creating custom generation schemes
• Useful commands and data export functions

API for Developers

Developers of other mods are recommended to use GenLoader as a soft or hard dependency. You can register generation schemes disabled by default, which users can activate and configure. Registration of enabled-by-default schemes fully managed by the mod is also supported.

The API allows organizing schemes by categories with saving to separate JSON files for convenient navigation. Blocks can be added to predefined lists for use in clearblock and countblock commands.

Standard Generation Management

For complete control over vanilla generation, you can disable it in GenLoader's configuration and activate corresponding schemes that initially duplicate standard settings but allow further modification.

Data Export

Each time the game starts after initialization, all registered blocks are exported to JSON files with information about possible states. Files are organized by mod identifiers for easy searching.

Example of JSON structure for a block:

Detailed examples are located in the configFolder/genloader/dumps/blocks folder.

Commands

All GenLoader commands start with /genloader and support autocompletion. Currently, two main commands are available.

countblock

Command usage:

/genloader countblock xchunkmin xchunkmax zchunkmin zchunkmax modid:blockname property property value

or

/genloader countblock xchunkmin xchunkmax zchunkmin zchunkmax predefined_list_name (e.g., valuable)

By default, a 5x5 chunk area around the player is selected. The "valuable" list contains vanilla ores and can be supplemented by other mods via the API. To count specific blocks, you can specify their identifier, for example minecraft:coal_ore. Block states are specified through "property-value" pairs.

The example shows specifying the variant property with the diorite value for diorite stone. Details about block states can be found in the exported files.

clearblock

The command is similar to countblock but removes specified blocks from the world. Works only in creative mode.

When using "Junk", all registered ores are preserved. For more precise cleaning, it is recommended to sequentially remove stone, dirt, grass, and other blocks.

Generation Configuration

Available parameters for configuring generation schemes:

• Dimensions - list of numeric identifiers
• Biome types - list of types from the Forge biome dictionary
• Specific biomes - individual biome identifiers
• Minimum and maximum Y coordinate
• Chance - probability of generation in a chunk (for rare ores)
• Frequency - number of generation attempts in a chunk
• Generation type - growing list of available methods:
  • Standard ore generation (most vanilla ores)
  • Weighted generation (lapis)
• Priority - order of generation execution
• Weighted block list - blocks for generation considering their weights
• Replaced block - usually stone, can be dirt and others

Example for emerald:

Additional documentation will be added soon!