Tags
Creators
Details
Licensed ARR
Published 2 months ago
Updated 3 weeks ago
All versions
0.1.3-beta
Beta
CC: HUD Glasses 0.1.3-beta3 weeks ago 1,195
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
- HUD on a pocket computer. Craft
pocket computer + HUD Modemto give it the HUD upgrade — the samehud_glassesperipheral, but portable. Bind your worn glasses to it with sneak + right-click (a plain right-click still opens the terminal). Modem blocks and pocket computers share one id space, so switching sources is just right-clicking whichever you want, and the glasses never come off. The pocket's buffer size is per-session; its id persists. - HUD + Ender Modem in one upgrade slot. A pocket computer has only one slot, so a
HUD-only upgrade would leave it with no networking. Craft a HUD Ender Modem
(
HUD Modem + Ender Modem) and fit it to a pocket computer for a peripheral that is both: its primary type ismodem(sorednet.open("back")works) withhud_glassesas an additional type (soperipheral.find("hud_glasses")finds the same object). The modem half is interdimensional and supportsopen/isOpen/close/closeAll/transmit/isWirelessplusmodem_messageevents. Fitting it uses CC's own upgrade recipe, so the computer's id and files are preserved; removing it returns the item. - New server config
allowPocketHudEnderCraft(defaulttrue) — setfalseand the HUD Ender Modem recipe is removed outright (gone from JEI, item unlisted). Pockets that already have the upgrade keep working. Read at recipe load, so it needs a/reload. - Fixed
getBackgroundColour()returning0when the background was transparent.0isn't a valid CC colour, which broke term-compatible libraries (e.g. More Fonts) that map the result through a colour table and gotnil. It now reportscolors.black;setBackgroundColour(0)still sets transparency.
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:HAKfjoUe:6p53WFd6"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:HAKfjoUe:6p53WFd6"
}

