
Discord Presence
Take control of your Discord Rich Presence (RPC) from in game. Click the live Discord card to edit text, images and buttons, use 26 real time placeholders, and set a custom Discord status per server. Client side only. Fabric, NeoForge and Forge.
1.5.0+26.2-fabric
Compatibility
Required content
Changes
Rename "Minecraft" on your Discord status.
- Click the game name at the top of the preview card and type your own. Discord shows it in place of "Minecraft", on the card and in the "Playing ..." line under your name. Leave the field empty to keep Minecraft.
- It is set per profile like everything else, so the Main Menu, Singleplayer, Multiplayer and each server profile can have their own name. Screen and dimension overrides can change it too, or inherit it.
- Placeholders work in it, for example "Minecraft {version}" or "{server}".
- Needs a current Discord desktop app. An older one ignores the name and keeps showing Minecraft; nothing else changes.
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:A8WM17FM:bGmBr7fn"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:A8WM17FM:bGmBr7fn"
}
