Current Behaviour
Current Behaviour
In some cases, when a player does not accept the battleground invitation (timeout on “Enter Battle”), the battleground does not get re-added to the free slot queue.
As a result:
The BG may start at minimum players (e.g. 10v10).
Additional invitations are sent to reach max capacity (e.g. 15v15).
If one or more players do not accept the invitation, InvitedCount decreases.
However, the battleground is not re-enqueued into the BG free slot queue.
The queue system does not attempt to fill it again.
The BG remains stuck at a lower player count (e.g. 11v11, 12v12) even when players are available in queue.
This also allows a new battleground to be created while an existing one still has real free slots.
Expected Behaviour
When an invitation expires (or is declined) and free slots reopen:
The battleground should be re-added to the free slot queue.
The queue system should attempt to fill it again on the next queue update.
No new battleground should be created while active battlegrounds still have free slots.
Source
No response
Steps to reproduce the problem
Set CONFIG_BATTLEGROUND_INVITATION_TYPE = BG_QUEUE_INVITATION_TYPE_EVEN.
Queue a battleground with enough players to start at minimum size (example: AV/WSG/etc. starts at 10v10 but can fill up to 15v15).
Let the battleground start and wait until it begins inviting additional players to fill remaining slots.
Reproduce one of these scenarios:
Invitation timeout: one of the invited players does not click “Enter Battle” and lets the invitation expire.
Player leaves: a player leaves the battleground / disconnects after the BG is active (creating free slots again).
Keep additional players waiting in queue (so there is supply to refill).
Observe that the battleground does not get filled again (stays e.g. 11v11 / 12v12 instead of reaching 15v15), even though free slots exist and players are available in queue.
In some cases, a new battleground instance may be created while the previous one still has reopened free slots.
Expected result
When an invitation expires or a player leaves and free slots reopen, the battleground should be re-enqueued into the free-slot queue and refilled on next queue update.
Actual result
The battleground is not re-enqueued, so it stops being considered for refill and can remain underfilled.
Extra Notes
No response
AC rev. hash/commit
8472334
Operating system
Debian
Custom changes or Modules
No response
Current Behaviour
Current Behaviour
In some cases, when a player does not accept the battleground invitation (timeout on “Enter Battle”), the battleground does not get re-added to the free slot queue.
As a result:
The BG may start at minimum players (e.g. 10v10).
Additional invitations are sent to reach max capacity (e.g. 15v15).
If one or more players do not accept the invitation, InvitedCount decreases.
However, the battleground is not re-enqueued into the BG free slot queue.
The queue system does not attempt to fill it again.
The BG remains stuck at a lower player count (e.g. 11v11, 12v12) even when players are available in queue.
This also allows a new battleground to be created while an existing one still has real free slots.
Expected Behaviour
When an invitation expires (or is declined) and free slots reopen:
The battleground should be re-added to the free slot queue.
The queue system should attempt to fill it again on the next queue update.
No new battleground should be created while active battlegrounds still have free slots.
Source
No response
Steps to reproduce the problem
Set CONFIG_BATTLEGROUND_INVITATION_TYPE = BG_QUEUE_INVITATION_TYPE_EVEN.
Queue a battleground with enough players to start at minimum size (example: AV/WSG/etc. starts at 10v10 but can fill up to 15v15).
Let the battleground start and wait until it begins inviting additional players to fill remaining slots.
Reproduce one of these scenarios:
Invitation timeout: one of the invited players does not click “Enter Battle” and lets the invitation expire.
Player leaves: a player leaves the battleground / disconnects after the BG is active (creating free slots again).
Keep additional players waiting in queue (so there is supply to refill).
Observe that the battleground does not get filled again (stays e.g. 11v11 / 12v12 instead of reaching 15v15), even though free slots exist and players are available in queue.
In some cases, a new battleground instance may be created while the previous one still has reopened free slots.
Expected result
When an invitation expires or a player leaves and free slots reopen, the battleground should be re-enqueued into the free-slot queue and refilled on next queue update.
Actual result
The battleground is not re-enqueued, so it stops being considered for refill and can remain underfilled.
Extra Notes
No response
AC rev. hash/commit
8472334
Operating system
Debian
Custom changes or Modules
No response