Camp Chat
Talk with the rest of the camp. Keep it friendly; officers moderate the board.
- Loading the board…
Signed out
Community site for the Peace in War of Rights server and Discord
Not a member yet? Join the Discord
Welcome back,
Announcements, upcoming events and community links for the Peace in War of Rights server.
Tie your site account to your War of Rights player to put your time on the line, streaks and regiment on your profile. It's optional: Steam sign-in, a code typed in game chat, or a name claim that staff check.
Talk with the rest of the camp. Keep it friendly; officers moderate the board.
All-time standings. Rank comes from points: time on the server, minus conduct.
Looking for a regiment to fight with? These ones want men. Lead a regiment? Post it here.
When the field fills up, and how the server is growing.
Shout-outs from the ranks for good play and good conduct, approved by officers.
Posted by server officers. Newest first.
Administration
Everything you can manage on the website, the Discord and the game server. Pick a section below, or use the tabs above.
Set rank, duty and status, then save the row. Roles decide what each member can open; change them with the Roles button. Discharging a member removes their access and ends their sessions. A reset code lets a member set a new password; share it with them on Discord. You can only edit members whose access does not exceed yours.
Each role is a set of permissions. A member's access is everything their roles allow. Owner always has every permission. Give roles to members on the Members tab.
Drafts are private. Published announcements appear on the home page.
The next upcoming event is shown on the home page. Past events stay here for the record.
Every message on the home page board, including deleted ones. Tick messages to act on many at once.
| Select | When | Who | Message | State | Actions |
|---|
Approved commendations show on the home page and on the member's profile. You cannot review one you gave or received.
Newest first, including deleted ones. Mutes from the chat board also stop a member posting here.
| Select | When | Who | Type | Text | State | Actions |
|---|
Restarting cancels the running campaign, without a winner, and starts a fresh one today.
Every admin action on the website and every Discord Admin request, newest first.
| When | Who | Action | Detail | Result |
|---|
Every announcement and every command run: on the website, as the Discord bot, and in the game server’s admin console. Newest first.
| When | Where | Who | What | Detail | Result |
|---|
Loading…
| Member | Roles | Joined | Account made |
|---|---|---|---|
| Search to see members. | |||
Highest first.
Loading the regiment…
Server maps
What the server plans to play next, and what it has played.
Planned, subject to change. These are the maps the schedulers mean to run. The map on the server can differ on the night.
The map on the server now, what came before it, and what was played each day.
Field forecast
The sky over the map on the server now, what changed today, and what the maps ahead tend to bring.
Each new map starts on its own weather; admins can change rain, fog, wind, cloud and the clock during play.
The maps ahead and the weather each has had before.
Every change to the weather, newest first. Times are in your time zone.
How often a map running at that hour got rain, fog or a night sky, over the last 30 days.
Who changed the weather, when, and what happened around it. Only members with the Weather_admin role see this.
The game logs every notch an admin's slider passes (0.025 apart, a quarter hour for the clock) and logs the final value once more when the slider is let go. Those steps are joined into one change. Where a change started is known when someone changed that slider earlier on the same map; otherwise it is worked out from the first notch (marked *).
Flags: Heavy thick fog, downpour, gale, overcast or a night clock. Undid someone another admin set the same slider within 10 minutes before. Fiddling the same slider 3 or more times in 5 minutes. Just joined within 3 minutes of joining. Left soon after left the server within 10 minutes. Chat about it other players talked about the weather within 5 minutes after. The score adds these up to sort the list; it is a pointer, not a verdict. Read the context before acting.
| Who | Changes | Heavy | Undid others | Undone | Fiddling | Drive-by | Chat after | Score |
|---|
| Between | Times | Sliders and maps | Last |
|---|
| When | Who | Change | Players on | Into round | Their visit | Flags |
|---|
Muster rolls
How many were on the field on PIWOR1 and PIWOR2 at any moment, counted from every join and leave in the game logs, with Steam's own connection records alongside.
Pick a date, a time and the time zone it was said in.
Soldiers on the field on each server. The dashed line is the moment you looked up.
| Hour starting | PIWOR1 at the hour | PIWOR1 most | PIWOR2 at the hour | PIWOR2 most | All of Steam |
|---|
The camp newspaper
Posts from the camp: after-action talk, screenshots described in words, game results and battle reports. Use @name to call someone in.
Strategy, history and bragging rights
Talk around the campfire
Recognition and service
Loading the profile…
Every soldier and regiment on the Peace in War of Rights server, from every log the server has kept.
Loading…
Every number on this site comes from the game server’s own log. Here is exactly how, so you can trust it.
A stay runs from the moment the server logs you joining to the moment it logs you leaving. Gaps between visits never count: play 30 minutes in the morning and 10 at night and you have 40 minutes, not a whole day.
If a leave line is missing (a crash, a server restart), a single stay is cut off at 10 hours so a ghost connection can’t pad anyone’s time.
Nothing is counted twice. Every stay is stored with its real start and end time. Pulling the same log again, or a longer copy of it, merges into what is already there instead of adding to it.
A regiment is any tag in square brackets worn by at least two players, like [7th]. Time counts toward the tag you wore at the time.
The highlight cards are worked out from the same stays: the biggest battle is the exact moment the most soldiers were connected at once, streaks are days in a row with at least one stay, and “this week” is the last 7 days. Cards only appear once there is enough data behind them.
The standings refresh themselves every 30 minutes from the live log, and officers can import older log backups at any time.
The game server’s clock runs on Nevada time. Every time and date on this site is converted to your own time zone, with daylight saving handled for each date. Times in the weekly Discord dispatch show in each reader’s own zone too.