whats better, an "All in One" script or separate?
im doing a game that have Race based morph, each race will have different skills and clothes that i set depending on race, datastore, Stats thing, spec thing depending on the Player.Name etc, so my question is, its better to i make all this in 1 big script, using something to separate it like coroutine or its better i separate all these things in 1 script each one? thinking in performance etc
0
3 answers
The answer is both. I would take a look at single-script architecture, as it definitely makes organizing your game much easier then the alternative multi-script architecture. That said, you still shouldn't be stuffing all your code into 1 single script. You should be using module scripts to modularize your code and break it up into functional pieces which can be ran separately, but used together. The last thing you want is to be scrolling through a script with 6000+ lines of code to find the function you want to change.
0
1
I'd think its better to seperate them so that scripts are more organized, like you have 600 lines of code in one script and for around each 60 lines (can be different, not the same) is a seperate task, so there will be 10 scripts for each task. (Extra: You can use bindable functions if you want the scripts to work in a order.)
0
0
For me, it depends on how complicated the thing you're trying to is. For example, if it's something like selecting a button and moving it, I'd make it one script as it's not that complicated. But for something like player morphs and data, I'd split it into 2 functions in a module script, then call it from the normal script as it's complicated enough where it would make some delicious code spaghetti.
0