All versions
0.2.0
Release
Create: Marketplace 0.2.02 months ago 337
Compatibility
Minecraft: Java Edition
1.21.1–1.21.11
Platform
NeoForge
Supported environments
Client and server
Required content
Changes
🏪 Create: Marketplace v0.2.0 — API & Compatibility Update
This update focuses on extensibility, UI improvements, and full integration with mod launchers and third-party addons.
✨ New Features
- Public Developer API: Introduced the
IShopHandlersystem, allowing other modders to add support for their own custom blocks and machines as shops in the marketplace. - Market Events (NeoForge): Added
MarketOfferEventhooks (Register,Registered,Removed). These allow other mods to react to market activities or even cancel shop registrations (e.g., in protected zones). - Configurable Button Position: Added client-side config options for the Marketplace button for players not using EMI. Choose between
CORNER(bottom-left),INVENTORY_SIDE(classic position), orCUSTOM(user-defined coordinates). - Global Database Access: Exposed the
MarketApi.getOffers()method, providing third-party mods with read-only access to the entire server-side market database.
🔧 Fixes & Improvements
- Launcher Metadata Fix: Resolved an issue where the mod version was displayed as
${version}and the logo was missing in Prism Launcher and other mod managers. - Dynamic EMI Integration: The Marketplace button now dynamically adjusts its position to avoid overlapping with EMI’s configuration icons.
- Code Refactoring: All native support for Create: Numismatics has been moved to a default API handler, significantly cleaning up the codebase and improving reliability.
- Documentation: Updated the
README.mdwith full API documentation and instructions for integration via Modrinth Maven.
📦 Technical Changes
- Migrated to official NeoForge and EMI API repositories.
- Full compatibility with NeoForge 21.1.228 and higher.
Optional dependencies
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:O7RTXyyq:EPrhTGdu"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:O7RTXyyq:EPrhTGdu"
}





