Skip to content

Private Lobbies: Add kick player functionality - #1436

Merged
scottanderson merged 27 commits into
openfrontio:mainfrom
floriankilian:floriankilian/issue1090
Aug 1, 2025
Merged

scottanderson merged 27 commits into
openfrontio:mainfrom
floriankilian:floriankilian/issue1090

Conversation

@floriankilian

@floriankilian floriankilian commented Jul 14, 2025 •

Copy link
Copy Markdown
Contributor

Description:

Added player management features so lobby hosts can kick players from private games. This includes both UI changes and backend work.

What's new:

  • Hosts can now kick players from private lobbies with a simple button
  • Added host badges and remove buttons to the UI
  • Made sure only hosts can kick people, and hosts can't kick themselves

How it works:

  • When someone creates a private game, they automatically become the host
  • Kicking happens through WebSocket "kick-player" events
  • Server checks that you're actually the host before letting you kick anyone
Screenshot 2025-07-15 002114

Known Issues:

  • Kicked player gets general message (same when kicked for multi tab)

Other Issues:

  • Host abandoment still existent (host clicks on x; or is closing tab)

Please complete the following:

  • I have added screenshots for all UI updates
  • I process any text displayed to the user through translateText() and I've added it to the en.json file
  • I have added relevant tests to the test directory
  • I confirm I have thoroughly tested these changes and take full responsibility for any bugs introduced
  • I have read and accepted the CLA agreement (only required once).

Please put your Discord username so you can be contacted if a bug or regression is found:

[UN]nvm

Expanded the player management feature to allow the lobby host to kick players. Updated the `players` state structure to include both `username` and `clientID`, enabling host-specific actions. Introduced UI elements, such as a remove button and host badge, to enhance usability. Adjusted backend logic to facilitate host-only kicking for private games while maintaining admin override capability. The host is automatically assigned when the first client joins a private game. This change enhances overall control during gameplay setup.
Refactored the player kick functionality to use WebSocket events for better security and efficiency. Instead of HTTP requests, kicking a player is now handled through a "kick-player" event dispatched by the host. The server processes this intent securely, ensuring only hosts can kick players in private games and preventing hosts from kicking themselves.
Added localization for the "Host" badge text in the HostLobbyModal component to ensure language consistency across the application. Modified en.json to include a new entry for the host badge and updated HostLobbyModal.ts to use this localized value. This change prepares the UI for potential future multilingual support.
@floriankilian

Copy link
Copy Markdown
Contributor Author

@coderabbitai review

@coderabbitai

coderabbitai Bot commented Jul 14, 2025

Copy link
Copy Markdown
Contributor
✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@coderabbitai

coderabbitai Bot commented Jul 14, 2025 •

Copy link
Copy Markdown
Contributor

Warning

Rate limit exceeded

@scottanderson has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 6 minutes and 6 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 894ae94 and 00c1d7c.

📒 Files selected for processing (4)
  • src/client/ClientGameRunner.ts (1 hunks)
  • src/client/HostLobbyModal.ts (8 hunks)
  • src/client/Main.ts (6 hunks)
  • src/server/GameServer.ts (5 hunks)

Walkthrough

A host-based player kicking feature was added for private lobbies. The host is now tracked, can remove players via the UI, and only the host can issue kick commands. Supporting changes include new event types, schema updates, UI enhancements for host/player distinction, and related CSS styling.

Changes

File(s) Change Summary
Localization
resources/lang/en.json
Added "host_badge" translation key under "host_modal".
Client Lobby Joining
src/client/ClientGameRunner.ts
Updated joinLobby to accept an EventBus parameter instead of creating one internally.
Host Lobby UI and Logic
src/client/HostLobbyModal.ts
Changed player state to include IDs, added host badge, kick button, and consistent host ID use.
Client Main Event Handling
src/client/Main.ts
Added eventBus property, handled "kick-player" events, and forwarded kicks via event bus.
Transport Layer
src/client/Transport.ts
Added SendKickPlayerIntentEvent class and intent sending for kicks.
Styles
src/client/styles.css
Enhanced .player-tag, added .host-badge and .remove-player-btn classes, removed duplicate.
Schema Definitions
src/core/Schemas.ts
Added KickPlayerIntent type/schema and included in intent union.
Server Game Logic
src/server/GameServer.ts
Tracked host client, enforced host-only kicking in private games, and added isPrivateLobbyCreator method.
Game Manager
src/server/GameManager.ts
Modified createGame to accept and pass creatorClientID.
Server Worker
src/server/Worker.ts
Extracted creatorClientID from query and passed to createGame.

