Re: [DM-dev] DM status update

[Henningsen <al...@gl...>]

>The plan is, though, as you say, a _purely_ flat model. The hierarchy's gonna 
>go completely on the back burner for now. This probably means going back to 
>the render-as-we-read approach for the dungeon grid, and it probably means 
>problems with saving a rendered dungeon back to "dungeon data" format. We'll 
>get through it, though.

Render-as-we read? As I see it, we read the data in and use it to initialize
the DungeonMaker internals (nothing's rendered at this time). The we run the
Dungeonmaker process (Crawlers crawl...), and then we have a data structure
that can be used any which way, either to render a dungeon or to initialize
another data structure used by the calling program. The second alternative
will be the norm in production use of the code, the rendering we currently
do is just for demonstration and testing.

Saving a dungeon back to "dungeon data" format is not what we want to do.
All we need is the initialization data and the random seed, and we can
generate the dungeon in under one second flat. Calling programs will have
their own formats, and it will be very easy for them to write code to save
the dungeon to that format, if desired.

Sorry to hear about the QUB leak. Hope you got the right tools to catch it.

Peter