Skip to content

docs: draft v33 release notes - #4752

Draft
evanpelle wants to merge 1 commit into
mainfrom
v33-release-notes
Draft

docs: draft v33 release notes#4752
evanpelle wants to merge 1 commit into
mainfrom
v33-release-notes

Conversation

@evanpelle

Copy link
Copy Markdown
Collaborator

Draft release notes for v33, compiled from the 215 commits on main since the v32 branch point (2026-06-17). Structure follows the v32 release body.

Still needs before publishing

  • Translators section — placeholder; comes from Crowdin.
  • Author attribution — currently git commit display names (Evan, Ryan, Zixer1, RickD004, …) rather than GitHub handles. v32 used a mix; note git says crunchybbb where v32 credited crunchybbb2.
  • Map flavor text — only 5 of the 17 new maps have descriptions. v32 had hand-written blurbs for every map; the map authors are the source for those.

Notes

  • There is no v33 branch on the remote yet, so the diff base is origin/v32. Two commits in the range explicitly reference v33, which confirms the range is right.
  • The file is at the repo root as v33-release-notes.md. Happy to move it (or drop it entirely and just paste the body into the GitHub release) — it isn't wired into the build. resources/changelog.md is overwritten at build time from the release body, so this file is purely for review.

🤖 Generated with Claude Code

Compiled from the 215 commits on main since the v32 branch point
(2026-06-17). Structured to match the v32 release body.

Still needs before publishing:
- Translators section (comes from Crowdin)
- GitHub handles instead of git display names
- Flavor text for the new maps

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Walkthrough

Adds a complete v33 release-notes document covering major gameplay changes, player-facing features, platform updates, administration, performance, and security.

Changes

v33 release documentation

Layer / File(s) Summary
Core gameplay and release highlights
v33-release-notes.md
Documents Doomsday Clock, Ranked 2v2, matchmaking behavior, gameplay balance changes, and new or updated maps.
Player-facing features
v33-release-notes.md
Documents cosmetics, accounts, Steam, anonymous names, featured streams, lobbies, graphics, quality-of-life, and advertising changes.
Platform, operations, and security notes
v33-release-notes.md
Documents performance work, nations and bots, admin tooling, security changes, translation placeholders, and a miscellaneous entry.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Suggested reviewers: celant, developingtom, flopinguin

Poem

New maps unfold beneath the sun,
Ranked battles queue, then run.
Steam and lobbies join the flow,
Tiny fixes help the pixels glow.
v33 sails out with lemon cheer.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly states this is a draft v33 release notes docs change.
Description check ✅ Passed The description matches the release-notes draft and its review notes.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 4

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@v33-release-notes.md`:
- Around line 240-242: Replace the placeholder under the “Translators” section
in v33-release-notes.md with the finalized translator acknowledgments exported
from Crowdin, preserving the existing release-notes structure and formatting.
- Line 233: Update the release-note entry to say “Reject late spawn intents from
already-spawned players,” matching the guard implemented in SpawnExecution
rather than implying all post-phase spawn intents are rejected.
- Around line 53-69: Complete the missing flavor-text descriptions for the 12
new map entries in the release notes, adding each description between its map
title/author and the next entry. Preserve the existing flavor text for entries
that already have descriptions and ensure all 17 map entries contain flavor text
before publishing.
- Around line 18-39: Normalize every contributor attribution in the release
notes to the contributor’s GitHub handle, replacing display names such as
“Navaneeth Prabha” and “Patrick Plays Badly” while preserving existing handles
and the changelog entries themselves.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: dbd1a7c8-3a54-4ced-bc86-5ce4ad4b9195

📥 Commits

Reviewing files that changed from the base of the PR and between 73b086a and 4d1e5fe.

📒 Files selected for processing (1)
  • v33-release-notes.md

Comment thread v33-release-notes.md
Comment on lines +18 to +39
- Added the Doomsday Clock battle-royale zone gamemode — Zixer1
- Rebalanced the Doomsday Clock: 10-minute grace period, wave squeeze, slower troop drain, gentler-but-steeper warship attrition — Zixer1
- Doomsday Clock now decays warships alongside troops for doomed sides, and floors the drain at 5% of max instead of wiping to zero — Zixer1
- Doomsday Clock judges teams against the same bar as solo sides — Zixer1
- Doomed warships stay on patrol instead of idling at ports — Zixer1
- Added warship veterancy, with updated in-game instructions — bijx
- MIRV warheads are now standard nukes: real flight, normal SAM interception, per-type speeds — Evan
- Missile silos go on cooldown when launching a MIRV — Evan
- Added impassable terrain — FloPinguin
- Fixed minimap priority for impassable terrain pathfinding — FloPinguin
- Added a custom alliance duration lobby control — Zixer1
- Fixed pirating not being disabled when a warship's owner has no port in that body of water — TKTK123456
- Fixed transport ships targeting unreachable inland-lake shores — Navaneeth Prabha
- Fixed transport ship troop counts not updating when a hydrogen bomb hits the player — AmanorsElliot
- Fixed the rail network path length limit and re-added its tests — TKTK123456
- Fixed the factory ghost radius — TKTK123456
- Fixed non-structures being deletable — unne27
- Fixed the nuke preview showing teammate SAMs as threats — Evan
- Highlight the owner of hovered naval units — unne27
- Reduced compact map chance in 1v1 from 50% to 20% — FloPinguin
- Removed the ports-disabled modifier from public games — Evan

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Normalize contributor attribution to GitHub handles.

This document still mixes display names such as Navaneeth Prabha and Patrick Plays Badly with handles such as Zixer1 and bijx. Replace all contributor suffixes with GitHub handles before publishing.

As per PR objectives, author attribution still needs this update.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@v33-release-notes.md` around lines 18 - 39, Normalize every contributor
attribution in the release notes to the contributor’s GitHub handle, replacing
display names such as “Navaneeth Prabha” and “Patrick Plays Badly” while
preserving existing handles and the changelog entries themselves.

