Tags
Creators
Details
1.0.1
Compatibility
Required content
Changes
Aeronautics Delivery Quests (ADQ) - v1.0.1 Changelog
Core Mechanics & Standalone Architecture Standalone Mod: Stripped all FTB Chunks, Teams, and Library requirements from compilation, config, and runtime scripts, making ADQ 100% independent.
Safe Air Spawning: Re-engineered physical spawning to check solid surface footprints and ensure 100% empty air columns. Cargo spawns 3 blocks in the air and drops cleanly under gravity.
Vertical Spawning Safety Fallback: Added a sky fallback (spawns cargo 4 blocks above solid ground) if flat ground is unavailable, preventing clipping into village structures/ground. Removed legacy floating grass block placements.
Custom Quest JSON Configurations Admins JSON Pool (custom_quests.json): Added a dedicated GSON database at config/aeronautics_delivery_quests/custom_quests.json (auto-generates example templates on startup) allowing custom names, descriptions, mass classes, NBT templates, and rewards.
Mix Ratio Tuning: Added customQuestsChance (default 0.5) double config parameter under ADQConfig to set the percentage ratio of custom JSON quests versus procedural generation. Instant Hot-Reloads: Integrated JSON reloader directly into the /adq reload command and chest-GUI reload button for real-time refreshes without a server restart.
Exploit Protection & Chest-GUI Command Panel Anti-Loot Balance: Swapped minecraft:netherite_block in the Heavy schematic with minecraft:polished_deepslate and programmed the manager to overwrite legacy/OP config files on startup. Guaranteed all default schematics use exactly simulated:rope_connector.
Chest-GUI Redesign: Restructured the board to limit quest maps to slots 0β17 (respecting maxActiveQuestsPerBoard). Converted the bottom row (slots 18β25) into a command dashboard for Reissuing Compass, Cancelling Contract, and OP-level 2 Admin Commands (Generate, Delete All, Reload).
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:tEL1KmWB:VhEHGU8f"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:tEL1KmWB:VhEHGU8f"
}

