Tags
Creators
Details
2.1.1
Compatibility
Changes
ModNVote v2.1.1 Changelog
This release improves ranked-choice result transparency and fixes misleading result presentation for closed ranked polls.
Added
- Added full round-by-round IRV result reporting for
RANKED_SINGLE_WINNERpolls. - Added final-round tally reporting so players can see the actual winning round, not just first preferences.
- Added exhausted ballot reporting where applicable.
- Added eliminated candidate reporting for each IRV round.
- Added manual result republishing command:
/modnvote publishresult <pollId>
This allows admins to republish corrected closed-poll results to the configured Discord witness webhook.
Changed
- Ranked-choice in-game results now clearly show:
Poll winner
Final winner tally
IRV Round Breakdown
First Preference Round
Final Round
-
Discord closed-poll messages now distinguish between:
- the declared winner,
- the final IRV round,
- and the full round-by-round IRV breakdown.
-
Replaced misleading first-preference-only “Result Summary” output for ranked-choice polls.
-
In-game wording changed from:
Winner after transfers
to:
Poll winner
for simpler player-facing language.
Fixed
- Fixed misleading ranked-choice output where the winner was correct but the displayed vote counts only showed first-preference totals.
- Fixed ranked-choice result display so users can now verify how transfers led to the final winner.
- Fixed empty ranked polls incorrectly being able to resolve to a winner when no ballots had been cast.
Notes for server admins
If you previously published a ranked-choice result that only showed first-preference totals, you can now republish the corrected result after upgrading:
/modnvote publishresult <pollId>
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:yTxmV2La:bk5bhj3y"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:yTxmV2La:bk5bhj3y"
}

