Tags
Creators
Details
Licensed ARR
Published 3 months ago
Updated 3 months ago
All versions
1.3.0
Release
TradeHub Markets 1.3.03 months ago 10
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.8–1.21.11
Platform
Paper
Changes
Version 1.3.0
Leveraged Long/Short Positions 📈📉⚙️
- 📈 Long Positions – bet on rising prices. Freely selectable investment amount and optional leverage (configurable, e.g., 2x/5x/10x). Profit is generated when the price rises.
- 📉 Short Positions – bet on falling prices. Profit is generated when the price falls; loss occurs when it rises.
- 🎚️ Fully configurable leverage system – leverage can be enabled/
disabled globally; maximum leverage level is adjustable; leverage
can be allowed or restricted per asset category (
positions.leverage.*). - 📋 New "Open Positions" menu – displays asset, symbol, position type, entry price, current market price, investment amount, leverage, current profit/loss (absolute and %), and opening time for each position. Open, close, refresh, and filter by asset or position type directly within the GUI.
- 🛡️ Automatic liquidation – positions are automatically closed
server-side once the configured loss threshold relative to the
margin is reached (
positions.liquidation-threshold). - 📊 Server-side calculation automatically accounts for bid/ask spreads, trading fees, current market price, volatility, trading hours, and disabled assets.
- 👨💼 Admin configuration (
config.yml→positions:): Long/short trading can be enabled individually; leverage enabled with a maximum value; minimum capital per position; liquidation limit; trading fee for positions; and allowed asset categories. - 🌐 Web Dashboard: New "Open position" section on the asset detail page, as well as a complete position overview with live profit/loss in the portfolio section.
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:SAOUAfpN:hkSQQliM"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:SAOUAfpN:hkSQQliM"
}

