This class really doesn't seem versatile enough. Sure, it's written like a queue of changes, but couldn't that be done using java API? Unless this is designed as a low-level block change interface (which absolutely reeks).

Personally, I'd be more inclined to take 'structure' (read: diff) based writing, to allow CraftBukkit to handle the internals of how to efficiently apply it; it's not particularly safe to assume this type of implementation can handle robust changes to the minecraft internals work.