1.4.2-forge
Compatibility
Changes
So.. I've decided to make a backport for 1.20.1 Forge.
Changes:
- All functionality from NeoForge 1.21.1 now on Forge 1.20.1
- Logic of server variables works different (not bug but feature, ha-ha)
- Methods from NeoForge converted to Forge methods
There are still could be some minor bugs but version is stable (there are also a hidden Mindless mechanic. Some unique bug that not a bug xD)
RU: Итак.. Я решил сделать бэкпорт для 1.20.1 Forge.
Изменения:
- Весь функционал от NeoForge 1.21.1 теперь на Forge 1.20.1
- Логика серверных переменных работает иначе (не баг, а фича, ха-ха)
- Методы от NeoForge конвертированы в Forge методы
Тут ещё могут быть незначительные баги, но версия стабильная (а ещё есть скрытая механика с Безрассудным. Такой уникальный баг, который не баг xD)
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:TSr6Tv7A:8diKIeEu"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:TSr6Tv7A:8diKIeEu"
}

