Play Home Contribute Github Join Us! Discourse Staff Members Github Contribution Guides Team

White Rabbit - (Can't Catch It){SOLVED}

#1

I believe some weird things are happening in this level. I’m writing in JS.

This code I believe should be working, but my hero stops halfway like it can’t understand where the lightstone went.:

// Follow the lightstone to navigate the traps.

while (true) {
    var item = hero.findNearestItem();
    if (item) {
        // Store the items position in a new variable using item.pos:
        var itemPos = item.pos;
        // Store the X and Y coordinates using pos.x and pos.y:
        var itemX = itemPos.x;
        var itemY = itemPos.y;
        // Move to the coordinates using moveXY() and the X and Y variables:
        hero.moveXY(itemX, itemY);
    }
}

However, it doesn’t work as it’s supposed to. Seems to only work when I make the hero.move(itemPos) to bypass the variables:

// Follow the lightstone to navigate the traps.

while (true) {
    var item = hero.findNearestItem();
    if (item) {
        // Store the items position in a new variable using item.pos:
        var itemPos = item.pos;
        // Store the X and Y coordinates using pos.x and pos.y:
        var itemX = itemPos.x;
        var itemY = itemPos.y;
        // Move to the coordinates using moveXY() and the X and Y variables:
        hero.move(itemPos);
        //Bypass all the variable storing in the middle and just hero.move to itemPos
    }
}

#2

When you do move it partialy moves there. But the moveXY command moves to the exact pos of the item @Eric_Kidwell

#3

So how do I store the item’s exact position so that the hero moves there instead of it’s partial position?

Here’s what the first code example ends up looking like:

ie:

// Follow the lightstone to navigate the traps.

while (true) {
    var item = hero.findNearestItem();
    if (item) {
        // Store the items position in a new variable using item.pos:
        var itemPos = item.pos;
        // Store the X and Y coordinates using pos.x and pos.y:
        var itemX = itemPos.x;
        var itemY = itemPos.y;
        // Move to the coordinates using moveXY() and the X and Y variables:
        hero.moveXY(itemX, itemY);
    }
}
#4
hero.moveXY(item.pos.x, item.pos.y);
#5

Yeh, I would expect that to work as an alternative to storing in variables the x and y position, however, it get’s teh same results as the comment suggested way of doing it with variables.

#6

Mabye is is an equipment problem The lightstone could be to far away for the hero to see. i used the same code and it worked fine because i hade the best glasses

#7

That be true since I only have the 2nd pair that the game gives.

However, when I pause to say the item’s position, then it get’s further into the maze, but loses due to time. Which would tell me that the hero should be able to see it (range) around the corner if he can get that far.

#8

Mabye you can get the ring of speed to make you faster

#9

Sure, I’ll try that. I’ve already got the maxspeed boots.

1 Like
#10

The softened leather boots is a little faster. Try that

#18

This issue is still happening in Jan 2019. It’s that exact spot where my hero gets stuck.

I’ve loaded the level multiple times, and when this particular maze setup appears, my hero stops pathing at this exact spot, and the level fails with “ran out of time”.

I doubt it has anything to do with our computers.

while True:
    item = hero.findNearestItem()
    if item:
        # Store the item's position in a new variable using item.pos:
        item.x = item.pos.x
        item.y = item.pos.y
        # Store the X and Y coordinates using pos.x and pos.y:
        
        # Move to the coordinates using moveXY() and the X and Y variables:
        hero.moveXY(item.x, item.y)
        pass

#19

The invisible obstacles might have been the cause

#20

I don’t understand what you mean by “invisible obstacles”, particularly with this level. Could you please explain?

#21

It’s a thang that keeps the player from going to a weird place. Just consider it an invisible wall

#22

Weird. Thanks for the heads up. Seems odd that it would be on a map which has only 1 solution.

#26

I see the same issue when I use a faster hero on this seed. The lightstone moves before your hero can pick up the next set of coordinates. Then your hero can’t find the lightstone. Switch to a slower hero and it works. Another thing I noticed, the faster hero has a weird XY coordinate on the position just before this. It is higher than it should be which might be why the lighstone moves sooner. You can see the angle that it creates.

moving%20lightstone
lightstone%20XY