Instead of adjusting the azimuth and retrying, I decided to take my chances and typed RUN to execute the one-line BASIC bootloader that starts the actual machine-code game.
To my surprise, the game started, but there was something odd. Even though I should have lost all my lives, the game kept going. Somehow the loading error had modified a few bytes in the game that were responsible for checking the game-over condition.
I finished the game several times without ever seeing the Game Over message. Well, the probability isn't as low as accidentally writing a game from scratch, but it's certainly interesting when you think about it.
Anyway, in Elite, you can save and restore your progress, so I did that because I felt like I'd accomplished something. However, after a week or so, I was getting pretty bored that I was just flying from place to place, trading, but not a lot else was happening. I had the occasional fight with another ship on my way to a new planet, but only maybe every 2nd or 3rd flight. It was basically a trading game and nothing much else.
I returned the game to my friend a couple of weeks later and told him how I found it pretty boring. He was surprised and said you get attacked almost every flight. We loaded it up on his CPC, and sure enough, I played for about an hour, and there was lots of combat. Borrowed the game from him again, and this time didn't load up my old save game, and had the same - lots of combat. Reluctantly, I started again, losing all my credits from trading, but suddenly the game was actually fun again.
My best guess is that some data that controlled how much combat action I got had been corrupted in a way that wasn't detected by the checksum, and once that was reloaded it got persisted in every subsequent save. It sounds implausible, but actually most checksum schemes on the CPC don't differentiate between runs of 00 bytes or runs of FF bytes, as they're usually done as mod-255. [0]
[0] checksum code is often a bit like this: IN: A byte that was written, HL previous CRC. ADD A,H: ADC A,0: LD H,A: ADD A,L: ADC A,0: LD L,A [1]
[1] Often called Fletcher-16, it's much simpler on an 8-bit CPU than the pseudo-code on Wikipedia suggests [2] if you pre-initialise the counters to 1 instead of 0
Rand and run and load and screens
Then five minutes fingers crossed
Hoping not to witness the terror
Of R: Tape Loading Error
(M.J. Hibbett & The Validators - Hey Hey 16k)
Unlike many other cheat devices, this meant that Game Genie modified ROM (game program) rather than RAM (game variables).
I would say, however, given the staggering space of possible ROMs, it's not particularly cheating to change from using the acceptance criteria to judge random ROMs, to using the acceptance criteria in the generation phase. It's fine to do things like generate random opcodes instead of purely random numbers for the first 1KB, for instance.
It's really just an optimization of what you're already doing; it's equivalent to randomly generating a lot of options then rejecting the ones that don't fit, except it goes much faster and produces a lot more output of interest instead of burning energy on things that are just going to be rejected anyhow.
If you want to increase your chances of finding something but still generating a "complete" rom, then limit the size to 2k.
https://www.youtube.com/watch?v=wlW84fEHngM
https://www.youtube.com/watch?v=O-WjF_dxdHM
I'd say gentlemen (m/f) start your random number generators
https://justine.lol/sectorlisp2/
Ok, Lisp and Forth can bootstrap themselves from a small core, but still...
If you do the math based on the specs given in the story (and crucially, you assume that each possible book appears once) you end up with a library several times larger than the observable universe.
Quite a while ago I did something similar [1] with a much simpler problem space: 32-byte DOS programs and rudimentary genetic programming.
While they will usually produce video on old CRTs, the video signal they generate is technically not valid. The VSync signal needs to be generated in software, and random programs are unlikely to do so correctly. Different TVs will behave differently (usually rolling on old TVs, blank on new TVs), and probably none would look like what the emulator is showing.
I tried running the game-like ROM in Stella and couldn't get it to work. It seems to depend on the startup state, which means it likely wouldn't run on an actual console.
[1] https://libraryofbabel.app/ disclaimer - my own project
Not exactly the same but reminds me of one time I did an experiment with rational number attempting to see which patterns emerged… 111? 112? 113? etc.
Also, instead of Z-Machine games, try writting Inform6 code, the games are highly modular and OOP oriented so creating something understandable can also be made without even an AI, just premade phrases with cliché settings.
I'm in awe.
It would be cool to start with a random ROM image and then use a Monte Carlo technique (simulated annealing), making a set of random changes to the image by flipping bits, use the change in the "composite score" for the decision step in the MC iteration, and have your image "evolve" into something.
Repeat until one finds a game that is new!
Should only take a few ages of the universe. :-)
Moosturm•1d ago