What's the point of a modular framework for GUIs?

I’m working on a single-script-architecture game, and I am now just starting to work on GUIs, but like it’s hard to implement an organized modular framework system for GUIs. So, what’s the point of it, if it’s not as clean as just using LocalScripts?

So, I wanna know what’s the point of them and how should I organize GUI?

1 Like

It’s important to understand why we have module scripts to begin with. Module scripts are a way to share code across scripts so that they can be used in multiple places of your game. In the case of GUI’s, it’s useful to use them to share code pertaining to GUIs. You might have a module for creating buttons, or checkboxes, or other UI components that you would use in multiple places in your game’s UI.

1 Like

I see, I understand like making modules to handle like buttons more efficiently rather than having the same local script and every single button. But, what about for handling UI that has it’s own functionality? My game doesn’t use components for UIs, everything is it’s own thing. So my question is, how would I be able to make a modular GUI framework for things like that? Cause, it’s seems messy and I need help navigating it. I appreciate your response though.

1 Like