I think I've found the issue with families introduced in recent builds and fixed it for the next build. However, it reverts back to a bug where Family.Count returns the wrong count. That's less serious, but it's hard to see another way to fix that. It'll probably be left as an open bug for now.