A new mapmaker package is now available from the download page.
This is the latest B5 release of the public maps, arches, and server, and Gridarta.
In theory you can just unpack this mapmaker over your existing B5 one. In practice, this may overwrite some of your changed maps and arches!
The thing to do is to backup the arch and maps directories from your existing map maker first, then unpack this one. This way you won't lose stuff.
@evilasa: I don't think that's something to laugh about ;|
It has been fixed though :)
Lmao @ Lippy
I guess that's another hack I'll have to incorporate into my working copy...
I think the permissions thing is a Vista problem. Though not sure why, since Gridarta is running in/from my user area where (presumably) it tries to create the file.
Don't forget dinosaurs like to do things the way they've always done it - but I take the point about more control over where events are added :)
Huh? It's not new. It's the (you'll hate this) correct way.
By forcing everyone to do it this way it means this area can be more easily improved and developed to automatically catch newby mistakes.
For example, to not allow events to be added to floors or floormasks (which I don't think G does yet do) and to not allow/query adding two same events to the same object (which G does do).
And by removing event objects from 'normal' objects it means they can't, for example, be placed directly on a map square.
I can't reproduce the permission or absolute path issue. So maybe a Windows G/Vista bug?
Why force people to adopt a new method of adding events, when the previous way was perfectly satisfactory? I hadn't even noticed the event tab existed, btw.
I don't understand why this particular object should be treated differently from any other object.
Also, it can't create a new script file (always supposing that someone wanted to do that, rather than link to an existing file) because of permissions.
Also, if you browse to an existing script file it creates an absolute rather than relative path.
By all means enhance the UI to add additional features, but why not allow people to use the same method they have always used, if they so choose?
Re: pickmaps. Yeah, this needs fixing. I think I know how. Need to submit a Gridarta feature request.
Re: event objects. Well this is precisely the point. You shouldn't be adding them directly in this way (and now can't). Use Gridarta's events tab on the parent object.
Which also brings up a new thing added. In the View menu is now an event objects option. This will show objects with an event object in them, which means you can see where the scripts are on a map.
Don't forget to save any private pickmaps you made first, in case they get overwritten.
And I'm not sure what effect moving event objects in arches will have in Gridarta: if they disappear from the special tab, how can you add them to something's inventory?
I knew someone would ask this. ;) (It's a reasonable question)
Well unfortunately we don't maintain a changelog for Dai (and I'm not going to fall into the trap of starting one myself which is then not kept uptodate by other devs because they assume 'Smacky will do it'!).
However, I do post fairly comprehensive threads in the Daimonin project forum board about most of the large-scale changes I make, and eventually I incorporate the mapper-interesting ones in Daipedia (go to the Mapper guide and then Map Wizardry).
There is a proper changelog for Gridarta and I included it in the mapmaker this time (editor/ChangeLog).
What is different in this one?