Summary
Klombos Bedwars has a persistent issue where players are still able to join matches in progress, even long after the Round Settings Device has triggered Disable Matchmaking.
We have tested multiple methods of activating Disable Matchmaking, including Verse and device-based events with both agent and non-agent triggers. The issue persists regardless of the activation method.
The unusual part is that reverting the island to an older revision fixes the issue. However, as soon as we publish a new update from that working revision—even if the changes are minor and completely unrelated to matchmaking—the issue returns.
The game is currently running an older revision version (made latest lore version) so that we are not hurting our playerbase actively, but we are unable to safely update live currently.
Because of this behavior, we believe this may be related to the matchmaking/backend state rather than our implementation.
Please select what you are reporting on:
Unreal Editor for Fortnite
What Type of Bug are you experiencing?
Matchmaking
Steps to Reproduce
- Publish a new version of Klombos Bedwars where Disable Matchmaking is functioning correctly. (The version we’re running before we changed ANYTHING about the round settings device).
- Update to Live
- Verify that players can no longer join the match in progress.
- Make a new update to the island that does not modify:
- The Round Settings Device
- The Disable Matchmaking logic
- The event used to trigger Disable Matchmaking
- Island Settings
- Publish the updated version.
- Attempt to join the active match from another account/player after matchmaking should already be disabled.
- Players are still placed into the match in progress.
Reverting back to the previously working published revision and pushing that to the live causes Disable Matchmaking to function correctly again.
Expected Result
Once the Round Settings Device receives the Disable Matchmaking event, new players should no longer be able to enter that active match.
This behavior should remain consistent between island updates as long as the matchmaking configuration and Disable Matchmaking implementation have not changed.
I know the device mentions it could take a little bit of time before it comes into effect, but we had this issue over a period 2 days before we decided to fully revert to an older revsion and push that.
Observed Result
Players continue joining matches in progress even after Disable Matchmaking has already been triggered.
This can occur significantly later in the match, not only immediately after the event is triggered.
The problem appears to be tied to publishing/updating the island:
Reverting to an older working revision pre-changing the methods used to activate the event fixes the issue.
Republishing that working version works, but as soon as we update again with unrelated changes causes the issue to return.
Changing the method used to trigger Disable Matchmaking does not resolve it, we even had over 3 different methods at some point (Verse, UEFN Events etc.)
Platform(s)
All
Island Code
4164-3090-6037
Video
Klombos Disable Matchmaking Bug Report Media - Album on Imgur (Set of media to be found here)
Additional Notes
The issue originally began after we published an update that used a different event method to trigger Disable Matchmaking then before.
We quickly restored our original implementation, but the issue remained.
The only successful fix was reverting the entire island to the older revision and publishing that revision again to live.
However, when we later took that same working revision, made several simple unrelated changes like editing the weapon pool, and published a new update, Disable Matchmaking broke again.
We have tested:
- Verse activation
- Device-to-device activation
- Agent-based events
- Non-agent events
- Returning to the previously working matchmaking implementation
None of these consistently resolve the issue.
At this point, we are effectively unable to update the island because publishing a new version appears to reintroduce the issue, even when no matchmaking-related systems have been modified.
Based on the reproducibility around publishing/reverting revisions, we suspect this may be an issue with the backend matchmaking state or how published island revisions are being processed rather than an issue with the Round Settings Device logic itself.
To provide more details, I attached a link showcasing the exact changes made between the fairly clean push where we only made minor changes with 0 relation to the event that disables the matchmaking currently (which is a timer device on 5 minutes). It used to always be timer device until we made a change for it to be verse + trigger disabling it which broke it, went back to timer device but issue persists when updating.
Some finals notes:
We’ve done such extensive research to make sure there is nothing we’re doing that is causing it and pretty much thought of everything including replacing the round device with a new one. We dont know what happens if we decide to update again, but we’re scared to do so as we have hurt our playerbase a ton with this already.
I have tried to cover every detail in this report, but due to it being so extensive I can imagine it can get confusing, I would be happy to run through this 1 on 1 as well!
Thank you for taking your time to look into this!