All versions
1.21.1-v1.3.2
Release
Sol's Party System 1.3.23 weeks ago 75
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
Sol's Party System v1.3.2
Fixes & Improvements
- Fixed party player cards reverting to vanilla Minecraft XP levels after traveling through portals or changing dimensions when Sol's Leveling System is installed.
- Improved Party PvP protection. Party members and their owned tameable pets are now properly protected from friendly fire while Party PvP is disabled, including attacks, projectiles, harmful abilities, crowd control, and other player-triggered effects.
- Fixed several abilities bypassing friendly-fire protection, including skills that ignite, drain air, reduce health or absorption, or apply damage through non-standard methods.
- Fixed player-ticked weapon auras and other harmful effects being able to affect party members despite Party PvP being disabled.
- Fixed weapon skills damaging the user's own tamed pets while Party PvP was disabled.
- Improved party-friendly healing and beneficial effects. Player-owned effects will now properly prioritize the user and their party members instead of unintentionally affecting unrelated players.
- Fixed protection for owned creatures interfering with environmental damage and natural mob lifetimes.
- Improved Simply Swords & Epic Fight compatibility. Normal, Dark, Nullification, and configurable banner effects now consistently follow party friendly-fire rules.
- Improved party cleanup. Players who remain offline for 5 minutes are automatically removed from their party. Reconnecting during this grace period will prevent removal.
- Fixed empty public parties appearing in Browse Parties. Public parties with no online members are now hidden, and parties whose final member remains offline for 5 minutes are fully closed.
- Fixed party invites being refreshed by repeated clicks. Repeatedly clicking an invite will no longer reset its pending state or spam the invited player with notifications.
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:PjTIldTa:TPQVn9s1"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:PjTIldTa:TPQVn9s1"
}

