The current iteration of the MainMenuUI is a mix of different methods for activating and deactivating UI. I have learned over the weeks that turning it on and off by setting the main GameObject active through 'object.isActive(bool)'. However, some of the 'old' UI (Quit Menu, Options Menu, etc.) are relying on enabling and disabling the Canvas component. While everything 'technically' works, it's possible to have all of the gameobjects disabled (thus making it so that all the ugly menus don't stack on one another) and can still be enabled through the scripts (which cannot be done if enabling and disabling the canvas).
Suffice to say, update the activations by relying on the GameObject rather than anything else.
The current iteration of the MainMenuUI is a mix of different methods for activating and deactivating UI. I have learned over the weeks that turning it on and off by setting the main GameObject active through 'object.isActive(bool)'. However, some of the 'old' UI (Quit Menu, Options Menu, etc.) are relying on enabling and disabling the Canvas component. While everything 'technically' works, it's possible to have all of the gameobjects disabled (thus making it so that all the ugly menus don't stack on one another) and can still be enabled through the scripts (which cannot be done if enabling and disabling the canvas).
Suffice to say, update the activations by relying on the GameObject rather than anything else.