Understandable. It looks like Native SketchUp can have subfolders. But I will say when the first version of Tag folders launched it was buggy, and I lost a very complex model I had invested a lot of time on, so I have been hesitant to use folders much. It would be awesome if you could get that working but I can see it’s a huge ask. I have already had to manage single layer grouping out of fear of crashes, yours has way more functionality that was not available before with the Any or All options. I can make a main group for Pipe then marker level can be each building, and I can apply the objects carefully with multiple markers. I’ll share my model when I get a few buildings set up.
I especially hope you’re testing it on a backup model. We’re still in beta testing. 
I started on a dummy data version and have had zero problems. The large plant model I am trying it on today has a few versions and several back ups. I can report I haven’t had any crash issues on the newer machines, and I would say it was my older machine with a modified OS that has been our only issue so far. On the larger model, I have noticed so far, any clicks in the plugin do take a few moments to update in the model. But no crashes or other issues. 
@mark.perrah Which beta version do you currently have installed? I also addressed performance optimizations in the latest versions. Maybe try comparing on a large model to see if there will be a noticeable difference.
If I were you, I would definitely use Tags and FolderTag for everything that can only be in one place (Building, room in a building) and Marker for everything else that needs to have multiple Markers on it. Native TAGS will still turn on and off faster, since they are directly inside the Sketchup core and Markers, due to the plugin principle, can never achieve the same speed on a large model. I have been using Folder Tags in version 2021.0.339 for years without any problems.
I had updated to beta 14 starting on the large model. I have a messy tag configuration starting off. I need to clean up my model a bit before I can give a meaningful review. I was asked to add things to each building by the company at different times so it was kind of a hodg podge combination. And I learned a about dynamic components along the way and tried incorporate those as I progressed. And managers of each building ask to see only their portions making tag groups a challenge. You plug in would have been a dream come true 2 years ago, but I’m glad, excited and thankful its finally here.
This is how I think I will rebuild my model Tag/Marker groupings:
| Tags Folders | Markers | Option B | |||||
|---|---|---|---|---|---|---|---|
| 10-Bldg | Fill Pipe | Tags | Markers | ||||
| 11-Production | Drain Pipe | 100 | Fill Pipe | ||||
| 12-Tank farm | Vent Pipe | 200 | Drain Pipe | ||||
| 13-Pack Off | Pipe Rack | 300 | Vent Pipe | ||||
| 30-Bldg | Sprinkler Pipe | 400 | Pipe Rack | ||||
| 31-Production | Flange | 500 | Sprinkler Pipe | ||||
| 32-Tank farm | Pump | 600 | Flange | ||||
| 40-Bldg | Valve | 700 | Pump | ||||
| 41-Production | Tank | 800 | Valve | ||||
| 42-Tank farm | Reactor | 900 | Tank | ||||
| 43-Pack Off | Platform | Reactor | |||||
| 50-Bldg | PLC | Platform | |||||
| 51-Production | Motor | PLC | |||||
| 52-Tank farm | Wall | Motor | |||||
| 53-Pack Off | Roof | Wall | |||||
| 60-Bldg | Fan | Roof | |||||
| 61-Production | Window | Fan | |||||
| 62-Tank farm | Containment | Window | |||||
| 63-Pack Off | Scrubber | Containment | |||||
| 70-Bldg | Chiller | Scrubber | |||||
| 71-Production | HeatExchange | Chiller | |||||
| 72-Tank farm | Storage Rack | HeatExchange | |||||
| 73-Pack Off | Ribbon Blender | Storage Rack | |||||
| 80-Bldg | Dust Collector | Ribbon Blender | |||||
| 81-Production | Dust Collector | ||||||
| 83-Pack Off | |||||||
| Production | |||||||
| Tank Farm | |||||||
| Pack Off | |||||||
| Shipping | |||||||
| Truck Dock | |||||||
| Yard | |||||||
| Fence | |||||||
| Landscaping |
The challenge will be isolating everything to apply the right combination of Tag - Marker(s)
@mark.perrah I have roughly evaluated Nested Categories, but I am not going to start implementing it yet. At this stage, this will be a huge intervention in the entire logic of AND/ANY evaluation.
But I have this idea:
Folders within Markers categories
In the current version of the plugin, it is possible to create categories (sections) and individual markers within them. Categories have ANY/ALL logic, which determines when an entity is hidden.
The idea assumes that within one category it would be possible to create folders - i.e. named groups of markers. This is purely an organizational tool for situations when there are many markers in a category and we want to divide them more clearly.
A folder would be able to:
- Collapse and expand - hide or display markers in it so that the panel remains clear
- Enable or disable all markers in a folder in bulk with one button
- Markers and entire folders could be moved by drag and drop - within a category, but also between categories. When moving a folder to another category, all markers in it will be moved with it.
Folders would have no effect on the visibility of objects in the model – the ANY/ALL category logic works the same as before, folders do not affect it in any way. They are just “sockets” for better organization of a larger number of markers.
What do you think about this?
Otherwise, try using a Marker filters. For example, for quickly turning certain groups on and off, this can work quite well at this stage. For example, you can simply add a group of pipes.
I will have to plan out my groupings to utilize the new abilities we have with your plugin. I am starting to grasp the possibilities. Like you mention to have tags for things that can only be in one place, and markers for things that can exist in multiple locations, then use filtering. I have to thank you for the latest update beta17 added the cursor focus to the marker text input box, This is a huge help. Thank you. Your app name should have a pronunciation key next to it that reads: (Lets Rock) because your plug in certainly does.
@mark.perrah You probably shouldn’t thank me for this… “the cursor focus”
I think that’s the native behavior of Sketchup. You probably just didn’t notice it before because it always worked in the plugin. But thanks for the compliment 
Well, between a few beta versions I had to re-write my markers and I remember getting frustrated starting to type a few times and my screen was jumping everywhere because my shortcuts were getting called. I had to make an effort to click the input box before typing. Not sure if it was my process in error, but this time the marker text input took focus as I was hoping for, so just happy its working (or I am working better? lol). Really enjoying this plug-in. Thanks for the hard work
Hello everyone. How do you like the idea of Automatic Level Markers?
This is the first test after writing a idea version of the additional module for Liserok Visibility manager, which I recorded on video. It is still a concept, but I see great potential for architects and designers.
Very impressive. So objects have controlled visibility based on its physical Z location. That could save a lot of time. And Good for troubleshooting too, if a part was designed or placed at the wrong height it can be easily discovered and corrected. This is a great idea.
Beta 19 - Done 
@mark.perrah Automatic Label Markers - done. You can donwload liserok_visibility_manager_v.1.0.285_beta.18 (from the email where you have the order..)
I’ll prepare a manual for it later, but if you’re interested, you can try it.
This looks amazing. I’ll fire it up today. One thing on the first graphic. The levels for lower 2 and upper 2 are both 3500. I think the upper should be 5000 possibly?
Each level has a lower and upper Z-level. The levels are independent of one another. By default, the second level starts at the top of the first… and so on.
You can easily leave a gap between the levels or have them overlap. If that makes any difference for assigning markers.
The numbers in the screenshot are just an example… The height of the levels doesn’t have to be the same.
Plugin beta 18 working on win 11 pro, sketchup 2024. Getting the objects to react to visibility commands took some trial and error. I had to select the objects then click the apply check box. then clicking hide or show eye for each level did nothing. then hiding the main group eye still did nothing, but now clicking each level eye works as expected.
Oh, right. I was testing the AI-generated image and I didn’t notice this hallucination.
It’s really time to put together that guide. I’m not at my computer today, but this needs to be set to “All” depending on how you add the main level mark to objects. In category raw.
(attachments)
Quick info for beta testers: I’ve uploaded Beta version 19.
This is just minor tweaks to the Skins after implementing Level Markers.