Links
Tags
Creators
Details
Licensed MIT
Published 5 days ago
Updated 2 weeks ago
All versions
1.0.0-neoforge-mc26.2
Release
EverLight 1.0.0 (NeoForge 1.21.4)2 weeks ago 5
Compatibility
Minecraft: Java Edition
26.2
Platform
NeoForge
Supported environments
Client-side
Changes
EverLight v1.0.0 リリースノート / Release Notes
🇯🇵 日本語
Minecraft 1.21.4 (26.2) 向け EverLight v1.0.0 へようこそ!
✨ 主な機能・ハイライト
- 💡 ワンタッチ視界全開 (Fullbright): 洞窟や夜間、水中でもワンキー(デフォルト
G)で即座に昼間同様の明瞭な視界を確保。 - 🧘 画面を汚さないクリア設計: 暗視パーティクル粒子や右上のバフエフェクトアイコン、画面点滅は一切表示されません。
- 🎚️ 明るさレベルの自由調整 (1.0 〜 10.0):
- スライドバー + 数値入力ボックス による直感的な設定 GUI。
- 控えめな明暗補正(
1.0)から完全な全開暗視(10.0)までレベルに合わせて動的に可変設定可能。
- 🔌 ローダー標準設定メニューとの統合:
- NeoForge: 組み込み Mod リスト画面の「設定 / Config」ボタンから遷移。
- Fabric: ModMenu の GUI メニューから遷移。
- 💾 設定の自動永続化: 変更した設定は
config/mc_ever_light.propertiesへ自動保存されます。
📦 動作環境
- Minecraft バージョン: 1.21.4 (26.2)
- Java バージョン: 25+
- 対応 Mod Loader: NeoForge (26.2.0+), Fabric (0.19.3+)
🇬🇧 English
Welcome to the initial release of EverLight for Minecraft 1.21.4 (26.2)!
✨ Highlights & Features
- 💡 Instant Fullbright Toggle: Toggle full daylight visibility in caves, underwater, and night with a single keypress (Default
G). - 🧘 Clean & Invisible: No potion particle effects, no HUD status icons, and no screen clutter.
- 🎚️ Customizable Brightness Level (1.0 - 10.0):
- Interactive Slider + Numeric Input Box configuration GUI.
- Adjust brightness dynamically from subtle enhancement (
1.0) to maximum night vision (10.0).
- 🔌 Seamless Integration:
- NeoForge: Configurable directly from the built-in Mod List option screen.
- Fabric: Fully integrated with ModMenu GUI.
- 💾 Persistent Configuration: Settings are saved automatically to
config/mc_ever_light.properties.
📦 Supported Environment
- Minecraft Version: 1.21.4 (26.2)
- Java Version: 25+
- Loaders: NeoForge (26.2.0+), Fabric (0.19.3+)
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:uIOnStsQ:fUxojvEs"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:uIOnStsQ:fUxojvEs"
}

