Zone.exe Crashes on Zone Boot?

[Cailin]

For some odd reason, zone.exe is crashing on me with what seems to be no reason. I mean, it doesn't even give me any detailed debug.

Map ./Maps/ecommons.map not found.
[Status] Weather should change in 3688 seconds
Init: Loading zone lists, zone state or spawn listElapsed time: 170105
Spawn2count: 238
gmspawntype_count: 2
npc_count: 239
npcloot_count: 347
Zone state loaded.
, player corpses, traps
, timezone data - Done. ZoneID = 22; Time Offset = 0
Successfully loaded Zone Config.
[Status] Loading Objects from DB...
[Status] Loading Ground Spawns from DB...
[Status] Loading doors for ecommons ...
[Status] Done loading doors for ecommons ...
[Status] Loading AA information...
[Status] Loading Merchant Lists...
[Status] Loading Temporary Merchant Lists...
[Status] Zone Bootup: Ecommons (22)
[Status] 162281 New client from ip:192.168.0.200 port:2209
Read group ID for 'Lakalia': 0

Lakalia being my character. I'm running this all off of my own system; I've got a MiniLogin setup going.
World.exe tells me this:

Attempting autobootup of Ecommons (22) for Lakalia
Zoneserver SetZone: 192.168.0.200:8780 Ecommons (22)
Enter world: Lakalia: Ecommons (22)
Zoneserver SetZone: 192.168.0.200:8780 Ecommons (22)
Received unknown opcode: 0x0376 size:0 bytes
192.168.0.200:2200: TCPConnection::RecvData(): Error: 10054
Removing zoneserver from ip:0.0.0.0 port:0 (192.168.0.200:8780)

I've been able to create characters fine, it's just when I've used #zone to get to another map I get booted and then this happens. Odd considering how it did work before.

I don't think it's the ecommons.map file that is the culprit (it's missing), as the server does work for every map that I've tried to get to by just walking into it. What am I doing wrong here?

Oh, and another thing: World.exe isn't good at handling multiple characters on one account when used with MiniLogin. Eqgame.exe will always disconnect from the server (or the other way around?) if one tries to log-in to one of their characters when the account's got two or more on it. It must be something to do with the accounts table in the database - the character field only ever lists the first character on the account.