5/5 Babar Javed K. 2 years ago on Google
300
words
for
a
review
is
just
too
high
and
mentioning
that
they
find
it
hard
to
find
300
words
to
write
about.
Thus,
this
article,
giving
advice
on
how
to
write
300
words
(or
more).
Note
that
you
need
to
actually
be
prepared
to
put
at
least
a
minimal
bit
of
effort
in
before
you
can
reap
the
rewards
of
this
tutorial.
Also,
you
need
to
have
played
the
game
you're
reviewing.
;p
Step
1
-
Categories
Sectioning
off
your
thoughts
on
a
game
into
different
categories
is
the
most
used
'trick'
to
writing
a
review
and
a
very
good
way
to
start
off.
The
headings
used
can
vary
but
often
they
consist
of
a
general
break-down
of
the
aspects
of
a
game.
Below
are
listed
the
most
used
examples
of
Section
Headers.
-Ā PlotĀ -
Details
information
about
the
story,
writing
and
characterisation
-Ā GameplayĀ -
Details
information
about
balance,
bugs,
ease
of
use,
battles
and
minigames/extra
content
-Ā GraphicsĀ -
Details
information
about
the
presentation,
design,
graphical
components
and
consistency
-Ā SoundĀ -
Details
information
about
music
and
sound
effect
use
and
the
fittingness
of
-Ā SummaryĀ -
Often
a
general
summary
of
the
above
Sections,
doling
out
of
points
and
last
minute
thoughts
Sometimes
these
will
be
broken
down
into
further
categories,
such
as:
Writing
>
Plot/Characters/Dialogue
Graphics
>
Mapping/Graphical
Components/GUI
Gameplay
>
Optional
Content/Battles/Systems/Other/Bugs
Sound
>
Sound
Effects/Music/Atmosphere
It
is
highly
recommended
that
you
should
touch
base
on
each
of
the
main
components
at
least
once
during
a
review.
Often,
breaking
things
into
parts
can
help
a
lot
with
focussing
on
just
that
part,
usually
leading
to
more
thought
about
what
to
write
about
said
category
and
ending
up
with
more
writing.
However,
if
you
are
still
reaching
for
that
elusive
300
word
limit
after
breaking
down
your
thoughts
on
the
game
into
the
above
categories,
the
next
step
will
be
of
aid
to
you!
Step
2
-
Question
Everything!
Oft-times
people
will
put
a
line
or
two
that
they
liked
something
or
thought
something
else
was
bad,
but
not
actually
give
anything
else
beyond
that.
This
is
silly
as
it
doesn't
give
the
readers
a
reference
as
to
what
the
reviewer
experiences
and
why
such
a
thing
was
considered
as
great
or
not.
The
best
way
to
expand
your
writing
is
to
ask
yourself
a
list
of
questions
on
each
of
the
above
categories.
These
questions
should
often
be
based
on
the
following
-
What,
Was,
Were,
Why
and
How.
Using
these
three
question
starters
should
help
a
lot
in
filling
up
those
300
words!
Here
are
some
basic
questions
you
can
ask
when
filling
in
the
above
categories:
Plot/Writing
What
did
you
like/dislike
about
the
writing/characters/plot?
Were
there
any
points
that
could
have
been
improved
on?
Was
there
anything
that
confused
you
and
if
so,
what?
Did
you
enjoy
the
overall
story
and
if
so,
why/why
not?
Graphics
Were
there
any
graphical
issues
that
you
noticed?
Did
you
like
or
dislike
the
graphics
and
if
so,
which
and
why?
Was
mapping
well
done
and
were
there
any
particular
maps
that
stood
out
to
you
as
really
good
or
really
bad?
Did
the
graphical
components
work
well
together
or
were
there
inconsistencies?
If
so,
where?
Were
menus
and
GUIs
designed
well
and
easy
to
read?
Music
Was
music
well
implemented?
Were
there
any
jarring
sounds/songs
that
stood
out?
Were
there
any
musical
areas
that
stood
out
as
particularly
good?
Did
you
notice
the
sound
in
general
or
was
it
just
there?
Did
it
enhance
your
experience
at
all?
2 people found this review helpful š