[!!] Zombie Map not switching

[Warren1001]

I get on aBlockz and people tell me they've been on the same map for an hour...
http://imgur.com/1Imrxwa
They also said that the new map vote came up, and they got to pick which map, but at the end it never said "(next) map loaded.".
If there is an error, you'd have to get it from Ultima...

[HETAL]

Could be this bug again viewtopic.php?f=24&t=2170

[Warren1001]

Could be this bug again viewtopic.php?f=24&t=2170

Except that's a ForEach error, which was fixed in the one of the later versions i believe.

[Ultima]

Zombie is clean from errors.

[Warren1001]

It happened again...

[Ultima]

After i restarted i saw someone using this:

Code: Select all

[name] used /viewranks was set to guest ;-;

After that it crashed.
This command was already set on guest.

[dzienny]

Is there any plugin that make use of the available events? It potentially could cause such problem. Anyway, I will check the code and add some try catch statements to prevent excemptions from breaking the game flow.

[HelloWorldCool]

This sounds like a problem I had before...long long ago

It happened to me on lava maps, but who knows, maybe the reason is the same for zombie maps.
As far as I have experimented, the problem has to do with physics and such. When a map is saved in-game, the physics(and blocks) will be saved in THAT state. This somehow breaks the system by confusing it. So in order to correct this problem you need to set /save, /saveall and any other save commands to nobody.

And apparently you need to reset your database.dll or edit it if you know how to
If you want to see if replacing your maps works go ahead but...usually it won't. "Yet renaming them will work...why? The map settings are saved in the database!"

Keep in mind this log was a LONG time ago and I have no idea if this or any of the above still applies. I'm lucky I still have a copy:

Code: Select all

----11/19/2011 4:46:59 PM ----
Type: ArgumentOutOfRangeException
Source: mscorlib
Message: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
Target: ThrowArgumentOutOfRangeException
Trace:    at System.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument argument, ExceptionResource resource)
   at System.ThrowHelper.ThrowArgumentOutOfRangeException()
   at MCDzienny.Level.finiteMovement(Check C, UInt16 x, UInt16 y, UInt16 z)
   at MCDzienny.Level.<>c__DisplayClass17.<CalcPhysics>b__c(Check C)

[dzienny]

Unfotunately the error log is too old to be relevant. Anyway, I haven't found the root of the problem. Actually, I haven't investigated it yet. Mainly because it appears to happen very rarely, so it has a low priority. It will get fix though