Tags
Creators
Details
Licensed ARR
Published 5 months ago
Updated yesterday
All versions
1.0.4.1
Release
Custom Skyboxes 1.0.4.1yesterday 12
Compatibility
Minecraft: Java Edition
26.3
Platform
NeoForge
Supported environments
Client-side
Client and server
Changes
CustomSkyboxes 1.0.4.1
A fix release for how servers remember what they have set, plus a few additions.
Fixed
- Clearing a sky or a rift on a server made it come back on the next join. What a server keeps is now kept straight in every direction: clearing for one player cancels a sky that was set for
@ainstead of having it replayed to them, clearing for@aalso wipes what single players had, and setting something again drops any clear that was remembered for it. - Clearing from your own client is now told to the server, so a sky you take off stays off after a rejoin. Before, only the server's own command was ever noticed.
New
animate <type> stopends only what is playing on that type and leaves the rest alone:/customskyboxes animate night_sky stop.animate stopon its own still ends everything.- Looping animations are part of the sky now. One started with
loop=trueis kept by the server, for@aor for one player, and starts again on its own when the player joins. One that does not loop is still a one-off and is never replayed. - 12 more rift shapes, 37 in all:
crescentcloverinfinitysquircleburststar4star12keyholehourglasseggarchclaw. - 10 more live effects for
animate rift, 18 in all:collapse(sucked shut, then thrown open),supernova(a long gathering and then everything at once),heartbeat,riptide,strobe,siphon,rupture(three more tears, shards on each),warp(two whole turns while it stretches),eclipse(out, then back brighter) andcascade(ring after ring). All of them take the samecolorsizestrengthlooplayerdelayspinshakeglowflash. modelposXandmodelposYmove a GeckoLib model inside a rift across and up, in degrees, to line it up next tomodel_scale.
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:PJflrYWw:WMQnQesN"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:PJflrYWw:WMQnQesN"
}

