Tags
Creators
Details
Licensed MIT
Published 3 years ago
Updated last year
All versions
1.1
Release
Alfheim 1.13 years ago 267
Compatibility
Minecraft: Java Edition
1.12.2
Platform
Forge
Supported environments
Client-side
Server-side
Client and server
Required content
Changes
Changelog File (Include Previous Versions)
Alfheim Version 1.1 Changelog - 2023-11-18
Now depends on Red Core 0.5
Now depends on MixinBooter 8.6
Changed
- Lighting engine will now schedule updates no matter if that chunk is loaded, which is different from vanilla but potentially fix areas lighting being weird when going far away
- Made the logic for capping the client updates per frame dumber which should fix performance drops on lower end hardware (Fixes #20)
- Made all head-cancels overwrite instead
- All overwrites now make the scope of the overwritten methods
publicto prevent access level conflicts at runtime - Updated the in game description to the new short description
- Updated to Red Core 0.5
Fixed
- Fixed a crash at start on Mohist (Probably any Bukkit implementation)
- Fixed skins not working with Alfheim paired with some other mod (we don't know which)
- Fixed unescaped unicode characters in the description
Internal
- Switched to CurseUpdate for update checking
- Switched to gradle-buildconfig-plugin entirely for project constants
- Switched to Gradle Kotlin DSL
- Switched to Adoptium
- Moved logo to the root of the resources module
- General cleanup
- General typo fixing
- Added missing since tags
- Deprecated
PooledLongQueue
Removed
- Removed access transformed as overwrites can already do the job on their own
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| Alfheim-1.1-sources.jar | Unknown | 54.54 KiB |
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:srzJgOEn:NYuYUXU8"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:srzJgOEn:NYuYUXU8"
}



