gb revamp - Page 2

**Wyzcrak** · 02-12-2007, 03:28 AM

Quote:

Originally Posted by ChopStick

Another command that you might want to keep in mind is passgb. If for whatever reason (ie you're going fade) and you think you might not be able to respond, it will passgb <playername> to another opted in player.

After several regulars requested it (and because it's a good idea I should have thought of to begin with), I've improved the 'passgb' command to display a list of opted-in players when invoked without any arguments.

**Ferris Bueller** · 02-12-2007, 05:08 AM

rock. on.

Dr. Pepper PhD. · 02-14-2007, 01:46 AM

Spoke with you tonite about the map change thing wyz

**Wyzcrak** · 02-15-2007, 01:23 AM

Quote:

Originally Posted by Dr. Pepper PhD.

Spoke with you tonite about the map change thing wyz

Opt-ins were (intermittently) not being persisted. This should be fixed now. If it's not, let me know.

aesop rock · 02-19-2007, 09:28 PM

Quote:

Originally Posted by Pokerface

What is 'gb'?
'gb' is a console command which allows one registered player per team to remove unregistered players who continue to violate server rules despite being warned. Any use of the command must cite a documented server rule, and the command must always be used professionally and respectfully. Users of the command keep the server great, while abuse of the command can remove its user from the server.

Why should I opt-in to 'gb'? How do I do that?
To opt-in to 'gb', issue the 'sharegb' console command. Read and follow the directions you're shown.

The communal motivation for doing so is that the server dies without rules enforcement. Not "sucks", but "dies". Your friends will leave, and you will flat-out lose your favored server. So, looking at the big picture server, your use of 'gb' helps the server survive and thrive.

The personal motivation is that all players who opt-in to 'gb' and its responsibilities become last targetted (among non-SMs, registered or not; SMs are never bumped, by anyone) by the slot reservation code when it bumps a player to make room on the full server for an incoming Supporting Member (SM).

If our rules ever change sufficiently such that the administration thinks old 'gb' opt-ins have become obsolete, opt-ins can be cleared en masse, forcing everyone to review the new rules and opt-in again.

Cool. Using my past experience and cross-referencing it with this post, I think I basically get the gyst. However, for the sake of those who are less familiar with TG and clarity, I pose a couple questions.

First, What exactly does it mean to opt-in? Is it some sort of self-nomination step? Then how is the one(?) person who gets GB selected? Do we vote?

Secondly, what do you mean share gb? I have no idea what this means. Who can issue this command, and when? What does this accomplish besides helping the server not 'suck' or 'die'? :P Also, Once again, I could go figure it out, but as long as we're stating new rules, I think we should be as specific as possible.

I did read the entire sticky, and hopefully my questions weren't directly answered there, but I didn't see anything specifically explaining those two concepts.

**Wyzcrak** · 02-19-2007, 09:33 PM

By using the 'sharegb' command, you're agreeing to do just that: share the 'gb' command. This is the "opt-in" step.

Opted-in players are then selected methodically by the plugin during games. I don't recall how at the moment. I think it finds the opted-in player on the appropriate team who's been on the server the longest (most likely to know what's going on).

Yeah, I think that's right. I recall thinking, while I was writing it, that picking the opted-in guy who's been there the longest guarantees (short of client crashes, etc) that the opted-in guy who joins the empty server to seed it can rely on his having the 'gb' command to deal with any unregistered troublemakers who pass through before the regulars arrive.

1Stop|Beowulf · 02-19-2007, 11:16 PM

Quote:

Originally Posted by Wyzcrak

By using the 'sharegb' command, you're agreeing to do just that: share the 'gb' command. This is the "opt-in" step.

Opted-in players are then selected methodically by the plugin during games. I don't recall how at the moment. I think it finds the opted-in player on the appropriate team who's been on the server the longest (most likely to know what's going on).

Yeah, I think that's right. I recall thinking, while I was writing it, that picking the opted-in guy who's been there the longest guarantees (short of client crashes, etc) that the opted-in guy who joins the empty server to seed it can rely on his having the 'gb' command to deal with any unregistered troublemakers who pass through before the regulars arrive.

it seems to me like its just whoever joins the team first . . . that algorithm may exist, but as soon as someone opted-in joins a team, they get gb(they are the only eligible person on the team), so unless an admin balances, the algorithm wont have a chance to run(even then maybe not, i dont know how fast the code runs/with what delay).

but then again, i usually only pay attention to whether or not i have gb, and i rarely(if ever) join a team first (dont care which i play on, i usually let other people pick first), and am usually not the person who's been on the server longest, so its perfectly possible that none of my experiences mean anything.

Kerostasis · 02-20-2007, 04:04 AM

That seems like exactly the sort of bug likely to pop-up...

I know Temp-Admin and GB status rarely changes hands unless people are joining teams, and the first eligible person to join an empty team gets status pretty quickly, so its entirely possible that the "pick which person to hand it to" algorithm will usually be picking between a field of "one".

But then again, theres very rarely a reason to move status around during a game, so my observation isn't exactly surprising. I'd have to watch a situation where a bunch of people join a team in sequence, slowly, to be sure.

**Wyzcrak** · 02-20-2007, 08:57 AM

Yeah, that's a problem with the design.

I might fix that one day.

Dr. Pepper PhD. · 04-02-2007, 01:04 AM

As a generality, I have noticed that every time gb is triggered it says something about all uses of the command are recorded. Being that I feel that I use it a lot, I sometimes wonder if I am gonna get a big NO yelled at me should I do it again. 9 out of 10 times I use it, it is because people don't have a microphone and cant hear mine. And the other is usually language.

I guess what I am wondering is, should someone check it is there also statistics on when they are used? i.e. for me, earlier in the afternoon when no SM's or admins are present, while registered members are. I just am afraid of getting a nastygram about using it.

As an estimate I probably average 3 gbs in every 2 play sessions. Play sessions usually consisting of at least an hour and half. 4 to 5 games.

**Wyzcrak** · 04-02-2007, 01:26 AM

If your intentions are good, and that's evident (as it likely is in all of the cases you're concerned about), the most you're going to get is a PM from an admin letting you know where you screwed up.

We're grateful for the help maintaining the server. As long as you don't let the power go to your head, or put some asinine quip in the kick reason (etc etc), you're better off using the command than anything else.

Just go with your gut. If you think we'd remove someone, and you've warned them, go for it. If you're not sure about a situation, whether you acted or not, you can always PM an admin later, asking if you screwed up. Dialog is fine.

The command is there so regulars will use it. Use it.

Stupid · 04-02-2007, 08:58 AM

Remember - all games are demo'd and demos kept for (an undescribed) period of time. YOU (and your gb's) ARE BEING WATCHED.

1Stop|Beowulf · 04-02-2007, 02:57 PM

big brother is watching you. but he just wants a hug.