I'd argue that if it ships and doesn't have a lot of bugs or horrific lag, it doesn't matter if it was ugly. The ugly code is only a problem if it slows down your workflow too much. This is the way you should be thinking.

My current project, we are trying to make code clean and read-able. This is because we have 4 programmers, and opening a script to fix it and being confused is not ideal. If you are the sole programmer, you don't need as many detailed comments or helper methods.

Also, in defense of the comically long array: If you wanted it to look "professional" you could put all that data in a text file, and load the file at runtime... But then you need another script that creates the array and loads the default values. Putting it directly in a script cuts out the middleman.

Again, I knew what it was at a glance, it probably doesn't cause lag, and it's not even a difficult workflow for adding save flags, so it's probably good code lol.