Databank support or data store for Lua screens

[matpratta]

Basically, the idea here is that we could link a databank to a Lua screen and have an API to access its contents. Right now any larger inputs need to be "buffered" with a PB into the input field, which not only is slow but probably ends up taking a toll on the server. Having screens being able to directly access databanks or at least having an internal data store could potentially improve this.

[NQ-Ligo]

Hi there !

Lua screens were not designed to be controllers like a programming board, or a command chair. They are only interface devices, it's a design choice we have made.

Anyway, we are considering, no promise again, local and/or synchronized solutions for Lua screens that could improve the data flow between the controllers and the screens.

I can understand that one can want to do everything without constraint, but this is part of the design choice, and the desire to not make elements of the game as "obsolete" because the screens could replace everything.

[samdeane]

and the desire to not make elements of the game as "obsolete" because the screens could replace everything.

Let the game evolve!

There's too much time spent worrying about how lua functionality will break existing game loops; not enough time thinking about the new game loops it could open up. Especially in a world where NQ has major constraints on the resources it can bring to bear.