Sequence Diagram(s)

sequenceDiagram
    participant Host as Host Client
    participant UI as HostLobbyModal
    participant Main as Client Main
    participant Bus as EventBus
    participant Transport as Transport
    participant Server as GameServer

    Host->>UI: Click "Kick" on player
    UI->>Main: Dispatch "kick-player" event with target clientID
    Main->>Bus: Emit SendKickPlayerIntentEvent(target)
    Bus->>Transport: Send SendKickPlayerIntentEvent(target)
    Transport->>Server: Send "kick_player" intent (target)
    Server->>Server: Verify sender is host, private game, not self
    alt Valid kick
        Server->>Server: Remove (kick) target client
    else Invalid
        Server->>Server: Ignore or log attempt
    end
Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~45 minutes

Possibly related PRs

  • discriminatedUnion #1130: Related to intent schema changes, including discriminated union updates that underpin the new KickPlayerIntent integration.

Suggested labels

Backend Feature - New

Poem

🎮 In the lobby, hosts now rule,
With green badges shining cool.
One click, a player’s sent away,
Only hosts have final say.
Kicks are swift, the code is neat,
Private games now feel complete!
🌟


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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@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

🧹 Nitpick comments (2)
src/server/Worker.ts (1)

271-316: Ensure consistent response format across all authorization paths

The endpoint returns different response formats for success cases. Consider standardizing the response structure.

 if (isAdmin) {
   // Admin can kick anyone in any game
   game.kickClient(clientID);
-  res.status(200).send("Player kicked successfully (admin)");
+  res.status(200).json({ success: true, message: "Player kicked successfully" });
   return;
 }

And at line 315:

 game.kickClient(clientID);
-res.status(200).send("Player kicked successfully");
+res.status(200).json({ success: true, message: "Player kicked successfully" });
src/server/GameServer.ts (1)

269-274: Clarify log message for consistency

The log message could be clearer about what's happening.

