Jetpaca's fundamental gameplay elements

[akien-mga]

To be able to further Jetpaca efficiently, we need to put into words the existing gameplay elements so that we can discuss them, see what makes the game fun or not.

The current set of pre-open sourcing levels also shows that various things were tried ("demo", "alpha", "gcon", "test", and some more or less "final" levels). Some levels are skinned, while others are mostly a layout used to test the gameplay before spending too much time making it pretty (good practice btw :D).

@reduz @punto- If we could have your insights on this, it would be great. What was tested, and what were the conclusions? What made the game cool in your eyes, and what are the existing levels that show it well (and what levels should be considered as "bad gameplay" if any)?

[punto-]

I don't remember the levels in particular, but my favorite reference would
be Yoshi's Island. The idea was to have big levels that the players can
explore, some enemies, and puzzles. Usually one new puzzle element/mechanic
introduced in each level, to build up the complexity.

On 22 May 2016 at 11:31, Rémi Verschelde notifications@github.com wrote:

To be able to further Jetpaca efficiently, we need to put into words the
existing gameplay elements so that we can discuss them, see what makes the
game fun or not.

The current set of pre-open sourcing levels also shows that various things
were tried ("demo", "alpha", "gcon", "test", and some more or less "final"
levels). Some levels are skinned, while others are mostly a layout used to
test the gameplay before spending too much time making it pretty (good
practice btw :D).

@reduz https://github.com/reduz @punto- https://github.com/punto- If
we could have your insights on this, it would be great. What was tested,
and what were the conclusions? What made the game cool in your eyes, and
what are the existing levels that show it well (and what levels should be
considered as "bad gameplay" if any)?

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#10