in reply to Todd Mitchell: > When making maps there is always the idea - if only I > had this...I should create a... and sometimes it isn't as > easy as tweeking an existing arch in a map > (although that should be encouraged). > Sometimes you want a new arch (like for summoning/creation > purposes) or need to modify the treasures file to make an > ability work. As it becomes easier to create maps, I believe > there would be more frequent modifications to the images > and archs. I completely agree to your point. A serious mapmaker often wants to, or even has to mofidy things like treasure/artifacts/ races file or add new arches/images. > I think there would be some benefit in discussing seperating > the arcs and the server a bit more than they currently are. > It would be nice if the Treasures and Races files were shipped > with the archs (or a package as you suggest) so you didn't > have to get the server download to modify them. Okay, sometimes it is annoying that in fact you need so many files from different locations and packages for mapmaking. However, I think the packages are quite okay and reasonable as they are. What should be done is to provide better tools to modify these things. For example, the editor could contain an up-to-date copy of the treasures file and parse it for seamless integration with the attribute interface. In the atribute window of a monster for example, you could then click on the treasurelist entry and get the list of items belonging to it. Then there could even be an interface or something to create new treasurelist entrys. Now I'm not saying I will code this anytime soon. But that's how things could get done. Generally that is my idea about solving the difficulties about map-making. The editor can make the transition between cryptic datafiles and easy-to-use interfaces. Andreas