All versions
3.1.0
Release
Mobile Networks 3.1.02 months ago 72
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Unavailable version
Changes
Mobile Networks 3.1.0: Calls and Performance
This update expands Mobile Networks 3.0 with phone calls, number management and call plans, alongside performance optimisations designed to reduce server workload during conversations.
Added
- Phone app with contacts for online players and individual phone numbers.
- Private voice calls using Simple Voice Chat: answer, decline, mute your own microphone and hang up.
- Multiple isolated calls can take place simultaneously, with voice outside calls blocked regardless of proximity.
- Call duration timer that starts when the call is answered, plus a compact call view so you can continue playing.
- Incoming and outgoing ringtones, voicemail, low-signal warnings and an end-of-call sound.
- Missed calls and silent notifications when you retrieve your phone.
- Unique random nine-digit phone numbers, editable from the Server block and shared across all of a player's networks.
- Per-player call minute limits, renewed alongside messages, with a warning when five minutes remain. Both plans are unlimited by default.
- Global network deletion with exact
deleteconfirmation. - Added H+, H and E signal indicators, along with an increased reference range for antennas.
Interface
- Call PiP moved to the centre of the left side of the screen.
- Vertical phone interface with scaling independent from Minecraft's GUI scale.
- Names of up to 15 characters are displayed in full inside message bubbles, with adjusted backgrounds and line wrapping for longer messages.
- Status notifications now adapt to the available screen width.
Optional dependencies
Any compatible version
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:pSUU4Yp7:ZpYIH9dB"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:pSUU4Yp7:ZpYIH9dB"
}

