I am not VCL.

If I was him, then for what reason would I be hiding my identity?

Btw, i have looked into the processLockMap function.

Now I see why your configuration isn't giving you the desired results.

Next formula's apply for your configuration:

$lockX = int($config{lockMap_x}) if ($config{lockMap_x} ne '');

$lockX += (int(rand($config{lockMap_randX}))+1) if ($config{lockMap_randX} ne '');

The smallest X coordinate outcome is 400+1 and this coordinate is ofcourse not walkable.

I was bored, so I went to that map myself to check out the 'optimal' coordinates.

-top walkable y coordinate: 372

-bottom walkable of the north island y coordinate: 240

If we get the arithmetical mean of these coordinates we get the middle y coordinate of the northern island: (372+240)/2 = 306

Then we need the distance from this coordinate to first 2 coordinates: 306-240=66

Try next configuration without any modification to the source, i'm almost certain that it will work like how it is supposed to.

lockMap_x

lockMap_y 306

lockMap_randX

lockMap_randY 66

Tough, there is not much buggless code thats any more complex than: print "Hello World\n";

So by looking at the code i actually found a very very tiny bug in it.

Every coordinate calculation in these two function blocks is similar to this:

int(rand($field{max}) + 1);

This piece of code has a minimal output of 1 !

But what about coordinate 0?

RANGE: 1- $field{max}-1+1

the code should be like this instead:

int(rand($field{max}+1));

RANGE: 0 - $field{max}

http://perldoc.perl.org/functions/rand.htmlGoing to commit this to SVN.

[EDIT 1]

you are right about that bug btw, for route calculation in the lockmap:

for y it only adds up to the top

for x it only adds up to the right

going to change that aswell soon.

[EDIT2]

The route calculation in lockMap is fixed now.

in svn