I got a code to review Shantae and the Pirate's Curse from Wayforward and I have beaten the game, but I don't know where to go with my review. Can anyone give me tips on how to come up with ideas in order to finish writing my review?
Before I try to give you any advice I have to:
a) point out that I'm only looking at this from a review hobbyist's perspective.
b) ask the following:
1. Is this a written review, a video review, or other?
2. What is this review for (a personal site, a large video game outlet, a college project, etc.)?
"I'll take a potato chip... AND EAT IT!"
Light Yagami, Death Note
"Ah, the Breakfast Club soundtrack! I can't wait 'til I'm old enough to feel ways about stuff!"
Phillip J. Fry, Futurama
So in other words you created this post to advertise you are writing a review for you blog. I have to give you points for that. In fact, I will let Zoidberg do it
RetiredPush Square Moderator and all around retro gamer.
I believe most reviews tend to start with some sort of broader comment about a scenario surrounding the game, and then work into the specifics.
So, if you were reviewing Star Fox Zero (for example), you could possibly start with a comment on the game's bumpy development and control controversies, then ask whether it had emerged successfully from these issues. Or you could mention the history of the series; perhaps reference some personal memories of playing Star Fox 64 - and then ask how the newest game has attempted to move the series forward. Or you could talk about the game in the context of the Wii U's game library as a whole; about how the game was developed as a demonstration of the Gamepad's possibilities, and could then ask whether it had succeeded in this goal.
So there are a number of ways of tackling a single game, but they all have a similar introduction: paint a broader scenario, describe how the game in question fits into it, and then ask whether the game achieves what it set out to, and go from there.
The rest of the review can be phrased around answering that motivating question, while also addressing each of the key elements that make a game what it is: controls, level design, music, characters, visuals, story, difficulty curve, etc. You would expect any review to comment on these features, but having a broader question should allow you to answer them with more context than simply writing, "it looks good, it plays well, the characters are a bit boring, but the story is good etc.". It should lend the review a bit of narrative which will make the whole thing feel more connected and (hopefully) keep the reader glued to the page. You can then finish with summary, taking all the above points into account, and hoping to answer the original question; does it achieve what it set out to?
Most readers will have questions of their own when they click on your review, which could range from simply "what sort of a game is it?" (from complete newbies) to "how does it compare to previous titles, and what new features have been added?" (from fans of the series).
A review is meant to inform people, but people will likely have already thought about the game themselves, and come up with a series of questions they want answered. Your job as reviewer is to provide these answers, ideally in an engaging, coherent and well structured piece of writing. So think about what people are probably asking about the game, make a mental (or real) list of these question, and do you best to cross these questions off throughout the review. And also, don't be afraid to providing your own thoughts and observations on the game that you've found through your playthrough. After all, you've played it and the readership likely hasn't.
Anyway, that's what I reckon.
EDIT: And don't be afraid to rewrite it. As many times as necessary.
I think I got an idea. I could talk about how most video game companies have mascots that primarily originate from platformers that, for the most part, are a hit to gamers. I then could list some companies and their mascot and lead in to saying how Wayforward's mascot is Shantae and how she is not one to break away from the trend that these companies created, implying that she is a popular star of a good platformer. Is that good?
@UltimateGamer132 Just a few general tips:
1. Try to take into account the game's newcomer-friendliness when you write the review. Perhaps dedicate a paragraph to the subject, but no more than that.
2. Gameplay and Story should get more attention than graphics and sound, even in games with notoriously good and bad visuals and/or horrendous sound design.
3. Always be specific. For instance, instead of stating "The bosses look pretty cool, but aren't very fun to fight." you should say "The bosses are visually impressive, but are insultingly easy.".
"I'll take a potato chip... AND EAT IT!"
Light Yagami, Death Note
"Ah, the Breakfast Club soundtrack! I can't wait 'til I'm old enough to feel ways about stuff!"
Phillip J. Fry, Futurama
@Ultimategamer132 Yeah, that sounds like it could be good. It's certainly true that we owe a lot of our modern mascots to the humble platformer, even if the characters have branched out into new genres.
Anyway, write something down and re-read it. It it looks good, go with it and move onto the next bit. If you've got problems, tinker around until your happy, then move on. Then re-read the whole thing, and repeat. About each part, ask: "Is it interesting in its own right? Does it answer people's questions? Does it flow well with the rest of the review?". If you're ticking the majority of those boxes for every section, you should be good.
@Ultimategamer132 How did you come by a code, given out for review purposes, if you have no review experience? Way Forward just giving the game away to anyone who says they'll review it?
You guys had me at blood and semen.
What better way to celebrate than firing something out of the pipe?
I sent an email to Wayforward requesting a code to review Shantae and the Pirate's Curse on PS4. Also, I do have review experience; I just got stuck on coming up with an opening for this review.
I've approached about 20-25 other devs. I tend to usually be successful in gaining a code to review a game when they are indi devs. I have contacted Nintendo and Capcom and almost received a code...ALMOST! They ran out of codes at the point they decided to reply to my request. Companies like Atlus and Aksys Games basically said no. So I've had an interesting experience, so to say the least.
I have to admit, when I make a product I don't think I would give out review copies. It just doesn't seem worth it to me. If you make a good enough game people will talk about it and review sites will want a review on their site.
People keep saying the Xbox One doesn't have Backwards Compatibility.
I don't think they know what Backwards Compatibility means...
@Tasuki I think that's quite unfair, he hasn't actually put a link to his blog anywhere, so there is no evidence of advertising the game at all. He's simply interested in reviewing, and wants some tips from people who have had more practice.
Forums
Topic: Helpful tips for writing?
Posts 1 to 18 of 18
This topic has been archived, no further posts can be added.