In Fortnite Creative 1.0, players are unable to properly join an island when a round is already in progress. This makes it extremely difficult, and in some cases impossible, to properly test and publish projects that are designed to support players joining mid-round.
This makes it extremely difficult for Creative 1.0 creators to properly test their projects before publishing them.
Many systems need to be tested specifically with late-joining players, including:
Team assignment
Spawning
Classes
Inventory
Player progression
Statistics
Devices that initialize when a player joins
Game-specific mechanics that need to work for players joining mid-round
Because creators cannot reliably reproduce and test the real matchmaking scenario of a player joining an ongoing round, projects may be published with bugs that cannot be properly detected during development.
Please select what you are reporting on:
Creative
What Type of Bug are you experiencing?
Live Edit
Steps to Reproduce
Create or open a Fortnite Creative 1.0 island with a round-based game.
Start a playtest with at least one player.
Allow the round to begin.
Have another player attempt to join the island after the round has already started.
Observe what happens to the joining player.
Expected Result
The player should be able to join the ongoing game and be correctly assigned to the appropriate team/spawn, allowing them to participate in the current round.
Observed Result
The player cannot properly join the ongoing round, preventing them from participating as expected.
Sometimes it let you, but you are completely glitched, I have a mutation zone that gives you items at the start, with the first player it works propperly, but when the other player join later, hd get send to the hub or just appear without weapons, on a team that I didn’t selected…
This also happens on my friend’s island, it isn’t a mistake of my island.
Ok awesome. Thank you so much for the additional info, this has helped us a ton to understand what you all are experiencing. We’ll be looking into this.
Hi @LuciAntonio2016, seem that the bot posted the incorrect wording
From what I can tell from our internal ticket, this should be fixed in the next release 42.20.
Once that release is out could you try again and let us know if you still encounter it