Foamy wrote:I had initial reservations, but they were answered by your addendum.
I have only one minor niggle remaining, the lack of sharing with entire guilds.
People use outside DBs now between several guilds sometimes, I don't see why it shouldn't be an option in an AE-run DB. To put it simply, if an AE-run DB doesn't offer what an off-site DB does, it won't cut down on people using scripts by much at all.
Sub-guilds are lame, but I will use them as an example. Why should a guild not be able to see every scrap of info from it's subguild, after both GMs have agreed permissions? I think as well as being able to set a limited number of players from outside your guild with access, you should also be able to set a limited number of guild IDs. By way of a compromise, perhaps you can only see a reduced amount of info from these linked guilds, and not the full shebang. I don't know, I've had a few too many JDs to give it proper thought, but I know I would like to see at least a limited guild sharing feature on an AE-run DB.
Besides that small point though, a well-presented solution to a topic that seems to have been discussed since the dawn of time. I fully support it.
Ya thats partially what I argued for the most part. As suggested it lacks versatility for the players as a whole. It more aims at the idea that unless you are in the guild at the time then you will take tons of handicaps because of it. Also it greatly benefits some guilds over as explained in some of my previous posts. Having the DB slightly split from the actual guild itself or at least opening it to player IDs rather would make it easier to do more with it that you cant do if its locked strictly to the guild. Its also partially why I wouldnt mind seeing it more aimed at cost is based on slots and those slots you can fill with whoever from whatever guild.
As an example with your setup on fenix your guild is more or less 3 different guilds FYAD, MODS, and RAVE. As the idea is suggested either you have to be one guild or you cant effectively use the DB. With a slightly split DB where slots can be filled you could have the leadership fill some of those slots and then increase the number of slots to fill up enough of the members that you want to actually use the DB.