I had to look this up cause it's my first time hearing about it. Was confused since it looks like it was made in a lab to sell cosmetics and capture an intersection of roblox/fortnite kids, but you can't do that unless you're F2P. As soon as I saw the price tag I immediately went "ohhhhhhhh..."

Day 5 of my 2025 Favorites is just the tiniest #EmotionalSupportSpood known to science, Mr Neonella camillae

Bug and I make regular pilgrimages to central Florida to see them. He's but a grain of black sand 🖤

Day 6 of my 2025 Favorites: There's a particular oak in a particular spot upon which for some reason I've found an adult male Phidippus richmani every year for the past 3. Little things like this bring me joy. And he looks like that 🥹
#EmotionalSupportSpood

If that's the case, why did Mass keep two actor LODs in the fragments? Seems pretty wasteful, no?

My best guess right now is that the more practical solution is to only have a singular Actor LOD and use something like the Significance Manager and Pawn Relevance to enable/disable things on it rather than replacing it with a whole new actor at a certain distance.

I've read just about every resource and dug through every sample project I could find on Mass/Crowd, and cannot seem to find an answer to these questions anywhere.

It seems to work reasonably well in standalone but when playing as client it doesn't seem to work at all. I noticed they have a separate trait for serverside actor representation but every example I've seen just configures that to be high-res actor only. Why? Who knows! It's not explained anywhere!

Like did it just not help that much with performance in practice? Or is this one of those things that they planned to flesh out and ran out of time?

Every example I've seen (including CitySample) sets the HiRes/LoRes actor representations to be the same asset. Was this an idea that was abandoned part-way through development for some reason? If so, why?