Format and typo fix 2011/toledo/README.md
This commit is contained in:
Cody Boone Ferguson committed
1 parent
42ef81fece
commit
2f6c0589d6
1 file changed
+64
-65
+64
-65
@@ -17,7 +17,8 @@ make
|
||||
./toledo
|
||||
```
|
||||
|
||||
NOTE: This requires X11 to run or modifications to use layer.c on Windows.
|
||||
NOTE: This requires X11 to run or modifications to use [layer.c](layer.c) on
|
||||
Windows (see below).
|
||||
|
||||
## Try:
|
||||
|
||||
@@ -28,7 +29,7 @@ echo "Do or do not. There is no try."
|
||||
## Judges' remarks:
|
||||
|
||||
This two player game uses X11. The control keys can be configured by
|
||||
modifying the A,B,C and D macros at compilation.
|
||||
modifying the `A`, `B`, `C` and `D` macros at compilation.
|
||||
|
||||
After a quick splash screen the objective should be clear. There
|
||||
are Red, Green and Cyan tanks. A larger window can be made by altering
|
||||
@@ -45,6 +46,7 @@ you ought to be able to compile and run this program on Windows.
|
||||
|
||||
## Author's remarks:
|
||||
|
||||
```
|
||||
/=========\
|
||||
\==\ /==/ ||
|
||||
|| || /====\ |\/=\ || //==\ ==\ |=\
|
||||
@@ -52,6 +54,7 @@ you ought to be able to compile and run this program on Windows.
|
||||
|| || //===| || || ||=// \\=\\ ==/ |=/
|
||||
|| || || || || || || \\ || User's
|
||||
\===/ \\==// || || || \\ \==// Manual
|
||||
```
|
||||
|
||||
This is a color X11 3D tank-game for two players, just compile
|
||||
and run it without arguments.
|
||||
@@ -73,7 +76,7 @@ extra points.
|
||||
When only one tank remains on the field, the level will advance.
|
||||
Don't forget to destroy the aqua tank.
|
||||
|
||||
The playground is surrounded by mountains and each level is
|
||||
The <strike>battle</strike>playground is surrounded by mountains and each level is
|
||||
filled with random obstacles (pyramids and cubes).
|
||||
|
||||
The bars show players energy and score, each bar shows energy
|
||||
@@ -98,8 +101,8 @@ Keys for player 2:
|
||||
|
||||
> Note: Numeric keys don't work.
|
||||
|
||||
If you don't like the keys assignment, you can change it on the
|
||||
the makefile.
|
||||
If you don't like the keys assignment, you can change it in the
|
||||
Makefile.
|
||||
|
||||
### PARENTAL ADVISORY WARNING:
|
||||
|
||||
@@ -110,7 +113,7 @@ Not really, just kidding :D
|
||||
|
||||
### PLATFORMS TESTED:
|
||||
|
||||
* openSuSE 10.2 x86-32, X11R6 1024x768 32-bits color.
|
||||
* openSUSE 10.2 x86-32, X11R6 1024x768 32-bits color.
|
||||
* Fedora Core 8 x86-64, X11R6 1280x1024 32-bits color.
|
||||
* Fedora Core 11 x86-64, X11R6 1024x768 32-bits color.
|
||||
* Fedora Core 14 x86-64, X11R6 1024x768 32-bits color.
|
||||
@@ -119,11 +122,11 @@ Not really, just kidding :D
|
||||
|
||||
* Multiplayer out of the box.
|
||||
* Totally self-contained, no external files.
|
||||
* Fast-furious action at 29.97 frames per second.
|
||||
* Fast-and-furious action at 29.97 frames per second.
|
||||
* Just as the movies, 16:9 aspect-ratio.
|
||||
* Beautiful mountains landscape plus horizon line :)
|
||||
* Tanks and bullets exploding as wires with weird physics.
|
||||
* Tanks backoff when firing.
|
||||
* Tanks back off when firing.
|
||||
* There is an infinite number of levels.
|
||||
* Always different levels.
|
||||
* Animated intro.
|
||||
@@ -131,27 +134,24 @@ Not really, just kidding :D
|
||||
|
||||
### FEATURES THAT PROGRAMMERS WILL FIND APPEALING:
|
||||
|
||||
* Works both with x86-32 and x86-64 processors.
|
||||
* Works both with 32 and 64-bit CPUs.
|
||||
* Double buffered, portable to any X11 with 24/32-bit color.
|
||||
* Memory-hungry as must be any 3-D program, uses a 256 MB
|
||||
array.
|
||||
* Total and absolute irreverent coding style, so it generates
|
||||
a lot of warnings when compiled.
|
||||
* It can take several minutes to compile (known culprits:
|
||||
Fedora Core 11-14 on x86-64 512 MB)
|
||||
* It is written in the only true C: K&R, and no, it not means
|
||||
* Memory-hungry as must be any 3D program; uses a 256 MB array.
|
||||
* Total and absolute irreverent coding style, so it generates a lot of warnings
|
||||
when compiled.
|
||||
* It can take several minutes to compile (known culprits: Fedora Core 11-14 on
|
||||
x86-64 512 MB).
|
||||
* It is written in the only true C: K&R, and no, that doesn't mean
|
||||
Katherine & Rose.
|
||||
* Vectorial scalable graphics, do you want a bigger
|
||||
playfield? change variables M & N.
|
||||
* Half of the program is formatted as 3-D cube, view with
|
||||
Tabs at 8 columns and a square font.
|
||||
* The other half of the program is unprintable source code,
|
||||
so no typing from paper, you have to write a converter of
|
||||
tabs and formfeeds to its C escaped forms.
|
||||
* No text, so this program can be used and understood easily
|
||||
on any country.
|
||||
* This program is highly ecologic, it sleeps when it is not
|
||||
doing anything.
|
||||
* Vectorial scalable graphics, do you want a bigger viewport? Change variables M
|
||||
`&` `N`.
|
||||
* Half of the program is formatted as 3D cube. View with tabs at 8 columns and a
|
||||
square font.
|
||||
* The other half of the program is unprintable source code, so no typing from
|
||||
paper, you have to write a converter of tabs and form-feeds to its C escaped
|
||||
forms.
|
||||
* No text, so this program can be used and understood easily in any country.
|
||||
* This program is highly ecological, it sleeps when it is not doing anything.
|
||||
* Virtual world with its own physics laws.
|
||||
* When closing the window it will show an X11 error :P
|
||||
|
||||
@@ -160,9 +160,10 @@ Not really, just kidding :D
|
||||
* Loop code included inside loop test.
|
||||
* Function arguments used as variables.
|
||||
* Operators used freely.
|
||||
* Precalculated values to save bytes.
|
||||
* Uses the +++, +- and *+ undocumented C operators :P
|
||||
* Pre-calculated values to save bytes.
|
||||
* Uses the `+++`, `+-` and `*+` undocumented C operators :P
|
||||
|
||||
```
|
||||
|
||||
....,,,,---++++++--,,..
|
||||
.,,,....... .$@@@@@@@@@@@@$$@@@@@@@@@@@@@@#+
|
||||
@@ -185,53 +186,51 @@ Not really, just kidding :D
|
||||
..,+++=+-,.. .@. +=+
|
||||
.,-+++++,@@==
|
||||
|
||||
```
|
||||
|
||||
### THE HISTORY OF THIS PROGRAM:
|
||||
|
||||
When I started working on this program, I figured that it would
|
||||
be easy to fit on the character limit, but I missed three
|
||||
things, the enormous X11 names, the unportable keycodes and my
|
||||
2 KB of artwork.
|
||||
be easy to fit on the character limit, but I missed three things: the enormous
|
||||
X11 names, the non-portable key codes and my 2 KB of artwork.
|
||||
|
||||
Very hard coding did the first thing, in fact I worked out
|
||||
twenty-nine different versions, at one step I had four
|
||||
parallel versions with different characteristics removed
|
||||
(mountains, horizon line, score/status bars and explosions),
|
||||
I've managed to fit it all together!.
|
||||
Very hard coding did the first thing. In fact I worked out twenty-nine different
|
||||
versions and at one step I had four parallel versions with different
|
||||
characteristics removed (mountains, horizon lines, score/status bars and
|
||||
explosions) but I've managed to fit it all together!
|
||||
|
||||
The second thing was solved using the makefile, it is under
|
||||
160 bytes and you get adjustable keyboard. The greatest
|
||||
mistery on the earth is why X11 handles unportable keycodes to
|
||||
The second thing was solved using the Makefile: it is under
|
||||
160 bytes and you get adjustable controls. The greatest
|
||||
mystery on the Earth is why X11 gives non-portable key codes to
|
||||
the user.
|
||||
|
||||
And finally, the third "Thing" was growing and growing, and
|
||||
growing, eating bytes for lunch... after endless rounds of
|
||||
crunching I obtained three-hundred seventy-eight bytes of
|
||||
artwork and guess what?, it doesn't fitted.
|
||||
And finally, the third "Thing" was growing and growing, and
|
||||
growing, eating bytes for lunch... after endless rounds of
|
||||
crunching I obtained three-hundred seventy-eight bytes of
|
||||
artwork and guess what? It doesn't fit.
|
||||
|
||||
So I had to integrate a decompressor, based on the space,
|
||||
tabulators and other non-counted characters.
|
||||
So I had to integrate a decompressor based on the space, tabulators and other
|
||||
non-counted characters.
|
||||
|
||||
The final program is composed of eight microfunctions, one is
|
||||
the core and does most of the hard work, other functions help
|
||||
doing the X11 things, explosion effects, 3-D calculations and
|
||||
viewing.
|
||||
The final program is composed of eight micro-functions: one is the core and does
|
||||
most of the hard work and the other functions help do the X11 things, explosion
|
||||
effects, 3D calculations and viewing.
|
||||
|
||||
* K() - 3-D transformation
|
||||
* s() - Rendering
|
||||
* b() - Line color selection
|
||||
* G() - Explosion animation
|
||||
* g() - Moves 3-D object backward and forward
|
||||
* F() - Collision detection
|
||||
* T() - Core (also known as main loop :D)
|
||||
* main() - Initialization and uncruncher, what a common name!,
|
||||
C programs should start in the cool() function :).
|
||||
* `K()` - 3D transformation
|
||||
* `s()` - Rendering
|
||||
* `b()` - Line color selection
|
||||
* `G()` - Explosion animation
|
||||
* `g()` - Moves 3D object backward and forward
|
||||
* `F()` - Collision detection
|
||||
* `T()` - Core (also known as main loop :D)
|
||||
* `main()` - Initialization and 'uncruncher', what a common name!;
|
||||
C programs should start in the cool() function :).
|
||||
|
||||
The source code was formatted as an cube using a specially
|
||||
written program, the reality is that the program is smaller and
|
||||
obfuscated of what is needed so the reformatting doesn't
|
||||
exceeded the character limits, the crunched vectors were
|
||||
generated by another special program and the tank that
|
||||
surrounds this text was generated by yet another program.
|
||||
The source code was formatted as a cube using a specially written program. This
|
||||
program is smaller and obfuscated what is needed so the reformatting doesn't
|
||||
exceeded the character limits. The crunched vectors were generated by another
|
||||
special program and the tank that surrounds this text was generated by yet
|
||||
another program.
|
||||
|
||||
*Have fun!*
|
||||
|
||||
|
||||
Reference in new issue
Block a user