local void Damaged(Arena *a, Player *p, struct S2CWatchDamage *damage, int count)
{
    chat->SendMessage(p,"You took %i damage. c=%i",damage->damage->damage,count);
    chat->SendArenaMessage(ALLARENAS,"someone took dmg");
   
    return;
}

mm->RegCallback(CB_PLAYERDAMAGE,Damaged,ALLARENAS);

I <cmod> loading C module 'pymod' from 'pymod'
'import site' failed; use -v for traceback
Traceback (most recent call last):
  File "<string>", line 1, in ?
ImportError: No module named os
Traceback (most recent call last):
  File "<string>", line 1, in ?
ImportError: No module named os
Traceback (most recent call last):
  File "<string>", line 1, in ?
ImportError: No module named os
Traceback (most recent call last):
  File "<string>", line 1, in ?
ImportError: No module named os
ImportError: No module named copy_reg

--edit-- also:
E <pymod> can't import cPickle

--edit2-- and after ?shutdown:
M <net> [Cheese] [pid=5] unknown packet type 165
M <net> [Cheese] [pid=5] unknown packet type 165
E <module> error unloading module playerdata

--edit3-- sometimes its this instead:
M <banners> {0} [Cheese] bad size for banner packet
M <banners> {0} [Cheese] bad size for banner packet
E <module> error unloading module playerdata

9 Virtual Servers
asss allows one server process to apear to clients as several di?erent servers. The primary
advantage of this feature is that players connecting to all virtual servers are treated the same
internally and can move between arenas and communicate as if they connected to the same
server.
To create virtual servers, you have to tell the net module to listen on more than one port.
You do this by creating additional sections in global.conf named \Listen1," \Listen2," etc.
Each setting must specify a port, and can also optionally specify a virtual server identi?er, and
a speci?c IP address to bind to.
Virtual server identi?ers are used in several ways: if you are using an arena placing module
that supports them (e.g., ap_multipub), the server id will be used as the arena basename to
place players who connect through that port in.
The directory module also supports virtual servers: it will create one directory entry for
each virtual server. The server name and description can be di?erent for each virtual server. To
specify them, create \Name" and \Description" settings in the section \Directory-servername"
for each virtual server identi?er. If either of those settings is missing from that section, it will
fall back to their values in the \Directory" section.
Finally, an example to make this all clear:
;; global.conf
;; listen on 3 different ports:
; players connecting to port 2000 will be send to a random arena.
[Listen1]
Port = 2000
; players who connect to 5000 will be sent to pb1, pb2, etc.
[Listen2]
Port = 5000
ConnectAs = pb
; port 7500 will send them to aswz by default, and so on.
[Listen3]
Port = 7500
ConnectAs = aswz
; this will force the server to listen on an internal interface only
; and send those players to a secret arena:
[Listen4]
BindAddress = 192.168.0.23
Port = 3300
ConnectAs = #secret
[Directory]
;; point to the directory servers you want to be listed on. using
12
;; default port and password.
Server1 = sscentral.one.com
Server2 = sscentral.two.com
;; now describe what this server is called by default:
Name = A Testing Zone
Description = Testing happens here.
[Directory-pb]
;; specify the name and description for pb:
Name = PowerBall
Description = Play with balls!
[Directory-aswz]
;; specify only name for aswz:
Name = A Small Warzone

Redirects:<name>
Type: String
Settings in the Redirects section correspond to arena names. If a player tries to ?go to an arena
name listed in this section, they will be redirected to the zone speci?ed as the value of the
setting. The format of values is 'ip:port[:arena]'. */