Full Games List
Featured Games
New Games
Reviews
Media
Images
Blogs
Game Updates
Images Feedback Summary
Game Design Highlights
Tutorials
Articles
Scripts
Utilities / Plugins
Resources
Engines
Engine Bulletins
What is Makerscore?
Past Events
Achievements
Misaos
Forums
Post History
Chat
New to RMN?
Full Store List
RMN Music Pack (free)
DO YOU PUT SPOILERS IN REVIEWS?
Posts
Pages:
1
unity
View playlists
CloseGiven that Reviewrim is here, and that I'm planning on writing my very first review soon, I had a question. What do you do with spoilers in a review?
In most cases, I'd opt to just not mention the spoiler at all, but what if it deeply affects how I feel about a game? Do I include it under hide tags? I guess I'm torn because I feel that its important to the review but I don't want to spoil the game for future players.
In most cases, I'd opt to just not mention the spoiler at all, but what if it deeply affects how I feel about a game? Do I include it under hide tags? I guess I'm torn because I feel that its important to the review but I don't want to spoil the game for future players.
I personally have no qualms with putting spoilers in reviews, since it's pretty much up to the reader to open them up. And you don't necessarily have to type up a bunch of important story details in your review for it to be a noteworthy recommendation.
It really depends on the game, of course.
It really depends on the game, of course.
If you do have unmarked spoilers please preface your review with spoiler warnings in big bold letters so readers know. If you do hide them then it isn't such a big deal as long as you say why something is hidden (because they are spoilers). Some people want to read reviews when deciding to playing a game, please think of them and don't spoil games needlessly.
Aegix_Drakan
6037
I HATE unmarked spoilers. Hate hate hate.
You don't need to tell me the super spoilery parts of the story like how is has a happy ending or that kind of thing.
If the spoiler is gameplay related then there's a lot less problems with poisting spoilers. (for example: "About halfway though the game everything changes and it's not action RPG rather than turn based and it's kinda hard to get use to this sudden shift" IS a spoiler, but you really should put in in your review, since it's highly gameplay related.)
You don't need to tell me the super spoilery parts of the story like how is has a happy ending or that kind of thing.
If the spoiler is gameplay related then there's a lot less problems with poisting spoilers. (for example: "About halfway though the game everything changes and it's not action RPG rather than turn based and it's kinda hard to get use to this sudden shift" IS a spoiler, but you really should put in in your review, since it's highly gameplay related.)
I've placed hide-tags when I talk about my experiences playing the game. Such talk will, invariably, contain spoilers. Which is why I put it under a hide-tag. This is way to circular for it's own good.
Why am I half-expecting a review for Okiku, Star Apprentice now?
Why am I half-expecting a review for Okiku, Star Apprentice now?
I usually don’t like to spoil anything too important, like giving away the game’s ending, for example, but I really don’t care if I end up spoiling the odd thing here or there either by accident or because it was just. More often than not, most of the people reading my reviews are either the developer(s) behind the game or anybody else that has already played the game and just wants to read something from a different perspective.
Thanks for all the advice. I think I'll just mention in the vaguest terms possible what I want to say so that I don't specifically spoil anything, just that "something happens, and here's how I feel about it," so that people who have played will know what I'm talking about.
Crystalgate
694
I don't spoil anything specific, but I will often tell about general occurrences a game has. For example, if your game features multiple scenes where the heroes defeat a villain and then are fed a tragic backstory about said villain, I will mention that.
My reviews tend to give a general idea of the story, usually stuff at the beginning of the game. Then I try to give an overall impression of what I think about the story. Is the story strong and does it make you want to play the game.
If there's something drastically wrong with the story you could probably mention it without actually describing what happened ie "What happened at the end of the game came from nowhere and didn't make sense."
Here you didn't spoil what happened, but gave an impression of what you thought about it. The developer will know what your talking about most likely.
Pages:
1
