The library doesn't save turfs and objs, it just saves type paths. There's a more efficient way to store the data but I'm not too concerned.
This is a library for creating instances of maps, not for saving and loading .dmm files. You have to be aware that maps may be instanced when designing the game so it's not a big deal that it doesn't save every var you can edit in the map editor - you just have to be aware of this. I plan to include some parts of the library (either demos or stuff in the actual library) that make it easier to create maps that save nicely and work when instanced (ex: ways to associate switches with doors).
Just throwing this out there. So long as you make it convenient for people to override your load and save functions, I don't think it'll be too big of a deal.
The library doesn't save turfs and objs, it just saves type paths. There's a more efficient way to store the data but I'm not too concerned.
This is a library for creating instances of maps, not for saving and loading .dmm files. You have to be aware that maps may be instanced when designing the game so it's not a big deal that it doesn't save every var you can edit in the map editor - you just have to be aware of this. I plan to include some parts of the library (either demos or stuff in the actual library) that make it easier to create maps that save nicely and work when instanced (ex: ways to associate switches with doors).