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)