fort_hud_controller.HideElements() doesn't work

As far as I can tell, the HideElements function just doesn’t work.

I have the following function to set up the UI and as written, nothing gets hidden.

    InitializeUI() : void = 
        HideList : []hud_element_identifier := array{
            creative_hud_identifier_round_info{}, 
            creative_hud_identifier_round_timer{},
            creative_hud_identifier_crafting_resources{},
            creative_hud_identifier_build_menu{},
            creative_hud_identifier_map_prompts{},
            creative_hud_identifier_minimap{},
            creative_hud_identifier_player_inventory{},
            creative_hud_identifier_player_count{},
            creative_hud_identifier_interaction_prompts{},
            creative_hud_identifier_elimination_counter{},
            creative_hud_identifier_storm_notifications{},
            creative_hud_identifier_storm_timer{},
            hud_identifier_world_resource_wood{},
            hud_identifier_world_resource_stone{},
            hud_identifier_world_resource_metal{},
            hud_identifier_world_resource_permanite{},
            hud_identifier_world_resource_gold_currency{},
            hud_identifier_world_resource_ingredient{}
        }

        Logger.Print("Configuring UI...")
        HudController : fort_hud_controller := GetPlayspace().GetHUDController()
        HudController.HideElements(HideList)

        # if (Me := GetPlayspace().GetPlayers()[0], UI := GetPlayerUI[Me]):
        #     UI.HideHUDElements(HideList)

If I uncomment out the “deprecated” method and use that instead, it works fine.

I haven’t seen any other reports of this and it seems pretty major, maybe I’m doing something wrong?

I don’t know if this is normal but your constants are not declared as they should

name : type = value

not

name : type := value

If it compiles then it shouldn’t come from this but I just noticed, try it maybe it’ll work :man_shrugging:

Also, as they are constants in a function scope you don’t need to specify the type, so :
name := value will also work

@Megaspace Thank you for your report! We would like to look into this further, would you be able to submit a bug report using the form available here? Fortnite Creative

Thanks for the tips, I usually just look for the red squiggles and get kinda lazy with which I should use.

I mean, they decided == is too confusing, but having multiple ways to set a variable isn’t. I’ll get it sorted eventually though!

Will do, I was just waiting to see if it was really a bug or if I was doing something wrong.

Yep, I get you, this Stevie-Moon posted on a thread of mine too, it doesn’t look like it knows what it’s doing…
Also hurts my feels to get answered by a robot, they could’ve used ChatGTP atleast :smiley:

Also, is your issue resolved ?

Well, the deprecated method works, but fixing the syntax didn’t help any.