D1st0rt

Depends on how rigid the stick is

Target was legit when I worked there

The idea is that the game will run as normal if nobody uses any commands, but errant behavior can be corrected

Who gave Al Gore keys to the weather? He's not being very responsible with them

Will the owner of this bot please get in touch with zone staff. Thanks.

shouldn't it include which attempt is failing or succeeding in case you send another request before you get the response back

I would be more worried about http://unixepoch.com/

That is correct

fixed

Blue, those three use 1477 colors 4553 colors 3141 colors respectively (not that we would, but in order to put those on a shirt you'd have to dither them)

Perhaps you should clarify the specifications, the impression I got from reading S!@#$%^&*'s first post was that it is to be something along the lines of what you would put on a t-shirt: static image (no animation) 3-4 colors max (plus alpha channel) multiple sizes (maybe a 500 pixel, 200 pixel, 50 pixel variety not just resized) no fancy effects

lol mojo county they should be adding lanes to the beltway, not worrying about what dudes can go into the ladies' room

you know what you should slow down? the rate at which i get kicked for sending commands

I could spend my time making a custom backend Syrus, or I could spend the time making things to actually use. I have a bunch of stuff coded for a previous version that I just need to get up to date with various updates and our own schema changes.

Then the changes we made were a success

...what?

This is more or less just a bandaid to patch up what we currently have for the time being

burn

Security is also very important, it should be structured in a way that lends itself to quick verification

I didn't mean wake up at a random time, that's not a good idea. You should set your alarm on something that will be near you at that time tomorrow (watches or cellphones are perfect)

People seem to ignore most green messages already. For private teams it's not a problem because we can have the team name say it in yellow, but pubs don't have that luxury. Maybe, like you suggested, when there is like a minute left on someone's flag timer we can send the messages to their teammates. The difference between the restrictdrop and forceneut commands would be that forceneut immediately neuts flags if you have somebody running away with them while restrictdrop simply prevents winning of the flag game

Yeah, that sounds better. One of the concerns I had would be with freqs that had little or no experience in the zone or with the commands

I've been tinkering around with the flag modules lately looking at ways to improve gameplay, and I have a couple of ideas that should help take away control of rogue players on teams. The first is adding a command like ?forceneut. If there is a single flag carrier on your team, you can use the command to vote for their flags to be neuted. Once a majority of the team votes to force neut, all of the flags that are currently carried by the flagger are neuted. It would only apply when there is one flag carrier, not for technical reasons but because it's harder to make a m!@#$%^&* informed decision and then determine what it is the team really wants when there are multiple people running around with flags. If you have a lot of rogue players on one team, you probably have some bigger issues you need to work out. Another is having it set up so that only players designated by majority vote are permitted to win. You pm the players on your team with something like ?letdrop and unless a majority of the team has indicated they are allowed to win, at the end of the flag timer the flags will simply neut instead of dropping. Hopefully this has been clear enough. What do you think, Hyperspace?

you know what's a good way to avoid getting shot? flying into the opening