Tags
Creators
Details
1.1.0+1.21.5+fabric
Compatibility
Required content
Changes
(Neo)Forge Support
Particle Effects (and my other cool mods) will now support (Neo)Forge mod loader!
Why?
All my mods were released exclusively for Fabric, as my projects always used Yarn mappings.
After the recent news about the end of support for Yarn mappings, it made sense to switch to the official Mojmap.
Since mappings are no longer an issue, it's fairly easy for me to add Neo(Forge) support.
Which versions will be supported?
Only the main ones, the ones most played.
Currently, I plan to support:
- Forge: 1.20.1
- NeoForge: 1.20.1 1.21.1 1.21.10
If there are many requests to add another popular version to support, I (maybe) will add support for it.
Does this affect Fabric users?
Not really, it's the same for you; the highest priority is still given to Fabric support.
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:PLAGcSFJ:StcJDCjs"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:PLAGcSFJ:StcJDCjs"
}



