Version -- This is version .5 of mcRipper. mcRipper now handles custom properties, including property sets, substacks, background fields with different text on different cards, and nested groups.

History -- See the Change Log.

What it Does -- mcRipper rips and burns MetaCard stacks.

What is "Ripping a MetaCard stack?" -- mcRipper goes through the stack and notes all the objects contained in the stack, and most of their properties. It records all this information in XML format, where it can be modified easily, either in a text editor or in any of numerous specialty XML editors.

What is "Burning a MetaCard stack?" -- mcRipper can take the XML it outputs and use it to recreate the stack from scratch, creating the stack, the backgrounds, the cards, and the objects.

Warning -- mcRipper is very light on testing so far. Please use only on copies of stacks. mcRipper hasn't done anything harmful to any of my test stacks, but I don't want you to be the first casualty.

What good is it? -- Well, it could be used as a format-independant way of storing a MetaCard stack. It could be used as a way of leaving behind corruption, if MetaCard stacks ever became corrupted (they don't). It could be used to create many related but slightly different stacks. It could be used to make many similar changes to a MetaCard stack using a text editor. It could be used as a way to edit MetaCard stacks without their scripts running. It can be used to allow editing MetaCard stacks in any of the numerous XML editors available. It was inspired by SuperEdit, which edits SuperCard files without running any scripts.

Does it also work on Revolution stacks? -- Revolution is a development environment based on the same engine as MetaCard but which has a different development environment. mcRipper has been tried on a few Revolution stacks, and seems to work.

How do I use it? -- See the How To Use It guide.

What are the bugs and limitations? -- See the Bugs/To-Do list.

What is the format of the text file? -- XML; see Text Format description.

What does the output look like? -- See the output Example.