The app begins by reading from mongodb’s ‘Models’ collection, initializing each document into Objects each representing a Gasm Model. Then, for every model, a Stream is instantiated, which itself immediately inits one BrowserAgent. Representing an instance of headless Chrome, browserAgent is responsible for communication between Gasm’s app and each model’s stream. In parallel, Stream calls the static ServerUser.getOne, to receive the login credentials of an available Server CB account.  After both of these Promises resolve, Stream sequentially calls browserAgent’s .login(), .goToStream(), & .listen().

When a model goes live, browserAgent emits “model_state_change”, when the state received is “live”, Stream calls .start(), which calls methods .model.setOnline() & .browserAgent.connectToBot(streamerToken). The latter will input ‘~^connect/${streamerToken}’, every 3 seconds, streamerToken being an optionally encrypted password. Every msg beginning w/ “~^” is hidden in chat. While the bot’s var “serverUser” is null, it will pause all execution, sans the eventListener, cb.onMessage(). For every message, isServerUser(msg), upon returning true, connectToServerUser(user) is called. This sets the global var serverUser and whispers to serverUser that the bot is ready to receive the script. sU will then send the script in <=1000 character chunks; all of sU’s msgs are instantly hidden. Once the bot compiles the received string into JSON, it notifies the streamer that the show can begin. 

If the streamer has not enabled script auto-start in the bot’s settings, they’ll enter “/startscript” in chat to start the first act. From this point, the script will display notifications and (synchronously) survey viewers. 

Upon “model_state_change” receiving “away”, Stream calls .model.setOffline & .restart(), reinstantiating itself, then waiting for “live” again. responsible for communication between Gasm’s app and each model’s stream. In parallel, Stream calls the static ServerUser.getOne, to receive the login credentials of an available Server CB account.  After both of these Promises resolve, Stream sequentially calls browserAgent’s .login(), .goToStream(), & .listen().