This Molag Bal quest is a great example of the game depriving the player of obvious choices. The game designer just half-asses it and then shrugs, “Well nobody’s forcing you to complete the quest.” If nicest thing you can say in defense of a quest is that the player isn’t physically compelled to endure it, then what you have is still a terrible quest.
This isn’t even that hard to solve. When the player rescues the priest, right now your only choice is to either bring them back to be sacrificed to the dark lord, or just ditch them and leave the quest unfulfilled. But this latter choice isn’t really a choice at all. I mean, you can always come back later. You’re not rejecting Molag Bal, you’re putting him off. And he doesn’t even mind.
Instead of the player just abandoning the priest and ignoring the quest, just add a line of dialog or two. You tell the priest what Molag Bal asked you to do, he thanks you, and the quest is marked as complete. If we really need to reward the player, we can have the priest give the player a trinket before they leave.
There. Not a lot of work, only a couple more lines of dialog, and we offer the player the ability to take an obvious and reasonable course of action.
A stream-of-gameplay review of Dead Island. This game is a cavalcade of bugs and bad design choices.
The No Politics Rule
Here are 6 reasons why I forbid political discussions on this site. #4 will amaze you. Or not.
Spec Ops: The Line
A videogame that judges its audience, criticizes its genre, and hates its premise. How did this thing get made?
Pixel City Dev Blog
An attempt to make a good looking cityscape with nothing but simple tricks and a few rectangles of light.
Silent Hill 2 Plot Analysis
A long-form analysis on one of the greatest horror games ever made.