Sure, and if I were designing it, I'd have the "name" of the console be arbitrary instead of the crux on which other things are based. So let's say you create a field that will simply be a display name for the console. Then you can have a separate field (maybe even hidden) that identifies to the software what console it is. It's a fine design, but not worth the trouble of customizing. I've had three errors that took hours to correct all related to customization settings. The less you customize the program, the better your experience will be. And that's sad, but it's a common thing among indy software. I don't regret buying premium. It's still worth it. Just... you know, would've been nice to have simpler systems that don't require you to seek out everywhere in the software that gets a reference from the display name of the console.