We’re aware that some device options of the HUD Controller Device were added Fortnite Creative and UEFN early. Since these options are unfinished and could cause issues, they will be removed until further notice. We’ll keep you posted.
Why not just keep them as experimental? 
Like an experimental editable section?
This could be a thing.
I like the separation going on with the new experimental devices directory, adopting that on editables as well so that there are 2 sections in the editables kind of like the folder directory for devices seems like it fits a common form factor and would be a good solution to including experimental device features since moving the whole device into the folder’s not really appropriate.
Perhaps logic gated contextual enum. In order for it to remain palpable to users perhaps you include the original options from the stable featuers enum list in the experimental list, then gate it behind a contextual logic gate.
stable_options:=enum:
StableOption1
StableOption2
StableOption3
experimental_options:=enum:
StableOption1
StableOption2
StableOption3
ExperimentalOption1
ExperimentalOption2
@editable
User_Choices:stable_options=stable_options.StableOption1
@editable
Experimental_Version:logic=false
#I'm not sure how you do contextual editables but that would use Experimental_Version = true and if possible disable the User_Choices since it's now overridden by Experimental_User_Choices
@editable
Experimental_User_Choices:experimental_options=experimental_options.StableOption1I’m sorry, but I don’t understand anything about Verse 
The setting was available in FNC, and that is what I used as I normally use it.
Oh sorry, basically having an option in the device that you would turn on (would start off) that would enable the experimental settings. So once you turn it on you would get new options including those experimental options.
Just to show that you know that it may be a cause of bugs if you do turn it on.
1 Like
Exactly