attackfighter
Magister
- Joined
- Jul 15, 2010
- Messages
- 2,307
Forcing him to stay is kind of a morale thing, no? I'm sure there's no consequence to it but I was usually not too unhappy to get rid of 'em. As for Cernd I always thought he had to go take care of the grove or something. Still, I never really used them -- I preferred to make my own characters via the multiplayer trick and just recruit in game NPCs for their quests, then to abandon them like the pieces of meat that they are.
BG 1's dungeons may not be very long but most are completely pointless, or are made tedious for the sake of tediousness. Even the whole cloakwood thing is dull with only the end being worth while because of the strong party you encounter before entering the mine and the actual boss fight.
With Keldorn he asks to leave your party for a few days to spend time with his family, then when you see him again he says that he's planning on giving up adventuring for good but that he's willing to help you complete your quest first. You can then keep him or not (it's obviously more honourable to let him go, but the way the dialogue paints it it's not a huge deal and everyone's understanding if you want him to stay).
With Cernd you just drop his kid off at the druid grove or something. I've only done his quest once, so I can't remember the specifics. Although one thing I do remember about his quest is that you can abuse some game mechanics in order to kill the demi-lich and that on the demi-lich there's an item called "Cernd's child", most likely a leftover from what was intended to be a longer questline. I found it interesting at the time.
The one issue I have with BG2's NPCs is that they all come pre-dual classed, so you can't really experiment with all of the cool new kits and whatnot that BG2 has, except for with your main character. Making an entirely user made party is a good way to bypass that and experiment with most new classes without having to dedicate an entire playthrough to each one.