Poll: best way to create an Auto Update System

Help and Feedback Scripting Support
#1

so I`m trying to make an auto-updater for a system I have.
and I want to add an update system
in the pole, you can enter what you think is best. and below the poll is an explanation
I don’t know what would be best programming-wise, ease of use, and performance

2 examples of the lights

DmxF: Channelwatcher - Roblox
DmxS: Universal RGB Script - Roblox

the system is meant to be used by me, my group and other players.

Auto Updater
  • 2 library inputs
  • create a plugin
  • wrap the light in a module script
  • software as main

0 voters

so I am making a modular lighting system.
the idea is to have 1 main script that controls all the lights.
and every light has its own software.
I want to update the software of the lights.

so far I have come up with these options.

2 library inputs

in this variant, I first save the light itself to Roblox.
then I save the module script to Roblox
I can call require on the script to update the Fixture
pro:

  • Really easy to install new lights
  • auto-updates every time a server is started

cons:

  • need to maintain 2 inputs
  • need a system to keep track of what software matches what light
  • mismatch between light and software possible
  • clutter in the toolbox when searching for lights
create a plugin

in this version, you only save the light once to Roblox.
using InsertService you can get the fixture and search for the software.
then replace the software from the lights
pro:

  • only 1 variant in the toolbox
  • it is a plugin

cons:

  • only updates in Studio
  • developer of the game needs to do manual updates
  • it is a plugin (unnecessarily complex)
wrap the light in a module script

in this variant, we make the light a child of a module script
in that module script, we add the code:
return script
pro:

  • auto-updates every time a server is started
  • only 1 variant in the toolbox

cons:

  • new fixtures need to be taken out of the module script first
  • no preview of the light in the toolbox
Software as main

in this variant, we set up the fixture as a child to the software.
then use a require on the light and throw the light itself away.
pro:

  • auto-updates every time a server is started
  • only 1 variant in the toolbox

cons:

  • no preview of the light in the toolbox
  • messed up explorer

if you vote, please reply with why.
if you have another option, please reply with what.
if there are questions, go ahead and ask.

#2

I think the first option is best. The 2 library input seems to be the best cause it auto updates and its easy to add lights. Even if it could get messy you can always re-organize and edit groups in studio.

1 Like