Exult Forum

working the wells in the game....

I put the bucket on the hook and I can't get it to go down the well...

Any thoughts?

No problems here in SI and BG. What version are you using?

And what exact well and which game? Or is it any well in either game?

Do you physically drop the bucket on the well? Or do you double click the bucket then target the well? I only ask because some people, over time, forgot a few game mechanics. If you double click the bucket then target the well, the avatar should automatically go over and start turning the crank.

I figured it out, but here is why I ask...I found a few places where the game locks up for about 10 seconds...

1. Go to the big gray building behind the observatory in Moonglow and get a few crates, stand the crates up on eachother to make stairs and double click the switch...

2. If you place a bucket on a well rope and then double click the bucket

3. If you walk past a building with a lot of action going on inside


1 and 2 I believe the reasoning is it is trying to do something that there isn't anything to do, so it maybe gets stuck in a loop for awhile, then gives up...???

3. I think possibly the exult engine may be trying to run whats going on in the building and outside the building at the same time...


what do you guys think?

What speed is your CPU? I have these kind of problems all the time. In fact, I posted a bug about it a few hours ago.
The thing in the bug tracker is probably similiar to 1 and 2, but 3 may be related to pathfinding. I've noticed that the pathfinding can be excruciatingly slow sometimes, especially when the NPC's can't find a path.

Not replicatible here. Going into the planet room is fine. Placing a bucket on a well then double clicking it is fine.

I've got a athlon @ 1.36gig with a radeon 32meg ddr and running the game at 400x300 with 2x scaling. (The best resolution IMO to play the game).

mine is a 400 celeron 160 ram ->soon to be 950....regardless, of the speed though that shows that there is some king of issue regarding those things

Roman: You're on the right track about the slowdowns. The bug is that an attempt to find a path for an NPC will fail, which may be correct, but then we'll keep trying again and again. It's tricky to get this right because, if we stop trying altogether, the path might become available (like if you open a door to a room where a monster is trapped inside).