Omgen

Quick rating

Omgen

No reviews yet

Modpackers util that allows for data-driven customizable cobblegen-like generators.

No Theme
No Genre
QoL & Tweaks
Modpack Customization Tool
API/Library
Mod Loaders
Forge
Minecraft

Community voices

Reviews

Versions
Loading versions…
Match includes

Click once to include, again to exclude, again to clear

Rating Any
Any 0.5 1.0 1.5 2.0 2.5 3.0 3.5 4.0 4.5 5.0
Min
Max
Play Status
Reviews
Time Played
hrs+
Verified developers only
Has developer response
List view
Grid view
Compact view
Sort by
Date
Rating
Helpful
Unhelpful
Edited
Sort ascending
Delete this review?

This removes your review from the project. You can write a new review after.

Review submitted for moderation

Your review has been sent to moderators, who will check that it meets our guidelines before it appears publicly.

No reviews yet. Be the first to review this project!

Get it on

Available Platforms

About

Project Details

Type
Mod
Latest Version
Omgen 0.6.1 - 1.19.2
Authors

For authors

Embed Badge

If you're the author of this project, you can embed a live badge anywhere that supports HTML or Markdown. It updates automatically whenever ratings change.

Custom banner text
ModDex rating badge preview

Use HTML for any page that supports it, or Markdown for README files and Markdown-based descriptions.

Identifiers

Platform IDs

CurseForge ID

Resources

External Links

Source Issues Wiki Discord

About

Description

Omgen is a mod, that uses JSON to create "Generation entries". Those entries consist of a condition (for example, what fluids must interact, where should they be in relation to each other etc.), and the generation itself - all the possible blocks/block tags that could generate with a certain weight.
This mod is intended for use of Forge modpackers. It's not perfectly tested yet - but that will be done in the future.
It supports JEI too - every single generation entry you create will be displayed in JEI:

(Image will be added soon)

I'm a modpacker. How do I add a generation entry?

Just like you would do in a datapack with data/minecraft/recipes/myrecipe.json, put your json file into this directory: data/omgen/gens/myentry.json
Your JSON file should follow this format:

Go to the image link to grab code.

{

"primary": "minecraft:flowing_lava",

"secondary": "#minecraft:water",

"secondary_pos":"Neighbour",

"gens": [

[100, "minecraft:cobblestone"],

[2, "minecraft:deepslate"]

],

"priority": 100

}

Available keywords are (< > is must, [ ] is may):
<primary> : Fluid ID or Tag that represents the main fluid .
[secondary]: The second fluid ID or Tag, that represents the other fluid (may not use, which means no second fluid needed for interaction).
[secondary_pos]: Represents the way liquids must interact in order for conversion to happen:
- "Neighbour", "N", "n" or 1: Newly placed liquid block must be neighbouring with the secondary fluid.
- "Replace", "R", "r" or 2: Newly placed liquid block must attempt to override the secondary fluid block (for example, drop onto it from above).
- "Doesntmatter", "D", "d" or 3: Both variants listed above work.
Defaults to "Doesntmatter".
[above]: Block ID or Tag that represents block ABOVE the interaction point.
[below]: Block ID or Tag that represents block BELOW the interaction point.
[around]: List of block IDs or Tags that represent blocks that may be AROUND the interaction point. Order doesn't matter. Count here must not be bigger than 4. Repetitions are allowed if you want multiple blocks of same kind.
[priority]: Positive integer that represents priority of targeted gen over others in case of conflict. Larger number represents larger priority. Defaults to 100.
[min_height]: Sets the minimal height at which interaction must happen for the generation to occur. Defaults to current world's minimal build height limit if not specified.
[max_height]: Sets the maximal height at which interaction must happen for the generation to occur. Defaults to current world's maximal build height limit if not specified.
<gens>: List of lists, where first element is a weight (how often this block/block tag should appear in relation to others), and second element is Block ID or Tag itself.

If you want to use Tag anywhere, you MUST put # in beginning: "minecraft:oak_log" is a block, "#minecraft:logs_that_burn" is a tag.

If priorities of two or more conflicting gens are equal, only one of these gens occur randomly with equal chances.

A short showcase video that shows how some possible entries work: https://youtu.be/vV8fa0XR4Wc

Screenshots

Gallery

This project has no gallery images yet.

Versions

Files

Relations

Project Relations

More like this

Similar Mods

Suggestions use data such as tags, dependencies, dependents, descriptions, titles, and more to rank how much they overlap with this mod.

On ModDex

Community snapshot

0
Ratings
0
Followers
0
In stacks

By the numbers

Statistics

~1,000
Downloads
Last Updated
Created
Last synced
When ModDex last fetched this project from CurseForge or Modrinth. Every project is re-checked on a schedule, and any project that ships a new file is synced automatically within hours of the release.
New file updates sync automatically
How syncing works