Dr Brain

He was talking to nighthawk, not you.

(Sysop mode) Why fire "inactive" coders? It's not like there is any cost to keeping them on the staff list. There are as many dev spots as we want. They can't step down and hand their position to someone else, because that someone else would have already been hired. (Developer mode) lol

I'm not really worried about how it looks on the receiving end, just that it shows up in some form. My suggestion for ?starlight was only if you weren't going be continuum compliant. If you are, then there's no issue. And your arguments against something like ?starlight are flawed: 1) If the server DOES need to distinguish clients, it has to query all of them. That means packets to all clients, even though only a very small percentage are starlights. I personally don't think the overhead of a single packet is significant, but you brought it up. 2&3) Making mapping impossible is worse than making it mandatory. If bugs are discovered in previous versions, then with your capability system it'll be impossible to resolve (without adding a capability for no_bug_x, which I'm sure you'll agree isn't clean). 4) Continuum compliance is really not something you should be changing at runtime. 5) Can send it out of band, either using invalid message settings or by creating a packet for it. Or not worry that continuum users can disable their continuum compliance.

Won't happen.

Read your post, then read my post.

Doesn't work unless there are 10 players playing.

Or, a simpler solution: make salvo and thors not work at the same time.

It's not really possible to do turf and normal flagging in the same arena.

We've made some map changes, and we've changed the rewards around since last time, so I'm making a totally new topic for commenting. Again, the turf arena won't be going public any time soon.

How about forcing clients to say ?starlight when they log into a zone? At least that way I can detect the lack of color support.

Yeah, Sharp has been working on a map upgrade for ?go turf, to make it less spread out. The attachment idea is a nice one, but unfortunately, Continuum doesn't really work well with the server deciding who can attach to whom. I've been pondering some ideas for this. The easiest is to totally disable F7, and make an /?attach command, but that's hard on newbies.

The ammo display has issues when you move through more than one pack in more than a few seconds (as a bandwidth saving feature).

It'd be nice if Starlight would display all the color codes despite their context, since there's no way to discriminate between Continuum and Starlight in the code. Meaning, if the server sends a public message with no pid, just display it anyway. Also it would be nice if Starlight supported color code 79 (Fuschia: http://forums.minegoboom.com/viewtopic.php?t=8095). I plan on using all of these codes in Hyperspace (for menus), and there's no way for me to modify things on the server side to not send these codes to Starlight clients (like I'm doing for chatnet clients).

My buy macro is ?|buy -c 20 repel|buy -c 20 burst|buy -c 10 gun ammo|buy -c 10 bomb ammo|buy -c 10 thor I just hit it every time I'm in the center safety.

You're dead wrong about not getting prized negative thrust bonuses. You do.

This is a good question to which I have no answer. Arnk Dylie created the module, and knows it has been broken for a long time. I'm not sure why it hasn't been fixed. Either he doesn't know what's wrong with it, or hasn't had time to fix it (or some combination of the two). On the other hand, I'm not exactly free of blame. I haven't taken the time to fix it myself or write my own.

Yeah, there's very little do!@#$%^&*entation for pidgin plugins, and zero for protocol plugins.

I'm guessing there was only one person on the team, and they got the entire jackpot.

At my research lab, we use graphics cards z-buffers to simulate machining.

best web comic ever: http://www.xkcd.com/ Oh, and newspaper comics doesn't get better than Pearls Before Swine: http://www.comics.com/comics/pearls/

Angstroms per year? That's almost as bogus as furlongs per fortnight.

Look at Warbird:BulletDelay or something to that effect.

Better question is how they faked it.

The way things are set up, you can't lose more than 5 minutes of stuff for any given crash.

D1st0rt has moved the database to a faster server. Hopefully this will help reduce the number of crashes we've been having lately.