Actually, since (as is typical in this family of software) I'm writing a different kind of data at each step, it's not as difficult as you might think.

Here's a little pseudo-code to illustrate:

initialise_stuff;
set_abilities;
set_race;
set_class;
set_skills;
[download]

That's the way (roughly) that it looks now. In my bad old BASIC days, I'd simply have had a GOTO triggered on the return value of each procedure to send the program back a chunk if the user asked to go back. Since you're given the chance to review any decision you make at the time you make it, this should allow procedures called to offer up the previously made choice for revision (and if it doesn't, I'll re-write the procedure so that it does) - I just need a clean way to drop back a stage on the appropriate return value.

Tiefling