Links
Tags
Creators
Details
1.5-26.x
Compatibility
Required content
Changes
PeaceSMP 1.5 for Minecraft 26.1-26.3
On Minecraft 26.x
- A second jar for Minecraft 26.1, 26.1.1, 26.1.2, 26.2 and 26.3, next to the one for 1.21 to 1.21.11:
PeaceSMP-1.5-26.x.jar. Java 25, Fabric Loader 0.18.4 or newer, Fabric API. Text Placeholder API 3.x if you use placeholders. - The same mod: every feature, command, permission, config key and message is the same as in 1.5 for 1.21.x, including the events, the Ascendant and its secret, clans, duels, bounties, zones, gated areas, holograms, map markers, Discord, new-player protection, Hunter's Sense and Guardian.
- Upgrading a world from 1.21.x keeps all PeaceSMP data: values, minutes, kills, the Ascendant and the value they keep under the crown, clans, bounties, protection time, zones, areas and holograms. 26.x keeps world data in folders: the file moves from
world/data/peacesmp_karma.dattoworld/data/peacesmp/karma.datby itself on the first start.peacesmp.jsonandpeacesmp-messages.jsonload unchanged.
Resource pack
- "PeaceSMP-Icons gen1 v4" works on 26.x as well as 1.21.x. 26.x read the pack's version information more strictly and refused the earlier packs, so players there saw no icons and no tints; v4 only updates that information in
pack.mcmeta. No file was added, changed or removed.
Everything in 1.5
New: karma events
Events are limited-time rule changes for the whole server. 1.5 brings the event system and its first two events, Peace Week and Blood Moon. More events come in the next updates.
- Three ways to start one:
- Admins:
/peace event start <event>counts down 5 minutes, or/peace event start <event> nowstarts it at once. - Schedule: weekly slots in the config (day, time, event). Off until you add some.
- Random: a 12% chance each hour, only while at least 4 players are online.
- Admins:
- Only one event at a time:
- A scheduled event that comes up during another one waits and starts the moment that one ends.
- A random event is skipped.
- An admin start is refused: "Blood Moon is running. Stop it first with /peace event stop."
- Everyone sees it coming:
- Scheduled events: a Discord post an hour before (if Discord is set up), plus chat and a sound at 5 minutes, 1 minute and 10 seconds.
- Random events: one minute's warning.
- While it runs: a start title, a timer on the action bar next to your karma, a message when it ends, and Discord posts when it starts and ends. Players who join mid-event are told what's on and how long is left.
- Everything else still applies: kill cap, kill cooldown, clans, duels, safe zones, new-player protection, the Value 6-8 risk and Guardian. Events never reveal the secret Ascendant.
- Reloads and restarts:
- A running event survives
/peace reload. - If the server stops during an event, that event is simply over. It doesn't resume after the restart, and nothing it changed stays changed.
- A running event survives
- Empty servers: events keep to their schedule even on a server paused for being empty, so the Discord notice still goes out.
- Admin log: every start, stop, skip and queue is recorded.
Peace Week (1 hour)
- Peaceful minutes count double, both pending and banked.
- Killing costs more:
- A killer above Value 5 drops 2 values for a kill that counts, never below 5.
- A hunter's kill (Value 0-4) doesn't count toward the Hunter path. It still resets their peaceful minutes and still goes on the season record.
- A kill on a Value 9-10 player already weighs 2, so it stays at 2 values, never 4.
Blood Moon (1 hour)
- Every kill that counts gives 2 kills on the Hunter path. The kill cap and cooldown still apply.
- No stacking: a kill on a Value 9-10 player still counts 2, not 4. A killer above Value 5 still drops the usual 1 value.
- Peaceful minutes pause for everyone. Nothing is earned while it lasts. Minutes earned just before it began are banked the moment it ends.
- A red tint covers the screen for the whole event, day or night, for everyone with the resource pack. Ability tints and titles still show over it, and it comes back after them.
Commands and permissions
/peace event start <event> [now],/peace event stop(also calls off a countdown),/peace event list,/peace event status(what's on, what's counting down or queued, the next scheduled slot, random events) and/peace event roll(rolls a random event now, for testing).peacesmp.command.event.start(alsoroll),peacesmp.command.event.stop,peacesmp.command.event.listandpeacesmp.command.event.status: OP by default./peace infoon the Ascendant now reads "Ascendant, real value 3" for admins (and the Ascendant themself): the value they keep while they hold the crown, and go back to when they lose it. Other players still see only their usual secret-safe view.
Resource pack (1.5)
- "PeaceSMP-Icons gen1 v3" added the Blood Moon tint.
- Every file of the earlier packs is unchanged. An older pack with 1.5 just shows no tint, and the new pack works with older versions of the mod.
New config keys
Schedule:
eventsSchedule(empty). For example,[{"day": "saturday", "time": "20:00", "event": "blood_moon"}].- Days are
monday..sunday(ormon..sun) ordaily. Times are in the server's local time.
Random events and warnings:
eventsRandom(true),eventsRandomChancePerHour(0.12),eventsRandomMinPlayers(4)eventAdminCountdownSeconds(300),eventRandomWarningSeconds(60),eventWarningSeconds([300, 60, 10]),eventDiscordNoticeMinutes(60),discordEvents(true)
Peace Week:
peaceWeekMinutes(60),peaceWeekRandomWeight(1),peaceWeekMinuteMultiplier(2),peaceWeekKillValueDrop(2),peaceWeekHunterKillsCount(false)
Blood Moon:
bloodMoonMinutes(60),bloodMoonRandomWeight(1),bloodMoonKillWeight(2),bloodMoonPausesMinutes(true),bloodMoonTint(true)
Old configs keep working: missing keys use these defaults and are added to your file. Every event message is in peacesmp-messages.json under event.* and discord.event.*.
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:nwVERkWN:5DArIl3J"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:nwVERkWN:5DArIl3J"
}

