Tags
Creators
Details
All versions
0.4.0-beta.1-neoforge-26.3
Beta
NeroAgriculture 0.4.0-beta.1 - NeoForge 26.32 weeks ago 10
Compatibility
Minecraft: Java Edition
26.3
Platform
NeoForge
Supported environments
Client and server
Changes
Item tags for tag-keyed pricing, and a crop-tower output threshold event. Neroland Core only: no new dependency (NeroEconomy is not needed for any of this).
Added
- Item tags for data packs and economy mods to key on, so a tag-keyed commodity follows every new
item with no code:
#neroagriculture:fragments(the five tier fragments; the component-keyedresource_fragmentstays out because its identity is in item components),#neroagriculture:fertilisers(fertiliser, speed and yield fertiliser) and#neroagriculture:biofuels(biofuel canister and bucket). The fragments and biofuels already sit inc:fragmentsandc:biofuels. - Threshold event
neroagriculture:tower_outputon Neroland Core'sThresholdEventsbus. Scope = the dimension id (never a player); value = items harvested by every crop tower in that dimension in the last in-game hour (1,000 game ticks of server game time, a rolling window in ten 100-tick steps); threshold = new configcrop_tower.output_event_threshold(default 512, 0 = off);risingistrueonce when the total reaches the threshold andfalseonce when it drops back below. In-memory only, so a restart announces nothing. Usable by NeroQuests'custom_eventand NeroEvents.
Deprecated
AgricultureApi.PremiumGoodsProvider,AgricultureApi.PremiumGood,AgricultureApi.PREMIUM_GOODSandCompatContracts.registerPremiumGoodsProvider. They were never implemented or read, priced in energy rather than credits, and keyed on a player. Price NeroAgriculture goods through the item tags above instead. Kept so existing callers still compile.
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:Vczal5Xy:EtVgiWGB"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Vczal5Xy:EtVgiWGB"
}

