yeah so instead of typing all the guild members names, instead input their Tag. so if you wanted to add vpr, simply type in [VPR] into the guilds' field.

+1

+1

+1....

-1

Core Design Goal: No guild exclusive content. That means, in any reasonable interpretation, not designing content that can easily be used to exclude people not in a guild. Guild alliances will just make keys strictly tags only as a matter of policy and that will be the end of it. It's the reason they weren't designed like this from the outset. Guild-only access monopoly is the inevitable result.

Can't believe FC 1+'ed it.

Bullshit. I mean, seriously, why are you even spouting this nonsense? Exclusive? That's exactly no different than it is right now from the perspective of an unguilded hero like me. So it would be a little easier for a bunch of incestuous pighumping ninnies to manage, big deal. How would that in any way impact my ability to rally some like-minded punks to blow shit up and take it for ourselves until we get bored and wander off to do other things?

What the devs are actually against is content that is only allowed by the engine to guilds, with no way for a motley assortment of unguilded players to have it too. Like guild banks (which you may have noticed we actually have anyway, so clearly they make occasional minor exceptions as well).

The reason keys weren't designed like the OP from the start was because that wouldn't have been half-assed enough. Guild Software has a reputation to maintain!

Anyway.

Character names are allowed to start with a [, right? So just directly entering a guild tag won't work without a checkbox or something to tell it you're specifying a guild rather than a player.

There should also be an "Add all members of my group" button.

In my post where does it say that it is guild exclusive? There would still be individuals listed. I don't see your point and agree with Rin entirely.

Hahaha. Worth a shot.

This has been suggested ever since keys were introduced;by now most guilds have I suspect the ability to give keys according to [guild].

I would agree that it should be part of a revamped key system rather than via player written plugins.

I wasn't +1-ing the idea that only guilded players should be able to get keys, just that it should be possible to add an entire guild easily. As it stands, should I take a station, and want to grant all [ORE] access for instance, I can only add CD, and hope she can add the rest, as I have no clue who is in ORE, and who is active, etc.

Faille.

Gee, thanks, Faille!

+1 to OP

Nothing about this is exclusive. An individual could make use of it as Faille just described.

It is a much-needed improvement for key management.

My post was under the assumption that you were suggesting you could add a guild tag to the access list and anybody who joined that guild would be granted automatic access. What you are actually suggesting is just an interface mod which already exists in plugins today.

If a guild tag was added, they should have auto-access/revoke when someone joins and leaves the guild. Why shouldn't it? It still doesn't make it any more guild exclusive since you can *still* have individuals on it.. This does not exist in plugins, and nor should it have to be made for plugins instead of fixing the stupid system, and doing it right.

The relatively easy way to implement this would have been to look at the name entered on a key and if it was surrounded with brackets then treat it as a guild tag and add the key to everyone in the guild. Unfortunately, brackets are acceptable for use in character names. So now they have to implement some other system for dealing with this.

While it would be nice to have this builtin, frankly I'd rather they not waste time on it at this point. This same feature can be handled with plugins as was mentioned, and there are more important things that need to be fixed (like the key system in general) or implemented.

The best implementation, imo would be a toggle to identify whether the entered text is a guild or a player. If a guild, look up all members of the guild and add them to the key. New players joining the guild would have to be added manually, or someone could perform the guild add function again.

The above would be easy to implement, and avoid the problem of someone joining a guild and auto-getting access.

Or have two separate fields.. Guilds and Individuals, which strikes me as hella easy to do.

It would be easy, but then you have to deal with the idiotic use case of someone entering data into both fields. Do you ignore, throw an error, etc. It's better to have a toggle that allows one field to serve as the input.

I don't see any problem with a guild auto-granting access is, from a gameplay standpoint. The whole point of a guild is to make it easier to manage a group of players who are in a long-term alliance.

The only reason TRS opposes this is that it would lessen the advantage conferred by the silly guild-only plugins that certain dweebs like hoarding.

+1 like I have proposed many times...

And finally more people are realizing that "Guild-Exclusive" is not the same as "Guild-Friendly"...

Guilds must be able to own capships, stations and storage. And again, Guilds can own is not the same as "only guilds can own"

The simple way to do so is creating a keychain for each Guild, and Guild members have access to that keychain... so the same key system can be use for people and guilds...

And get over it:
-Guilds already do most of Capship and Conquerable Stations gameplay
-A Guild own something is not the same as a guild member own that same thing