Tags
Creators
Details
Licensed LGPL-3.0-only
Published last year
Updated 4 days ago
All versions
1.10.2
Release
Dream Displays 1.10.2 Release — Paper 1.21+last week 770
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
1.21.x
Platforms
Folia
Paper
Purpur
Changes
Highlights
- Experimental addons: you can build your own
Fabric/NeoForgemod orPaperaddon - A much simpler experimental developer API
Client
Features
- Experimental addons:
- Mark a class with
@Addonand register it withDreamDisplays.register(...) - Works on the client, the server, or both
- Everything an addon subscribes to is cleaned up automatically when it is disabled
- Mark a class with
Improvements
- Much simpler developer API:
- One entry point,
DreamDisplays, instead of a set of service keys - A display is now a live object:
display.volume = 0.5f,display.play(),display.seek(30_000) - Act on many displays at once:
DreamDisplays.displays.near(x, y, z, 32.0).pause() - Subscriptions are grouped in a session and closed together; per-display ones end when the display is removed
- Commands return a clear result, and a removed display never crashes your code
onReady { }lets your code wait untilDream Displayshas loaded
- One entry point,
- API for moving displays:
DreamDisplays.placementstellsDream Displayswhere a display really is, and it is drawn, heard, clicked and culled there - API for addon data on displays (
display.customData) and public display position math - The API is published as a separate artifact with sources, and now contains only what integrations can use
Fixes
- API methods no longer have unreadable names in some cases
Server
Features
- Server API for
Paper,FabricandNeoForge - Support experimental addons
Optional dependencies
Any compatible version
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:4IIKQyBu:od9F3U52"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:4IIKQyBu:od9F3U52"
}

