This is the hackers' guide to SST2K. Read it before messing with the code.
It consists of an introduction, a history, suggestions for regression testing,
-some notes on the Python translation. For a to-do list, see TODO in the
+and some notes on the Python translation. For a to-do list, see TODO in the
top-level directory.
INTRODUCTION:
This is one place where OPTION_PLAIN does not restore the original
behavior, which was equiprobable damage across all devices. If we
wanted that, we'd return randrange(NDEVICES) and have done with it.
-Also, in the original game, DNAVYS and DCOMPTR were the same device.
+Also, in the original game, DNAVSYS and DCOMPTR were the same device.
Instead, we use a table of weights similar to the one from BSD Trek.
BSD doesn't have the shuttle, shield controller, death ray, or probes.
included in the distribution, 'replay', automatically reruns the
last game you played.
-Here are some interesting seeds for debugging and regression testing
-For each one, I list the seed, the options, and the last svn revision
-for which it is known to have given the described behavior.
+See the "test" directory for regression-test logs and checkfiles.
-1160647745 regular short good fancy (r769)
-
-Starts you in a quadrant with the Super-Commander in it. Slamming three
-torps at him will kill him. You can use this to regression-test both
-torpedo tracks and the Deep Space Probe. Known bug: "probe aut 2 8"
-triggers manual navigation.
-
-1160707235 regular short good fancy (r769)
-
-Do sr/mov aut 5 4/sr/sensors/orbit/transport; you'll get a transporter
-failure.
NOTES ON THE PYTHON TRANSLATION:
projects / super-star-trek.git / blobdiff