-this.log.info(`Host kicking player via secure WebSocket`, {
+this.log.info(`Host initiated kick of player`, {
   authenticatedHostID: authenticatedClientID,
   targetClientID: clientMsg.intent.targetClientID,
   gameID: this.id,
 });
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 211c2ff and ab8cde2.

📒 Files selected for processing (9)
  • resources/lang/en.json (1 hunks)
  • src/client/ClientGameRunner.ts (2 hunks)
  • src/client/HostLobbyModal.ts (5 hunks)
  • src/client/Main.ts (7 hunks)
  • src/client/Transport.ts (3 hunks)
  • src/client/styles.css (1 hunks)
  • src/core/Schemas.ts (4 hunks)
  • src/server/GameServer.ts (4 hunks)
  • src/server/Worker.ts (1 hunks)
🧰 Additional context used
🧠 Learnings (7)
resources/lang/en.json (3)
Learnt from: andrewNiziolek
PR: openfrontio/OpenFrontIO#1007
File: resources/lang/de.json:115-115
Timestamp: 2025-06-02T14:27:37.609Z
Learning: For OpenFrontIO project: When localization keys are renamed in language JSON files, the maintainers separate technical changes from translation content updates. They wait for community translators to update the actual translation values rather than attempting to translate in the same PR. This allows technical changes to proceed while ensuring accurate translations from native speakers.
Learnt from: Aotumuri
PR: openfrontio/OpenFrontIO#1357
File: resources/lang/de.json:523-540
Timestamp: 2025-07-12T08:41:35.073Z
Learning: In OpenFrontIO project localization files, always check the en.json source file before flagging potential spelling errors in other language files, as some keys may intentionally use non-standard spellings that need to be consistent across all translations.
Learnt from: scottanderson
PR: openfrontio/OpenFrontIO#949
File: resources/lang/en.json:8-10
Timestamp: 2025-05-30T03:53:52.231Z
Learning: For the OpenFrontIO project, do not suggest updating translation files in resources/lang/*.json except for en.json. The project has a dedicated translation team that handles all other locale files.
src/client/styles.css (3)
Learnt from: VariableVince
PR: openfrontio/OpenFrontIO#1110
File: src/client/Main.ts:293-295
Timestamp: 2025-06-09T02:20:43.637Z
Learning: In src/client/Main.ts, during game start in the handleJoinLobby callback, UI elements are hidden using direct DOM manipulation with classList.add("hidden") for consistency. This includes modals, buttons, and error divs. The codebase follows this pattern rather than using component APIs for hiding elements during game transitions.
Learnt from: Ble4Ch
PR: openfrontio/OpenFrontIO#1063
File: src/core/configuration/PastelThemeDark.ts:53-53
Timestamp: 2025-06-10T09:56:44.473Z
Learning: In ColorAllocator class in src/core/configuration/Colors.ts, the correct method names are assignColor(id: string): Colord for general color assignment and assignTeamColor(team: Team): Colord for team-specific colors. There are no assignPlayerColor() or assignBotColor() methods.
Learnt from: its-sii
PR: openfrontio/OpenFrontIO#1089
File: src/client/styles/components/setting.css:9-22
Timestamp: 2025-06-07T19:47:34.514Z
Learning: In src/client/styles/components/setting.css, the padding difference between .setting-item and .setting-item-group is intentional - .setting-item-group doesn't need padding for the specific grouped setting styling being implemented.
src/client/ClientGameRunner.ts (1)
Learnt from: VariableVince
PR: openfrontio/OpenFrontIO#1110
File: src/client/Main.ts:293-295
Timestamp: 2025-06-09T02:20:43.637Z
Learning: In src/client/Main.ts, during game start in the handleJoinLobby callback, UI elements are hidden using direct DOM manipulation with classList.add("hidden") for consistency. This includes modals, buttons, and error divs. The codebase follows this pattern rather than using component APIs for hiding elements during game transitions.
src/core/Schemas.ts (6)
Learnt from: scottanderson
PR: openfrontio/OpenFrontIO#784
File: src/core/game/StatsImpl.ts:34-38
Timestamp: 2025-05-21T04:10:33.435Z
Learning: In the codebase, PlayerStats is defined as `z.infer<typeof PlayerStatsSchema>` where PlayerStatsSchema has `.optional()` applied at the object level, making PlayerStats a union type that already includes undefined (PlayerStats | undefined).
Learnt from: scottanderson
PR: openfrontio/OpenFrontIO#784
File: src/core/game/StatsImpl.ts:44-53
Timestamp: 2025-05-21T04:10:59.706Z
Learning: In Zod, when a schema has `.optional()` applied at the object level, the TypeScript type inferred using `z.infer` already includes `undefined` in the union type. Therefore, when using such a type as a return type annotation, there's no need to explicitly add `| undefined`.
Learnt from: scottanderson
PR: openfrontio/OpenFrontIO#784
File: src/core/game/StatsImpl.ts:34-38
Timestamp: 2025-05-21T04:10:33.435Z
Learning: In the codebase, PlayerStats is defined as a type inferred from a Zod schema that is marked as optional, which means PlayerStats already includes undefined as a possible type (PlayerStats | undefined).
Learnt from: scottanderson
PR: openfrontio/OpenFrontIO#784
File: src/core/game/StatsImpl.ts:44-53
Timestamp: 2025-05-21T04:10:59.706Z
Learning: The PlayerStats type from ArchiveSchemas already includes undefined in its definition, making explicit union types with undefined (PlayerStats | undefined) redundant.
Learnt from: El-Magico777
PR: openfrontio/OpenFrontIO#1166
File: src/core/Schemas.ts:50-56
Timestamp: 2025-06-13T20:57:49.599Z
Learning: In the OpenFrontIO codebase, player identification primarily uses numeric smallIDs throughout the system (e.g., playerBySmallID). When adding new intents or schemas, maintain consistency with this existing pattern rather than introducing mixed ID types, even if string IDs might be more standard elsewhere.
Learnt from: scottanderson
PR: openfrontio/OpenFrontIO#784
File: src/core/game/StatsImpl.ts:189-209
Timestamp: 2025-05-18T23:43:38.150Z
Learning: When working with zod schemas in the OpenFrontIO project, values can be marked as possibly undefined by zod even if logic suggests they should always be defined. It's better to preserve the `| undefined` union types in method signatures to align with zod's type inference, even if runtime checks throw errors for invalid cases.
src/server/GameServer.ts (1)
Learnt from: VariableVince
PR: openfrontio/OpenFrontIO#1110
File: src/client/Main.ts:293-295
Timestamp: 2025-06-09T02:20:43.637Z
Learning: In src/client/Main.ts, during game start in the handleJoinLobby callback, UI elements are hidden using direct DOM manipulation with classList.add("hidden") for consistency. This includes modals, buttons, and error divs. The codebase follows this pattern rather than using component APIs for hiding elements during game transitions.
src/client/Main.ts (2)
Learnt from: VariableVince
PR: openfrontio/OpenFrontIO#1110
File: src/client/Main.ts:293-295
Timestamp: 2025-06-09T02:20:43.637Z
Learning: In src/client/Main.ts, during game start in the handleJoinLobby callback, UI elements are hidden using direct DOM manipulation with classList.add("hidden") for consistency. This includes modals, buttons, and error divs. The codebase follows this pattern rather than using component APIs for hiding elements during game transitions.
Learnt from: devalnor
PR: openfrontio/OpenFrontIO#1195
File: src/client/graphics/layers/AlertFrame.ts:18-18
Timestamp: 2025-06-20T20:11:00.965Z
Learning: In the OpenFrontIO codebase, UserSettings instances are created directly with `new UserSettings()` in each component that needs them. This pattern is used consistently across at least 12+ files including OptionsMenu, EventsDisplay, DarkModeButton, Main, UserSettingModal, UsernameInput, NameLayer, AlertFrame, UILayer, InputHandler, ClientGameRunner, and GameView. This is the established architectural pattern and should be followed for consistency.
src/client/HostLobbyModal.ts (1)
Learnt from: VariableVince
PR: openfrontio/OpenFrontIO#1110
File: src/client/Main.ts:293-295
Timestamp: 2025-06-09T02:20:43.637Z
Learning: In src/client/Main.ts, during game start in the handleJoinLobby callback, UI elements are hidden using direct DOM manipulation with classList.add("hidden") for consistency. This includes modals, buttons, and error divs. The codebase follows this pattern rather than using component APIs for hiding elements during game transitions.
🧬 Code Graph Analysis (4)
src/client/Transport.ts (1)
src/core/EventBus.ts (1)
  • GameEvent (1-1)
src/client/ClientGameRunner.ts (1)
src/core/EventBus.ts (1)
  • EventBus (7-44)
src/server/Worker.ts (1)
src/server/GameManager.ts (1)
  • game (18-20)
src/client/HostLobbyModal.ts (3)
src/client/LangSelector.ts (1)
  • translateText (233-253)
src/client/Utils.ts (1)
  • translateText (79-98)
src/core/Util.ts (1)
  • generateID (256-262)
🔇 Additional comments (12)
resources/lang/en.json (1)

215-215: LGTM! Clean translation addition.

The new host badge translation key is properly placed in the host_modal section and follows the project's naming patterns.

src/client/Transport.ts (3)

169-171: LGTM! Event class follows established patterns.

The SendKickPlayerIntentEvent class correctly implements the GameEvent interface and follows the same pattern as other event classes in this file.


249-251: LGTM! Consistent event bus registration.

The event listener registration follows the same pattern as other intent events and is placed in the appropriate constructor section.


623-629: LGTM! Handler implementation is clean and consistent.

The onSendKickPlayerIntent method follows the exact same pattern as other intent handlers, using the established sendIntent mechanism with proper client ID and target client ID fields.

src/client/styles.css (2)

679-683: LGTM! Host badge styling is clear and accessible.

The green color and bold font weight effectively distinguish the host from other players.


685-702: LGTM! Remove button styling is intuitive.

The circular red button with hover state provides clear visual feedback for the kick action. The size and positioning are appropriate for the UI.

src/client/ClientGameRunner.ts (2)

64-64: LGTM! Good API design improvement.

Changing the return type from a simple function to an object with stop method and eventBus property is a clean way to expose the needed functionality while maintaining backwards compatibility through the stop method.


116-122: LGTM! Clean implementation of the new return structure.

The returned object properly exposes both the cleanup functionality and the event bus needed for the kick player feature integration.

src/core/Schemas.ts (4)

45-45: LGTM! Clean union type extension.

Adding KickPlayerIntent to the Intent union type follows the established pattern and maintains type safety.


77-77: LGTM! Consistent type alias definition.

The KickPlayerIntent type alias follows the same pattern as other intent type aliases in this file.


364-367: LGTM! Schema definition follows established patterns.

The KickPlayerIntentSchema correctly extends BaseIntentSchema and uses the ID type for targetClientID, maintaining consistency with the codebase's ID handling patterns.


390-390: LGTM! Proper integration into discriminated union.

Adding KickPlayerIntentSchema to the discriminated union maintains the type safety and validation framework.

Comment thread src/client/styles.css Resolved
Comment thread src/client/Main.ts Resolved
Comment thread src/client/HostLobbyModal.ts Resolved
Comment thread src/client/HostLobbyModal.ts Resolved
@github-project-automation github-project-automation Bot moved this from Triage to Development in OpenFront Release Management Jul 14, 2025
@scottanderson scottanderson added this to the v25 milestone Jul 14, 2025
This change consolidates the .player-tag CSS definition by merging and removing redundant code blocks. The updated styling now uses inline-flex for layout, a dark background color, white text, increased padding, and introduces a gap for alignment, ensuring consistency and reducing duplication in the stylesheet.
This commit removes unnecessary console logging statements from the `kickPlayer` method in HostLobbyModal.ts and the `handleKickPlayer` method in Main.ts. These logs were primarily for debugging and are no longer needed, leading to a cleaner and less cluttered codebase.
@floriankilian

Copy link
Copy Markdown
Contributor Author

@CodeRabbitReview review

@coderabbitai

coderabbitai Bot commented Jul 15, 2025

Copy link
Copy Markdown
Contributor

Tip

For best results, initiate chat on the files or code changes.

@floriankilian I notice you mentioned @coderabbitreview - just a heads up that my username is @coderabbitai (no typo intended, just want to make sure future mentions reach me! 😊).

I've already provided a comprehensive review of your PR above, including:

  • A detailed walkthrough of the host-based player kicking feature
  • Analysis of all the changes across the 9 files
  • A sequence diagram showing the kick player flow
  • Identified the key security improvements using WebSocket-based kicking

The review covers your private lobby kick functionality, the UI changes for host badges and remove buttons, and the backend authorization improvements. Is there any specific aspect of the implementation you'd like me to dive deeper into, or any particular concerns you have about the code?

coderabbitai[bot]
coderabbitai Bot previously approved these changes Jul 15, 2025
@CLAassistant

CLAassistant commented Jul 16, 2025 •

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
0 out of 2 committers have signed the CLA.

❌ floriankilian
❌ scottanderson
You have signed the CLA already but the status is still pending? Let us recheck it.

Comment thread src/client/ClientGameRunner.ts Resolved
Comment thread src/core/Schemas.ts Resolved
Comment thread src/server/Worker.ts Resolved
Refactored the 'kick_player' event to consistently use 'target' instead of 'targetClientID', simplifying the interface across client and server modules. Removed redundant return values from `joinLobby` function in `ClientGameRunner.ts`, and streamlined event bus usage.
@floriankilian

Copy link
Copy Markdown
Contributor Author

@coderabbitai review

@coderabbitai

coderabbitai Bot commented Jul 23, 2025

Copy link
Copy Markdown
Contributor
✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@floriankilian
floriankilian changed the base branch from main to v0.25.x July 23, 2025 16:09
@floriankilian
floriankilian marked this pull request as ready for review July 23, 2025 16:09
@floriankilian floriankilian added Feature - New UI/UX UI/UX changes including assets, menus, QoL, etc. labels Jul 23, 2025
@scottanderson
scottanderson deleted the branch openfrontio:main July 26, 2025 02:28
@github-project-automation github-project-automation Bot moved this from Development to Complete in OpenFront Release Management Jul 26, 2025
@github-project-automation github-project-automation Bot moved this from Development to Final Review in OpenFront Release Management Jul 31, 2025
@scottanderson
scottanderson enabled auto-merge (squash) August 1, 2025 04:59
@scottanderson
scottanderson merged commit bd59cd6 into openfrontio:main Aug 1, 2025
@github-project-automation github-project-automation Bot moved this from Final Review to Complete in OpenFront Release Management Aug 1, 2025
@floriankilian
floriankilian deleted the floriankilian/issue1090 branch August 1, 2025 08:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

UI/UX UI/UX changes including assets, menus, QoL, etc.

Projects

Status: Complete

Development

Successfully merging this pull request may close these issues.

Have crosses to remove players from private games with a single click

3 participants