Part of knowing What Revit Wants, is also knowing what it Does Not want. Sometimes, you can push the hack (or workaround) that step or two too far… and the result is unpredictable, buggy and kinda useless.
In the past, I have used various methods to create inplace or component families that are not ‘officially’ or natively available. In this particular instance, I used the IFC round trip method to force the creation of an Inplace family with Category set to Rooms. I also pushed this into a Component (loadable) family.
Great! I have Room families. But guess what? The result is unpredictable, buggy and kinda useless.
In fact, if you open these projects, make some Room Separation lines and then try to place a Room, I would estimate that in 95% of cases, your Revit has already crashed. The families will not accept a tag, and they won’t schedule. They seem to just sit there, destabilizing your Revit environment. So why post about it? Well, basically so that you can add this workaround to the aforementioned list of something that Revit (currently) does not want.
I have provided both 2013 and 2014 versions for your download and testing here:
RVTs that will crash Revit