Repository navigation
Setup
AbyssCore is published to Maven Local. In AbyssCore's folder, run:
.\gradlew publishToMavenLocal
NeoForge 1.21.1 (ModDevGradle / NeoGradle):
repositories {
mavenLocal()
}
dependencies {
implementation "com.gugas749:abysscore-neoforge-1.21.1:0.1.0"
}Forge 1.20.1 (ForgeGradle). The published jar uses SRG names, like every Forge 1.20.1 mod jar, so it must go
through fg.deobf:
repositories {
mavenLocal()
}
dependencies {
implementation fg.deobf("com.gugas749:abysscore-forge-1.20.1:0.1.0")
}The old coordinates
com.gugas749:AbyssCore:0.0.5and JitPackcom.github.Gugas749:AbyssCore-Remakepoint to the old single-loader code, which is no longer updated. Don't use them.
AbyssCore needs GeckoLib at runtime. If you use the GeckoLib classes (section 12), add GeckoLib to your own build too.
NeoForge 1.21.1 — META-INF/neoforge.mods.toml:
[[dependencies.mymod]]
modId = "abysscore"
type = "required"
versionRange = "[0.1.0,)"
ordering = "AFTER"
side = "BOTH"Forge 1.20.1 — META-INF/mods.toml:
[[dependencies.mymod]]
modId = "abysscore"
mandatory = true
versionRange = "[0.1.0,)"
ordering = "AFTER"
side = "BOTH"side = "BOTH" matters because AbyssCore has client parts (HUD, screens, overlays). Server and client must also run
the same AbyssCore version: AbyssCore's own network channel refuses to connect when the protocol differs.
- Setup: depending on AbyssCore
- Sides, threads and lifecycle: read this first
- Permissions
- Networking
- Synced player data
- Corruption
- Damage
- Continuous effects
- Screen overlays
- Commands
- GUI toolkit
- GeckoLib
- Outside the API package: vanish and config queries
- Complete example: a mana mod
- Limitations, troubleshooting and changelog
- Quick reference