All trigger devices are being triggered by test players on startup (v36.00)

[ReasonableTrout]

Summary

Since the 36.00 update, I am seeing every trigger device in the level being triggered on startup. This is happening in a map with test players. Every trigger is triggered once by every test player (so the bug goes away if you disable test players).

Please select what you are reporting on:

Unreal Editor for Fortnite

What Type of Bug are you experiencing?

Devices

Steps to Reproduce

1: create a new empty project
2: create a new verse device in a file called test_device.verse and paste this code into it:

using { /Fortnite.com/Devices }
using { /Verse.org/Simulation }
using { /UnrealEngine.com/Temporary/Diagnostics }

test_device := class(creative_device):

@editable Triggers : []trigger_device = array{}

OnBegin<override>()<suspends>:void=
    for(Index->Trigger : Triggers):
        spawn {TriggerLoop(Trigger, Index)}

TriggerLoop(Trigger:trigger_device, Index:int)<suspends>:void=
    loop:
        Trigger.TriggeredEvent.Await()
        Print("Triggered device {Index}")

3: compile verse and drag an instance of the new verse device into the scene.
4: Add 3 trigger devices to the scene. Make sure they are spread out and nowhere near the player spawn points
5: Populate the ‘Triggers’ array on the verse device with the new triggers
6: In island settings, enable ‘Debug’, set ‘Test players on start’ to ‘Custom’ and set ‘Number of test players’ to 5
7: Launch the island

Expected Result

I would expect to see no debug output unless I go and walk over one of the triggers

Observed Result

I get the following output on startup:

LogValkyrieBeacon: [3881] (ValkyrieBeaconClient_2) MinigameStateChanged: EFortMinigameState::WaitingForCameras
LogVerse: : Triggered device 2
LogVerse: : Triggered device 1
LogVerse: : Triggered device 0
LogVerse: : Triggered device 2
LogValkyrieBeacon: [3881] (ValkyrieBeaconClient_2) MinigameStateChanged: EFortMinigameState::Warmup
LogVerse: : Triggered device 1
LogVerse: : Triggered device 0
LogVerse: : Triggered device 2
LogVerse: : Triggered device 1
LogVerse: : Triggered device 0
LogVerse: : Triggered device 2
LogVerse: : Triggered device 1
LogVerse: : Triggered device 0
LogVerse: : Triggered device 2
LogVerse: : Triggered device 1
LogVerse: : Triggered device 0
LogVerse: : Triggered device 2
LogVerse: : Triggered device 1
LogVerse: : Triggered device 0
LogVerse: : Triggered device 2
LogVerse: : Triggered device 1
LogVerse: : Triggered device 0
LogVerse: : Triggered device 2
LogVerse: : Triggered device 1
LogVerse: : Triggered device 0
LogVerse: : Triggered device 2
LogVerse: : Triggered device 1
LogVerse: : Triggered device 0
LogVerse: : Triggered device 2
LogVerse: : Triggered device 1
LogVerse: : Triggered device 0
LogValkyrieBeacon: [3881] (ValkyrieBeaconClient_2) MinigameStateChanged:

Platform(s)

Windows PC

Additional Notes

The problem doesn’t happen if you turn off ‘triggered by player’ on the trigger devices.