I remember a lot of things about the summer of 1991 (like sneaking into the theater to watch Don't Tell Mom the Babysitter's Dead because my parents absolutely did not approve of movies that so clearly showed teenage disrespect for authority), but the thing I remember most about that summer is spending countless sun-dappled afternoon hours staring at a rotoscoped little dude on my computer screen as he died a million deaths. Sometimes he'd fall. Sometimes he'd be impaled by spikes. Sometimes he'd be chomped in half by giant steel jaws. And sometimes he'd collapse into a bleeding pile after crossing swords with pixellated bad guys.
It was, for me, the summer of Prince of Persia—and I was completely entranced.
Created by Jordan Mechner a couple of years earlier in 1989 for the Apple II, the MS-DOS port of PoP came thundering onto shelves near the end of 1990, just as the Apple II platform was gasping its last breath as a viable gaming platform. Mechner had quite famously spent literally years working on the game's animations, tracing them from videotaped recordings of his brother (also of Errol Flynn, interestingly enough), but I didn't learn about any of that until some time later. All I knew was that from the moment that game came into my life—likely purchased from our friendly neighborhood Babbage's—I was hooked.
In ancient Persia…
Mechner's game had a long road from development to the screen, but what I learned from our interview with the man is just how much the Apple II's memory limitations shaped the game's final form—even though none of those limitations applied to the platform on which I (and the majority of players, going by sales numbers) first experienced PoP.
The biggest impact was that up until the tail end of development, PoP was going to be a largely solitary experience, with a non-violent character platforming his way through a series of dungeons to rescue the princess. The available RAM was simply too sparse to include any additional characters with their own animations and sound effects that would eat precious bytes. But one afternoon, after repeated prodding by another developer with whom Mechner was sharing office space, Mechner took advantage of some 6502 assembly instructions and coded up a bit-shifted bad guy that used the protagonist's animations and sounds—and suddenly the game had a real antagonist.
It was the kick needed to transform an interesting but not terribly exciting platformer prototype into a focused gaming experience, and it led Mechner to pull out all the stops and pull togethRead More – Source