#single vs multi script architecture

1 messages · Page 1 of 1 (latest)

worldly schooner
#

when i look at free game kits there's always multiple scripts for one system, whats the point?

fallen flume
solar sleet
#

A single script architecture means the client and server utilizes one single script to handle all game logic. They typically (always) use modules. This is good for almost any project you make and allows for easy loading systems to be made out of them.
Multiple scripts are also good and is an easy way to create systems pretty fast. Though one problem does arise and it's multi-script communication but there are many ways to fix that issue. It's all about what you're most comfortable with tbh

#

I prefer a single script architecture just because it's ease of use and allows me to execute scripts in a specific order I want

sour aurora
twin folio
#

isn't multi script better?

#

it's more modular.

sour aurora
# twin folio it's more modular.

Using both systems can be modular, it’s really just up to preference. Of course a module script can always act like a server script, you can just control when it runs

worldly schooner
sour aurora
#

?

twin folio
sour aurora
#

i think you dont know what single script arch is

twin folio
#

Oh

#

Lol

#

H

sour aurora
#

Its misleading

solar sleet
#

I have a module that loads my Handlers and Controllers within the subfolders under the Handlers folder

#

The one client script handles all logic for most client behavior (ui, movement, etc.)

#

While a multi-script architecture will most likely ditch the modules and use scripts for each system which is fine

worldly schooner
solar sleet
#

For me it allows to load modules in a certain order

#

So systems with higher priority to load first can load first

#

Thats about it rlly

worldly schooner
#

thanks for your help @solar sleet now i know why to use it