Tags
Creators
Details
1.0.0
Compatibility
Required content
Changes
Proxcord: Cross-Platform Proximity Voice Chat Proxcord is the ultimate bridge for Minecraft server communities. It brings immersive, proximity-based voice chat to Spigot servers, finally allowing Minecraft Bedrock and Java Edition players to communicate seamlessly through Discord.
Whether you are exploring a cave together or building a massive base, Proxcord ensures that no one is left out of the conversation just because of the platform they play on.
🚀 Key Features True Cross-Play: The first real solution for Bedrock and Java players to talk in the same proximity-based environment.
Discord Integration: Uses a dedicated Discord bot to handle the audio, ensuring high quality and low latency without taxing your server's hardware.
Spatial Audio: Voices get louder as you get closer and fade away as you move apart, creating a truly immersive survival experience.
Geyser & Floodgate Compatible: Designed specifically to work alongside GeyserMC, making the connection process seamless for Bedrock users.
Automatic Syncing: Automatically links players' Minecraft accounts to their Discord accounts for a "set it and forget it" experience.
🛠️ How It Works Proxcord tracks player coordinates on your Spigot/Paper server and communicates that data to a Discord bot. The bot then adjusts the volume of players in a voice channel in real-time based on their in-game distance from one another.
📋 Requirements Server: Spigot, Paper,Purpur(NOT STABLE)(1.20+)
Dependencies: GeyserMC & Floodgate (for Bedrock support)
Communication: A Discord Server and a Bot Token.
📥 Getting Started Upload the Proxcord plugin to your plugins folder.
Invite the Proxcord bot to your Discord server.
Configure the config.yml with your bot token and channel IDs.
Start talking!
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:Hauz1asI:wEmuNRRH"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Hauz1asI:wEmuNRRH"
}

