1. icon for News
  2. icon for TCHOW

News

Tuesday, October 16, 2012

rktcr: Looking for a few good testers

Rktcr is a physics-based action-platformer-turned-puzzle-platformer; that is, it's an action game meant to be played thoughtfully at much slower than real-time. I'm currently in what I call the alpha stage of development.

The goal of the alpha is to shake down this basic gameplay and to find a good set of levels. Levels have some portals (entrances/exits) and some gems. Each level can be played in 16 orientations (8 gravity directions + mirroring). And it should be reasonably interesting (that is, one should be able to get between different pairs of portals, possibly collecting a gem) in at least a few of those orientations.

Here's where you come in

I'm looking for alpha testers to help (for a few hours each week):

  1. Find bugs (out-of-memory, crashes, sound glitches).
  2. Provide gameplay feedback. See how the controls and physics feel to you. Record your thoughts on easy and difficult elements of the game.
  3. Think about new levels. Can you do something with the rktcr that isn't exploited by a level yet?
  4. (Most importantly:) Make paths. Play through levels in orientations they have not yet been played, and contribute the resulting paths to a repository on github.

Knowing which paths are feasible is important for the second (and as-yet nonexistent) level of gameplay, wherein levels are assembled into worlds.

In compensation, you'll get a thanks in the game credits and a free copy of the game if it's ever finished.

Requirements/Applying

NOTE: Currently, I'm only testing on Windows and Linux, as I don't have a MacOS machine to run builds on.

If you are interested in becoming an alpha tester:

  • Make a github account; you'll need this to access the paths repository.
  • Make a skype account; screen sharing is useful for complaining about glitches and debugging crashes.
  • Make a google account; google docs is good for writing up your feedback, and google drive is good for distributing files.
  • Record your system information (cpu, graphics, os version). On windows, if you have steam: Steam > Help > System Information -- though I don't need/want/care about the "Installed Software" part of the info. On linux `uname -a`, `cat /proc/cpuinfo`, and `glxinfo`.

And, critically, have a conversation with me via e-mail, google chat, or in person about games, gameplay, what you like, and what you don't like (my contact info is on the about page). I'd like to make sure that my testers are able to think analytically about gameplay and mechanics.