I know you're not going to like this suggestion, but I'd rather see this as a proper "creatable list helper" stream...  It may be a bit more work now, but if we need to do some server-side filtering (or debugging) in the future, that will make it much easier to work with than an opaque ```buffer``` member.  I don't imagine there would be more than a small handful of creatable types actually used in the stream, and a NetMsgStream object already exists as a sample of how to handle the streaming and compression within the DS codebase.