~swashberry/orange

v1.3 5 years ago .tar.gz browse log

Version 1.3

At long last, version 1.3 is finally here!

1.3 is a small release that only adds a few things to the game.  First
of all, it adds dynamic screen resizing both from the command line and
from a configuration file.  Secondly, it adds working teleporters which
can be used to make more complex levels, potentially even with secret
areas.  And lastly, the game now has an actual ending rather than just a
drop to the command line.

The game has also been re-released under the Sunflower Seed License,
which is my own version of the Beerware License.  Have fun with that!

v1.002 7 years ago .tar.gz browse log

Minor changes to the inner workings of the game

This update comes with a few minor changes (hence the revision number
being updated to 2 rather than the release number) which make the game
more pleasant and less programmer-y.

These changes include re-implementing the in-game message system and
incorporating that into the plaintext level building system, so that
in-game messages now appear as text rather than as objects randomly
floating in the level.  This system also instructs the player on how to
reset the level if they die, so you don't need the command line to tell
you what to do.

A few new levels have been added in order to smooth the learning curve
and make the game easier for newbies to understand.

The display window has been resized to better fit 16x9 screens, so you
get a nice wide view of the game that's better for platforming.

There are a few smaller changes as well, but those will be further
refined and incorporated into future releases.  In short, Orange Guy's
Quest still lives!!

v1.1 7 years ago .tar.gz browse log

Version 1.1

The previous version of the code which was last updated in 2011 has been
retroactively named "Version 1.0" and these updates have been
collectively called "Version 1.1" for the purposes of this release.

Because this is the first release of the code in this repository, a
summary of changes would be meaningless, but ``doc/changes.txt'' will
provide information about the code updates for those of you who want to
know how laughably bad the code was when I was in college.

Don't read ``doc/bugs.txt'' because that will also reveal the
embarrassing mistakes I've made just recently :-p
Do not follow this link