Tags
Creators
Details
Licensed MPL-2.0
Published 3 years ago
Updated 2 months ago
All versions
1.4.0-r5.3-forge
Release
Euphoria Patches 1.4.0-r5.3-forge2 years ago 10.2K
Compatibility
Minecraft: Java Edition
1.21–1.21.1
1.20.x
1.19.x
1.18.x
1.17.x
1.16.x
1.15.x
1.14.x
1.13.x
Platform
Forge
Supported environments
Client-side
Changes
The entire changelog can be found here: https://euphoriapatches.com/changelogs
Changes
- Updated to Complementary Shaders r5.3 + Euphoria Patches 1.4.0
- Auto Settings Updater:
- The Mod will automatically detect the latest settings version you have (let's say from EP 1.3.2) copy that file and rename it to work with the newer Euphoria Patches version (1.3.2). Will not do anything if you already have a 1.4.0 settings file.
- Auto Base Shader Settings Transfer:
- If you have never used EP before but have used the normal Complementary versions and have settings files there, the mod will automatically copy the latest version of that settings file and have it automatically be applied to Euphoria Patches!
- Auto Shader Applier:
- The Mod will detect if you were using an older version of Euphoria Patches and only then apply the new version in Iris/Oculus/OptiFine settings automatically
- A config file was added where you can disable all te new features if desired
- Forge now works from 1.13+
- Update Checker:
- The mod will now check if a new version is available by checking against the latest release tag in https://github.com/EuphoriaPatches/PatcherUpdateChecker and modify the current in use Euphoria Patches version to display an update message!
- Auto Rename Old Versions:
- Old Versions of EP will automatically be renamed so users know which version to take if they can't read the version number (yes, that happens)
- The entire code got cleaned up and rewritten and made more modular and organized
- Changed the mod versioning to be the same as the shader versioning
Optional dependencies
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:4H6sumDB:nqyDtliP"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:4H6sumDB:nqyDtliP"
}



