silentwings

closing for now - can be reopened in future if traffic reduction is needed

It looks to me like status / battle status would be the best candidates for this, but it would add alot of overhead, for not much gain. Not sure if...

and avoid relying on md5!

ChanServ in db is better, doesn't need userid=1, just should check if its there on boot and add it if not. Since in long run the plan is to kill...

I can't see how else it could be done.

> add a flag: "trusted account" maybe?! presence of verified email address can now be used, and it is not practical to obtain more trust than that in normal users

given the limitations of the GIL, and that we already pool db connections, i'm not sure we would gain anything here

n2s, since channels save stuff to db, can't use battle_id for channel name

I'm working on making Battle a derived class of Channel!

n2s ideas: FORCETEAMNO, FORCEALLYNO, FORCETEAMCOLOR, FORCESPECTATORMODE, HANDICAP should be deprecated/combined into a single key=value command e.g. SETUSERBATTLESTATUS this leaves the following commands needing changes: JOINBATTLE LEAVEBATTLE KICKFROMBATTLE SETSCRIPTTAGS REMOVESCRIPTTAGS ADDBOT...