- Jun 11, 2019
- 141
- 193
Eh, agree to disagree. There's not much I hate more than an author ruining a good mystery with a subpar reveal, ESPECIALLY when the reveal would not and did not enhance the experience in any way. Like the Ents in LOTR; there is so much history and lore there, but it's irrelevant to the story being told so it's not included. And although knowing these things does give more weight to Saruman's actions and the Ents' grief, the story still comes first.Very hard disagree here. If there's one thing I hate, it's deliberately leaving questions unanswered and leaving them "up to interpretation". Speculation is only fun if there's actually the possibility of it going somewhere, and a question with no answer is just... asfdgfakds. Especially if it's on purpose. It doesn't matter if the canon answer isn't ideal.
Edit: To be clear, I'm not saying that there should be a bunch of meaningless worldbuilding about stuff that has absolutely no relevance to anything. Another thing I dislike is when people try to make a world look bigger than it really is by talking about events that didn't affect anything or places that nobody has ever been to. (I'm looking at you, Elder Scrolls.) But in a way, it's the same issue. The story should be made of substance, and any mysteries should be a transitory stage between a question and an answer.
Edit 2: Actually, most of the examples I can think of the latter were really just adding onto the former. Like how Skyrim introduced a whole event in the backstory where the moons disappeared and the Thalmor took credit for bringing it back, and then it's like "lol this won't be addressed at all in this game or any other, it's a mysteryyyyy".
With Going Deeper specifically, the entire setup (dungeon(s) popping up that nobody knows anything about but they big threat) gives me Lovecraftian Lite vibes, so I've been approaching the story behind the dungeon in that vein. If that's not what the author is going for, more power to him. But if it is, I'd prefer to express my opinions.