Page 1 of 1

BG: problem with parrot treasure?

Posted: Sat Nov 09, 2002 4:33 pm
by AJ
I recently looted the treasure lair parrots tell you about in BG. There are two rings lying out on the ground in the cave, but I can't get them because they are on the other side of the pool and apparently there is no path to them. I know they were there in the original (checked my old notes), but I don't remember them being un-getable. Since getability is a function of the terrain and not the game engine (?), it doesn't make sense. Any thoughts anyone?

Re: BG: problem with parrot treasure?

Posted: Sat Nov 09, 2002 5:07 pm
by ToasterThief2
It's possible to get all the treasures. Perhaps you need to reenter the cave from a different angle?

Re: BG: problem with parrot treasure?

Posted: Sat Nov 09, 2002 5:46 pm
by Neutronium Dragon
Yes. At least in the original, it wouldn't let you pick things up if you were at the wrong angle (most likely that it couldn't easily find a path and so assumed there wasn't one).

Neutronium Dragon

Re: BG: problem with parrot treasure?

Posted: Sat Nov 09, 2002 6:25 pm
by AJ
There's no path, I promise. I simply can't walk to that side of the cave. It might have something to do with caltrops. There are some in the cave that you can't see (and thus can't move). I think they might be blocking the path somehow.

Re: BG: problem with parrot treasure?

Posted: Sat Nov 09, 2002 6:43 pm
by Blah
Well I've just tried it on exult 1.1 and I can't get the rings either, but the caltdrops are not invisable and can be moved. Some of them are hidden behind the cave's perspective.

Re: BG: problem with parrot treasure?

Posted: Sat Nov 09, 2002 7:23 pm
by Darke
Yep. Even if you remove all the items in the cave (which IIRC is what you
had to do to get to them in the original), you still get a 'BLOCKED'
message when trying to move them.

Re: BG: problem with parrot treasure?

Posted: Sun Nov 10, 2002 12:06 pm
by AJ
Okay, since more than one person has confirmed that it's not just my memory going bad, I'm going to enter a bug report on this.