Comment thread v33-release-notes.md
Comment on lines +53 to +69
- **Sol** 🪐 — Massive map of the Solar System (by RickD004)
- **Russia** 🇷🇺 — Big-map treatment of Russia (by RickD004)
- **United States** 🇺🇸 — Built for the new impassable terrain feature (by RickD004)
- **Germany** 🇩🇪 — With state flags (by SpeakIsntThere)
- **China** 🇨🇳 (by crunchybbb)
- **Scandinavia** 🇸🇪 (by crunchybbb)
- **Baltics** (by RickD004)
- **Caspian Sea** — With team spawns (by crunchybbb)
- **Crimea** (by crunchybbb)
- **Finger Lakes** (by crunchybbb)
- **Gulf of Guinea** (by RickD004)
- **Hecate Strait** (by Liam Langford)
- **Irish Sea** (by RickD004)
- **Levant** (by RickD004)
- **Tierra del Fuego** — Featuring impassable terrain (by RickD004)
- **Branching Paths** (by NotRocketfish)
- **More than luck** (by Patrick Plays Badly)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Complete the missing map flavor text.

Most new-map entries currently contain only a title and author. Add the remaining flavor text before publishing.

As per PR objectives, flavor text is still pending for 12 of the 17 new maps.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@v33-release-notes.md` around lines 53 - 69, Complete the missing flavor-text
descriptions for the 12 new map entries in the release notes, adding each
description between its map title/author and the next entry. Preserve the
existing flavor text for entries that already have descriptions and ensure all
17 map entries contain flavor text before publishing.

Comment thread v33-release-notes.md

### 🔒 Security & Anti-Cheat

- Reject spawn intents after the spawn phase (anti-teleport) — iamlewis

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

Narrow the spawn-intent wording.

src/core/execution/SpawnExecution.ts:40-95 ignores late spawn intents only for players who have already spawned. “Reject spawn intents after the spawn phase” sounds broader than the implemented guard; say “Reject late spawn intents from already-spawned players” instead.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@v33-release-notes.md` at line 233, Update the release-note entry to say
“Reject late spawn intents from already-spawned players,” matching the guard
implemented in SpawnExecution rather than implying all post-phase spawn intents
are rejected.

Comment thread v33-release-notes.md
Comment on lines +240 to +242
### 🌐 Translators

_(To be filled in from Crowdin before publishing.)_

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Replace the Crowdin placeholder before publishing.

The translators section is still incomplete and contains only a placeholder.

As per PR objectives, this section still needs to be filled from Crowdin.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@v33-release-notes.md` around lines 240 - 242, Replace the placeholder under
the “Translators” section in v33-release-notes.md with the finalized translator
acknowledgments exported from Crowdin, preserving the existing release-notes
structure and formatting.

@github-project-automation github-project-automation Bot moved this from Triage to Development in OpenFront Release Management Jul 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Development

Development

Successfully merging this pull request may close these issues.

1 participant