You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For a long time, SPADS used SWIG to interface with the engine's unitsync library. Due to this, it was necessary to generate wrappers (binaries) specific to the system it was installed on. Initially the SPADS installer was just a script designed to simplify and automate this process in addition to helping initialize SPADS configuration files via an interactive prompt (minimal mandatory customization). The goal was for users to be able to run SPADS directly on official lobby server without having to edit any configuration file.
Nowadays, FFI is used to call the unitsync library, so there is no need to generate any system specific binary anymore. However, more and more functionalities have been added to this installer to increase automation (automatic installation and management of engines, games, maps, plugins...), and make it easier for users to use their own custom unattended installations templates (for containerized installations for example), without having to duplicate default SPADS configuration files.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Question from BAR discord:
For a long time, SPADS used SWIG to interface with the engine's unitsync library. Due to this, it was necessary to generate wrappers (binaries) specific to the system it was installed on. Initially the SPADS installer was just a script designed to simplify and automate this process in addition to helping initialize SPADS configuration files via an interactive prompt (minimal mandatory customization). The goal was for users to be able to run SPADS directly on official lobby server without having to edit any configuration file.
Nowadays, FFI is used to call the unitsync library, so there is no need to generate any system specific binary anymore. However, more and more functionalities have been added to this installer to increase automation (automatic installation and management of engines, games, maps, plugins...), and make it easier for users to use their own custom unattended installations templates (for containerized installations for example), without having to duplicate default SPADS configuration files.
Beta Was this translation helpful? Give feedback.
All reactions