Tags
Creators
Details
Licensed CC-BY-NC-ND-4.0
Published 2 years ago
Updated 2 weeks ago
All versions
2.3.0b-neoforge-1.21.1
Beta
Paradigm 2.3.0b (neoforge 1.21.1)2 weeks ago 108
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Dedicated servers only
Changes
Paradigm Changelog
2.3.0b
Holograms (new)
- Added holograms, using native Text Display entities: billboard mode, alignment, scale, shadow, background, opacity, see-through, line wrapping, spacing, view distance, refresh behavior.
- Added click/attack interactions with actions, cooldowns, and conditions.
- Added temporary holograms (
/hologram temporary). - Added per-viewer rendering for placeholders and visibility rules (vanilla packets only, no client mod).
- Added
/hologram,/holo, and/paradigm hologramcommands. - Added a full dashboard page: display, visibility, interaction, runtime status, temporary holograms, placeholders.
Tablist (new)
- Added a native tablist: header/footer, entry ordering, per-world overrides, live placeholders.
- Added a cached, non-blocking metadata resolver with debounced/coalesced refresh.
- Added
/paradigm tablist status|refresh|reload. - Added a dashboard page with inline validation for world overrides and refresh interval.
Permissions
- Fixed command permission discovery missing commands registered late by other mods/loaders.
- Fixed a crash when debug logging isn't configured.
- Added internal state versioning for cache invalidation.
Commands
- Fixed
/kickspamming its log line and stalling instead of disconnecting the player. - Fixed
/enchantusing wrong enchantment IDs on some versions.
Build
- Pinned ForgeGradle to 6.0.54.
- Removed the unused legacy code folder.
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:s4i32SJd:j1cVa3kl"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:s4i32SJd:j1cVa3kl"
}

