Crucial Guild Quaility Of Life Updates: Kick Confirmation Dialogue, Officer Demotion/Kick Flow, and "Avoid Members in PvP" Fix for Random Battles

Dear PRO Development Team,

As a Guild Leader, I would like to propose three essential Quality of Life improvements and bug fixes regarding the Guild Management Menu and matchmaking system. Currently, managing a guild has some friction points that can easily lead to critical accidents or operational issues.

I have attached screenshots of the current Guild Leader interaction menu for reference

1. Instant Guild Removal Without Confirmation (UI/UX Tip)
The Problem:

As you can see in my first image, the "Guild Kick" button is located right between "Inspect" and "Promote Guild." Clicking "Remove Guild" instantly removes the user from the guild without warning or verification. Due to the UI's scalability or the tendency for quick clicks, leaders often mistakenly click "Remove" when they only intend to inspect or promote a member. This causes unnecessary problems, loss of accumulated guild points, and forces us to constantly invite new members.

Proposed Solution:

Add a simple confirmation dialog box when clicking "Kick":

"Are you sure you want to kick [Player Name] from the guild? [Yes] [No]"

2. Guild Leader Cannot Directly Kick "Officers" (Hierarchy Logic Error)

The Problem:

Currently, a guild leader cannot "Kick" a member with the rank of "Officer" via the Roster. It's possible through code, but I consider this hierarchically incorrect, as the leader has absolute authority over all ranks.

Currently, we first have to manually demote the Officer to a Standard Member, and only then does the "Kick" button work. This is unintuitive and slows down urgent moderation actions.

Proposed Solution:

Adjust the hierarchy permissions code. If the interacting user has the rank of Guild Leader, they should be able to bypass all security checks and remove any member, regardless of their current rank (including Officers).

3. The "Avoid Members in PvP" option doesn't work in Random Battles (Bug Report)

The problem:

In the guild member list interface, there is an option/button to "Avoid Members in PvP." While this security algorithm works correctly for standard ranked PvP matchmaking, it fails completely during Random Battles. Guild members frequently face each other in Random Battles, raising suspicions of matchmaking or unwanted competitive friction.

Proposed Solution:

Ensure that the matchmaking queue logic for Random Battles respects the "Avoid members in PvP" option or applies the same guild member avoidance filter already present in standard PvP matchmaking.

These quality-of-life improvements would greatly optimize guild management and prevent frustrating situations for all community leaders.

Thank you for your continued effort and support of the game!

Edited 1 hour ago1 hr by Midnightagony