Bouncer, Chiller, and Launch Pad are missing from the content browser

Summary

As of update v36.10, the bouncer, chiller, and launch pad traps are missing from the content browser

Please select what you are reporting on:

Creative

What Type of Bug are you experiencing?

UI/Tools

Steps to Reproduce

Open the content browser and attempt to find any of the 3 listed items

Expected Result

The listed traps should be available to equip and use

Observed Result

The listed traps are unavailable

Platform(s)

PC/All

Upload an image


I found that this is due to someone adding the hidden tag to these traps for some reason?
image



Confirmation has already been given in the original post, but here it is in video format.

3 Likes

i don’t know how i can provide more information that this

The fact that in depth issue reports like this continue to get these kind of responses baffles me. Anyways, for the second time now on a bug like this, here’s a guide on how to fix the issue.

The issue in question here is caused by the Creative Tag “DeviceUEFNHidden” being inside the following trap item definitions. This should not be inside of these.

  • TID_Context_BouncePad_Athena
  • TID_Context_Freeze_Athena
  • TID_Floor_Player_Launch_Pad_Athena

Open up each of the listed trap item definitions, search “Creative Tags”, and remove the tag “DeviceUEFNHidden”. That is it, all you need to do.

1 Like

“Needs more info” is not always related to wrong or lack of information on the bug report itself, as already explained by some staff on other posts, that can mean that the internal team needs to study the case to see why it happened/the change occured, if it was on purpose by some decision, or if it needs some extra steps internally before actively working on a fix for it.

It does not always mean that the report is wrong or lacking information to reproduce or understand it, is just a generic message that is also shown for the internal devs when they need to investigate things that may relate to the issue indirectly first

1 Like

Ah, misunderstanding then, I really feel like logically Epic should probably make the Jira posts for things like this public so that would be more clear, similar to what Mojang does for Minecraft’s bug tracker… oh well.

Thanks for clarifying!

2 Likes

Thanks a lot for explaining, that status made me lose hope on bugs I reported before you explained it

1 Like

This was already fixed in the latest update

FORT-932292 is ‘Closed’ as ‘Fixed’. The issue will be addressed in 36.30.