You're making the assumption that the binvar would be containing static data and needs to be persisted through sessions in the first place. Binvars make it easy to do double buffering for any animation style drawing, something files would *not* be able to do efficiently. If you don't understand its usage, don't blindly claim it's not useful- there's no basis for shooting down an idea just for the sake of it. What exactly is there to lose here? The implementation is actually already there in /drawcopy- mIRC just needs to extend that functionality to read data from a binary var.
