Is there any chance that we could have more complete MySQL tables in the CVS release.
I know you dont want people to be able to read things like full quest definitions, which seems fair enough, but it would be a LOT easier for me to design quests if the tables were complete wrt to all non-secret data.
From what I can see, that means that all tables except characters , npc_triggers and quests can be exported without restrictions in the state that they would be when a new live server is installed.
As far as the tables that can only be partially exported are concerned, I would guess that, if they are set up with the simplest quests at the start of the table (eg the magic shop gold ore quest - which is trivial to complete) and the more important quests later, then the tables could be partially exported to only include the info relevant to those quests and people like myself who want to design new quests would have relevant examples that they could look at ingame, instead of an example quest involving the rescue of Princess Leia from the Death Star (!?).
In that way, people running their own server and designing quests using it would have all the NPC\'s that are already in place, without any quest information beyond the basic quests.
Having the NPC\'s installed in the CVS tables would mean that new quests would not inadvertently place two NPC\'s in the same place and that, assuming the quest dewsigner knew what the quests were from playing the game, that they could place augmentary characters without problems.
NB for the purposes of quest design, an ingame command something like /teleport_to char would be very useful for testing quests.
Would also be very useful for GM\'s I suspect as would /teleport_to querent so that GM\'s go teleport directly to someone they were talking to on the help channel.