I would like to be able to give keys by specifing the guild and position rather then just by name only
For example:
A key for the commander of ORE which would automatically transfer if the commander changed

Perhaps a dropdown menu specifing the type of key such as
Name
Commander
lieutenant
Council
Member

Followed by entry for the guild tag or name

Keys would apply to everyone in that position so a member key for TGFT would allow all TGFT members access as long as they are members.

+1, but really the whole key system needs an overhaul. I suggest a new thread for this purpose, but I'm too lazy to start one.

No way. Our solution to fixing the outdated key system cannot be to rely on the even more broken and outdated guild rank system.

Fix it? no I am just trying to keep it livable....

Yeah but I have a feeling if Incarnate were to reply here he would say something like: "If we're going to do this we might as well overhaul and that's not high on the priority list"

We're stuck with it.

-1

I'm with TRS, lets not divert development resources to slap a band-aid on a bullet wound.

Itan uses a plugin for key distribution. There's no easy way to specify keys by guild though, since guild tags are not known to the client unless you have the character id, which isn't always available, except under certain conditions. Within your own guild, you can use positions as a determining factor.

I have been working on a plugin to pull guild information off the website. It's maybe 75% usable right now. I haven't done much with it for a month or so. I should finish it sometime. Then you could have your plugin pull from this one's data to get a full list of guild members.

Or we could just request a new function in the API. Perhaps something like GetGuildTagByCharacterName()

Uh that wouldnt help any actually - I want the key to be to the position and not the character so a key for the commander of BLF would point to whoever is the BLF commander but if the commander died suddenly and was replaced then the key would in fact point to the new commander automatically with no further intervention.

I dont see guild structure changing anytime soon but even if it does then this change is still usefull as the key could still be set to mistress just as easily as it can be set to commander....

I've never really understood why they are so tight with information through the API. Many other games both newer and older made it possible to query a player's guild rank and other information without having to jump through hoops.

A lot of what you request could be done easily if the API were a little less strict in regard to some of this information, without the devs having to do any sort of major overhaul to existing data structures.

+1 for complete key system implementation...

Most efficient solution is full adoption of keys for every entity in game and decent key management system...

So, a Person have a keyring of his own. When joining Guild, he gets a key to Guild's keyring, and thru that he access whatever his Guild owns, like capships, stations and future content.

That way, OP only requires that the Guild keyring have 4 sub-keys, for each position. That really makes sense, like making all your lieutenants as capship "pilot" and members as users... or Council members can manage a station resources and other members can dock...

* Give [KeyType] to [Nation,Guild,Player] {_name_} [___] (if Guild, 5th field is position)

Even Guild bank and Guilds Friend/Foe List can be tied to keys for easier management and flexibility. When Inc first proposed it, seemed that way it would be implemented, and now we only have a very initial draft on that.

-1 to OP.