> The correct way that this should be handled is for the voice cartridge to add its own > child slot, which more accurately reflects how the hardware worked: > > -cart voice -voice:cart kcmunchkin
That's ugly, and more typing. The actual user-and-documentation-friendly way would be for it to reset "cart1" each time there's a device that adds another slot. This reinforces that it's the same kind of cart slot each time.