Next Gen Explorer now available for everyone!

Hi, this is a known bug with searching. I was going to look into it soonish.

2 Likes

Hey, a recent update changed the visibility of some of these. I’ll double check what went amiss there. Thanks!

1 Like


is there any chance we can get an option to choose whenever we want these dropdowns to exist or we want the menu to show all options at once?

I’m having a hard time getting used to hierarchy dropdown even after months of using this new explorer.

Please, this is affecting my workflow and I don’t think I can keep using this new explorer until this is fixed.

This is a very good explorer update, however these dropdowns are making things harder.


add it as an option in here to disable/enable the dropdowns.

I think it’s ALOT more useful than “Increment names for new instances”, so I’m not sure why it doesn’t have an option while the other option exists.

Why is this in Lua? Why not C++? Why is it so much slower compared to the existing, superior explorer. (it’s because it’s in Lua and the engineers are slowly being replaced with Large Language Models) Why do I see the pointlessly abstracted GoodSignal module in place of the existing, better, RBXScriptSignal implementation. Why are the Scripts in it held up by Twigs and Duct Tape. Why can I see their hilarious errors in the console. Why are you actually planning to replace the current explorer with this. Why do you care so much about meeting your quota with pointless updates no one asked for? (It’s to satisfy the investors.)

1 Like

Sorry for the holdup, it looks like you guys actually resolved the issue this week. Thanks for looking into this!

1 Like