The thing is, no matter how many customization options there are, every option has to have a value linked to it in some way so that it can be graphically rendered. Otherwise, there’s be no way for the engine to keep track of what you chose. There has to be something stored when an option is chosen. What I wrote was simplistic, yes, but I did it as an example to show what I was asking. I understand that there are a hell of a lot more customization options, but whether there’s 10 options or a billion, they all have to store something when chosen, right? So why couldn’t the engine create a description based on whatever options the person had applied? We’re using a computer here, and computers only look at values to apply and render things. For every option there’s a value, and if those values are pulled, a description should be able to be formulated.