08-23-2015, 12:22 AM
From what I've heard, vanilla mine-craft uses four byte ids internally, then serializes them down to one byte ids for the network. There is nothing saying we can't do that to.
So the biggest issues I can see with forge block compatibility is increased memory usage (cChunkSegment would grow by 120%), and protocol detection.
Memory usage can be mitigated by making blockids an opaque class, then adding a compile time flag as to whether to support forge.
So the biggest issues I can see with forge block compatibility is increased memory usage (cChunkSegment would grow by 120%), and protocol detection.
Memory usage can be mitigated by making blockids an opaque class, then adding a compile time flag as to whether to support forge.