I’ve converted a map to UEFN after a copious amount of work, and when I went to test the map after converting it to UEFN by launching a session, it told me that about 10 or so of my devices were “disallowed” and refused to launch. I didn’t do anything to these devices beyond changing ONE setting, however this isn’t the first time this has happened. In both cases I had a system of RNG devices and triggers hooked up to item granters triggered by a tracker for opening chests to simulate the RNG of a custom loot pool I’d made. This time around it flagged several of my item granters, but the last time this happened it only flagged two of my RNG devices, and that time I didn’t even change any settings on them, literally untouched from the moment they left creative 1.0 the game told me they were “disallowed” in the message log after telling me it failed to launch session.
Steps to Reproduce
I guess just… set up a bunch of devices in creative 1.0 and convert the map over to UEFN, then try to launch session? I don’t even know exactly why it’s happening in the first place so I don’t know if it’s just my computer or what, but hopefully you can recreate it to help me see what I may have done wrong.
Expected Result
The program will launch a session of Fortnite, allowing the user to test the map.
Observed Result
It will fail to launch session, and if you check the message log via the pop ups in the bottom right it will tell you some of your devices are “disallowed” in Fortnite, and prevent you from launching session until said devices are deleted… unless I’m missing something, which I really hope I am.
If anyone has a way to fix this that doesn’t involve deleting the devices in question it would be greatly appreciated considering how much work it would take to recreate all the connections I have set up on said devices.
My first thought is that there might be something in the ‘loot pool’ that’s causing the error. (Like an array that references something in Creative 1.0, but that reference path has changed or does not exist in 2.0?)
Post the entire disallowed message.
Also, for best chances of getting a bug fixed we’d need to know how to replicate that disallowed error in a new level.
The problem is I don’t know exactly what caused it in the first place, especially since it’s a completely different device this time around being the item granters, so beyond simply telling you how the system is set up I can’t exactly provide you with a step by step process on how to replicate it. I’ll give you the error message first then give you the setup, that’s the best I can really offer you unfortunately.
The whole system goes as follows: A tracker to track the opening of chests, which triggers an RNG device, said RNG Device activates triggers, these triggers then activate more RNG devices facing a different direction for the sake of compactness, and those RNG devices then activate triggers connected to item granters that give the player a gun and a set amount of ammo corresponding to said gun. There’s one outlier item granter, one that gives the player materials, that also got hit by this, and it’s in a system of similar concept with triggers activated by an RNG device, not only to simulate the drop rate of metal to stone to wood, but also whether or not a trap should spawn as well.
I’ve… put a lot of attention to detail into trying to as accurately as I could recreating the drop rates from chests, maybe that backfired.
Actually no it wasn’t, I couldn’t even find the option despite having been told about it. I honestly would have liked to at least make a copy of the island for later use since I enjoyed last season but I guess it’s no big deal. That being said if you could tell me where to find said option I would greatly appreciate it as this season hasn’t been half bad either
Anyway, I was using the Survival Island template, with the mountains and lakes it seemed like a good base for what I was planning to do and gave me a good variety of terrain to work with.
Okay so I figured out the issue. After checking the devices in question I found they all had some sort of weird reference to something that had a strange name and was flagged. After checking to make sure the references weren’t tied to anything I’d placed down I found out that the issue was that the game had arbitrarily given all the devices in question nonexistent references, and once I deleted these references the game functioned as intended. Thank you for your patience in this matter but I’m glad I was finally able to get it all sorted out
Here’s a screenshot of one of the references in question from before I deleted them all:
