Loading a map with objects that don't exist crashes FastDMM

[Qbopper]

This is a bit of a fringe case, but...

Dream Maker has a catch for when a map file contains nonexistent objects (usually created when you update your codebase and an object was removed for whatever reason) where it asks the user to change the file path for each "nonexistent" object (which is really obnoxious and slow, like everything in Dream Maker). FastDMM doesn't catch these errors nicely, and will immediately crash once you scroll over a tile containing one of these nonexistent objects. To be clear:

-create a map using objects 1, 2, 3, 4, and 5
-a codebase update removes object 5
-load the map in dream maker and it asks you to remove/provide a new path for all instances of object 5
-load the map using fastdmm and it crashes when the program sees a now nonexistent object

[monster860]

Well I suppose there's the option of creating an "invalid object" subtype.