1 Variations on Rockdodger
3 vor is a quick action game where you drive a space ship and try to avoid
4 crashing into rocks. Current information about vor can be found on the
5 homepage: http://herkamire.com/jason/vor
7 See INSTALL for instructions on building, running and installing.
9 Jason Woofenden and Josh Grams like rockdodger
10 (http://spacerocks.sourceforge.net/) very much: both playing it and hacking on
11 it. VoR is the result. It is currently based on the rockdodger 0.4.2 codebase,
12 with quite a few modifications, both user-visible changes and internal
13 technical improvements.
15 Available for download from http://qualdan.com/vor/, or you can check out the
16 latest SVN copy from http://josh.qualdan.com:3/svn/vor/trunk/ (Warning: Not
19 Note: This is a fairly hard game, intended to be a quickie game for when you
20 want to kill a few spare minutes. For reference, my best time [Josh Grams] is
21 about 3 minutes. I'm not generally very good at video games, but I have been
22 playing this one for quite a while now. However, you can make it substantially
23 easier by slowing the game down. New in version 0.2, we have a constant
24 GAMESPEED in config.h. New players may like to try it at 3/4 or even 2/3 speed.
25 It should probably be a command-line option, but I'm too lazy to fix that right
28 Changes from Rock Dodgers
32 * Moves like a real spacecraft; no more friction!
33 * No more silly shields or lasers; just pure rockdodgin' fun!
34 * Up/down scrolling; gives you more escape options.
35 * Proper time display for score, not just raw milliseconds (bleh).
36 * Ship explodes, blowing rocks away, rather than automagically vanishing
38 * New graphics, generated by POV-Ray. Yeah, okay, the ship is really cheezy.
39 At least the rocks are cool.
40 * Real collision detection; no more "ship is 1 pixel bigger all around
43 Internal Technical Changes:
45 * Upgraded to SFont 2.03, which has way less cruft, but no text input
47 * Started factoring a lot of stuff out of main into their own .c files.
48 * Removed a bunch of unused code.
49 * Function definitions: name at beginning of line (line following the return
50 type) for easy grepping as per GNU coding standards.
51 * Real collision detection (bbox/bitmask).