ShadowTiger
05-18-2013, 09:40 AM
So imagine you give your quest to some testers so they can test it. Rather than having to post screenshots with no idea of the internals of the bug, they can actually go inside of the quest to see the screen/map number for themselves, and any ZQuest-savvy users can see why the bug is happening and offer suggestions. There could be a "L1 Quest Password" so that absolutely no writing of the quest, or even ripping of the graphics or music or script, could occur. Only analysis.
Or, imagine people working on a group quest where one person is doing the graphical work, and some other people are doing the building of the quest. There could be a password to build the quest, but not alter anything graphical or Dmap related. Only access to build from the combo page, without affecting the combo page itself. Screen data and tools are of course accessible.
So this is where having multiple access levels comes in. It's a pretty interesting concept, yes?
Or, imagine people working on a group quest where one person is doing the graphical work, and some other people are doing the building of the quest. There could be a password to build the quest, but not alter anything graphical or Dmap related. Only access to build from the combo page, without affecting the combo page itself. Screen data and tools are of course accessible.
So this is where having multiple access levels comes in. It's a pretty interesting concept, yes?