Summary
I believe persistence is pulling incorrect information from round 1 into round 2. I have a simple loadout selector system where I use buttons to enable different loadouts using item granters. I cannot use classes, since I have a teleporter system already using classes and teams. The system works like this :
The buttons used have persistence enabled with auto save, initial state off, each player does NOT have their own state, and mutual exclusivity.
Button x selected for Loadout x (i think this would be saved) > Items are granted from item granter x > round 1 occurs > (i think button states would be saved) > round 2 starts and i use triggers with round devices to load the state of each switch on round start > another trigger with a slight delay is used to then check the state of switch x > on checked switch ON sends signal to grant from item granter x.
I am 99% sure i tested this exact system in the past and it worked flawlessly. I am baffled that I recently tested my game again and i started getting problems. The issue is that
When i flip switch 3, I do get the items from item granter 3 for round 1, but in subsequent rounds, I only get items from item granter 1, which is strange because switch 1 was never on, I should be getting the things from Item granter 3 from round 2 onwards. I double checked everything, and there should not be anyway that i would get items from Item granter 1 if switch 1 isn’t activated.
the only explanation would be that data from the backend isn’t being loaded properly, and somehow data saying that switch 1 is activated is being loaded even though it is not.
Please select what you are reporting on:
Unreal Editor for Fortnite
What Type of Bug are you experiencing?
Devices
Steps to Reproduce
use persistence to load button information from different rounds using autosave.
Expected Result
Button x, which is activated from round 1 should be enabled.
Observed Result
the functionality from button x isnt happening, however functionality from another button is happening, a button that was never turned on, and a button that should not be on. I assume this is being pulled from the backend.
Platform(s)
PC UEFN
Additional Notes
I would do more research on clearing / loading persistence data at different points, and see if this solves anything.
I AM 99% I TESTED THIS IN THE PAST AND NEVER GOT AN ERROR LIKE THIS. THIS IS NEW, EVEN WHEN USING THE SAME RELOADING A “BUG FREE” VERSION FROM REVISION CONTROL. I AM BAFFLED.
Thank you so much for all assistance rendered.