Feedback talk:User/BlackNova/Guild Officer Kick Limit

Or

Guild leaders don't promote idiots that they don't trust. This option requires zero programmer time. -- FreedomBound 23:01, 4 May 2011 (UTC)

Ideally yes, but sometimes leaders misjudge someone's character and someone they thought was trustworthy turns out not to be. All it takes is 1 person(officer) to cause a lot of grief to everyone in the guild. This would help limit the damage that a single person could do, and save a lot of effort from the leader and officers to remedy it. It's happened before in some of the large guilds, and this would help it from happening again. As far as programming time goes, compared to other projects I'd consider this 1 pretty small and simple that could help a lot of people in the long run, although you wouldn't be able to judge its success in traditional terms.BlackNova 00:41, 5 May 2011 (UTC)

Just the fact that it's happened before should help prevent it from happening again. Guild leaders should be more careful if they know this has happened before. Not everyone needs to be an officer, though that seems to be a common theme. I don't think this would be quite so simple a project, either. Just the interface changes would require a lot of work, and the Live Team only has one coder. -- FreedomBound 00:49, 5 May 2011 (UTC)

Well if they only have 1 programmer then I doubt this would be a high priority project, but I would imagine it would be similar to the interface changes they made when they added hero battles. I'm not ingame so I can't check the details but if I recall they: added a tab to the hero panel [in this case guild panel], added a drop-down menu to an npc [in this case 2 to the guild panel, no npc required], added a lot of background support code [in this case probably little: add a variable to accounts and check the account's kick counter, preventing the kick from occuring if it matches the guild's kick limit].

As far as learning from experience goes and being responsible, both of those are important. However this would prevent new guild leaders from having to learn that the hard way, and experienced leaders who have a momentary lapse in judgement from making a grave mistake. At the least, having the option available (and set) would give leaders one less thing to worry about. I know some guilds, in order to prevent this from happening, promote all their members to officers (which creates its own problems), while others take screenshots of its members list in case an officer does start kick a lot of people, neither being an ideal solution.

Theoretically, this would be akin to the 'enter a character name' prompt at login. Some people would use it (entering a character name each time = setting a limit) and some won't (have remember name selected = leaving it as no limit). Some people won't use it, but those who do want/need it will be glad it's there. Also, it wouldn't harm how guilds currently operate, but could discourage any players with evil intents.BlackNova 02:12, 5 May 2011 (UTC)

I guess part of the problem is that I've only been in a small guild where if someone leaves, you notice pretty fast, and you know who's missing. I suppose the guilds that have max members and no other connection would have problems with it. -- FreedomBound 02:30, 5 May 2011 (UTC)

I understand what FreedomBound is trying to say, but sometimes it just doesn't work that way. One occasion, one of my officers' account was hacked, and while stealing all of my officer's stuff, this hacker took some time to be extra douchey and kicked all of my members. This guild died after this. In the alliance I'm currently in, it has happened where an officer, who HAD been trustworthy, just ends up going bat-shit over something, perhaps he'd been short changed some how. FOrtunately, our alliance is strong enough to support and repopulate guilds where this happens. Sill, I'd like to see something like this put in place. I say that understanding that its unlikely to happen, but I'd still like it. Perhaps in GW2.--Will Greyhawk 08:29, 16 May 2011 (UTC)