This API has been archived and will not be updated. I may come back to it in the future, though.

Check out the homepage here!

Why should you use Creo API?

Creo API addresses three main issues not typically covered by other library mods.

• De-centralization of features, resulting in unnecessary similar or duplicated code from different mods.
• Tedious aspects of development that take time away from implementing fun, unique features.
• Expanding the powerful, yet lacking, worldgen & datapack system.

What's included in Creo API?

Here is a list of features implemented:

• Over 50 new Block, Item, Entity Type, Enchantment, & Biome tags
• Expanded version of BlockSettings & ItemSettings for easy modification

Vanilla is phasing these out in favor of the components system in 1.20.5+

• Utilities to edit vanilla blocks, items, & entity types
• Various Feature/Structure Placement, Density Functions, Placers, & Surface Rules to assist in worldgen
• FastNoise implementation
• Entity Attributes such as Block Place/Break Cooldown, Max Air, Climbing Speed, etc
• POI State & Block Entity Injection
• Customizable Entity-Block collision interactions
• Customizable Enchantment Targets
• Extensions to Blocks & Items for further customizability
• Even more small features
• And more to come!

Creo API targets both modders & datapack creators, aiming to provide both with useful features.

In order to optionally reduce file size, all modules are available to depend on separately.

We aim to be a higher-layer API on top of Fabric API (for modders) and Minecraft (for modders & datapack devs).