Neither (completely ruined and slight annoyance). Somewhere in between.
I am really, really pissed if something gets spoiled for me. The game will still be fun to play, but not being surprised actually is making it more about the destination and not the journey, if I may take your wording. When you already know what will happen, and no matter what you do, it won't matter, then the journey isn't as fun to go through. It is difficult for me to articulate, but knowing exactly where it will go is just me playing, waiting, to get there. Otherwise, I'll be surprised left and right where it goes. It's just more fun.
Did you ever went home with a random girl or guy after going out? Sure, if you knew it was coming it would still be fun, but it's so much better when you didn't know until it happened.
For some games, I don't want any spoilers. I didn't want to see what the new Normandy looked like in the Mass Effect games. Not a story spoiler, but still a spoiler for me. I want to experience it all myself, not through someone else. It does make it different and while it doesn't ruin the game, it does make it less fun.
Especially because I'm pissed off about being spoiled. If I suspect something to happen and it does, I'm not surprised, but that's still better than knowing 100% sure what will happen.
That said, I remember this guy on the Borderlands 2 forums who complaint about a post because it consisted the name of a location. Not tied to the story, not tied to the game in any meaningful way. Just a location name. A moderator removed the post because of 'spoilers'. That goes too far. I think my Mass Effect Normandy issue already goes pretty far. I don't like people who consider every little thing a spoiler. But I also very much dislike people's attitude when they don't think something is a spoiler just because they didn't give away the story's end. 'I didn't spoil the end exactly, so the experience isn't spoiled for you'. Gah. They don't get it.
Log in to comment