What is the most bat-guano-insane thing in Blender that you can't believe they haven't fixed yet?

[thinsoldier]

@zeauro

The real issue is that Collection Instance reference for placement is relative to a fixed world location, instead of parent location.
At the moment, you want to move the orignal collection + instances, everything goes unexpected.
What it is unintuitive is to be careful about the placement of original collection, and to be forced to never move it.

@thorn

But I can’t change the position of a collection myself, and it’s inherent position screws everything up when I try to move it instanced. It’s the worst of both worlds.

Is there anything else you should know about collection instances?

I’ve seen a few youtube videos recently claiming to show all you need to know about collection instances. They leave out a lot of useful information. The first thing you should know is that a single object can exist in multiple collections. I haven’t seen a tutorial mention that since around the release day of 2.80. Something plaguing tutorials lately is they don’t demonstrate multiple objects in a collection being used as a collection instance. I’m still seeing many comments asking about this…

@Romanji

Since Collections don’t have a transform I am forced to use empties and Collections - the additional (undesired) complexity is counterintuitive and wastes attention and concentration.

They are not meant to have transforms. You can hide collections from the outliner and not see or think about them most of the time.