Dual Universe Creators

An addition to my Factory Monitor scripts. This one Monitors all Transfer Units on a core (up to 408/6 screens) . Simply connet core and screen(s) in any order. The script will tell you how many screens you may need even if it crashes due to lack of screens :) grab it here: https://github.com/BartasRS/Transfer-Units-Monitor As always, tips are greately appreciated but not required ;)

The script comes with a functional interface to display your ship core health, shields, and all 4 resistances. The shield manager handles auto venting your shields once they either break completely, or fall below the configured amount There is also a display to display your core health and shields as well. It displays how much you have in each resistance It auto configures your shields based off the incoming attack damage.

A small Node.js CLI built to ease the development of Lua scripts, from small to large ones. https://github.com/wolfe-labs/DU-LuaC ⭐ Features: • Project files and management, with configurable link types • Multiple source file support, compiled to Lua, JSON, YAML and CONF • Code on your favorite IDE or editor, be it VS Code, IntelliJ IDEA, Atom or even Notepad! • Automatic code completion support when used with EmmyLua on VS Code and IntelliJ IDEA • Multiple build targets, such as development and production, allowing control over minification, etc. • Multiple entry-point support, allowing you to use a single codebase to code multiple components of a build, such as different Programming Boards, seats, etc. • Support for code libraries, both built using the compiler and outside it • Integration with GitHub Actions available • Built-in helpers for linked element detection and event handling, no need to worry about multiple filters anymore! • Copy output JSON/YAML code directly to your clipboard, speed up your workflow! 📋 Requirements: • Node.js 18 or LTS • Tested on both Windows and Linux 🚗 Getting Started: 1. Install our CLI tool via `npm i -g @wolfe-labs/du-luac` 2. Run `du-lua create hello-world` to create a new project folder or just go into an existing one and run `du-lua init` then follow the prompts 3. When ready, run `du-lua script-add main` to create your main Lua file 4. Run `du-lua target-add` to create a new build target 5. Run `du-lua build` to compile your project You should now be ready to build your next big thing! ℹ️ Source and Documentation URL: https://github.com/wolfe-labs/DU-LuaC/

A board that monitors and broadcast fuel info to a screen/databank/emitter. Simply connect 1-9 fuel tanks, 1-9 screens, and/or 1-9 emitters.

Allows you a screen interface to view the contents of a container. Comes as both a screen and board script.

A script that provides various info / functions for your ships, using LUA api with multi touch screens. Info & instruction on github: https://github.com/Krengus/DU_ASTco/tree/main/ShipInfo

--Still in development Free Industry script to manage and update products. https://github.com/Anauine/DU-MachineControl

Essentially, this script provides an AR overlay to your world to view waypoints you have set with Archaegeo's script, in addition to the planets around you. Like all AR scripts made with the AR projection library, there are specific conditions under which this script functions correctly. If you are on a planet, assuming you aren't in a cockpit in another ship, the script should function flawlessly. It will only work in a seat on the construct the programming board was deployed in, and only if you correctly calibrate said seat, assuming you have "freelook" enabled. What freelook enables is a way to track where your camera is looking purely based on your mouse movement. Of course, this comes with one major downside: it won't work in the third person. Nor will it work if you don't calibrate your pitch and heading. Calibration takes place in the form of looking either up or down, pushing your mouse past the limit you can look and then looking either left or right. The accuracy is around 1 degree when looking straight on if the calibration was done properly. (Inaccuracy is purely a result of the mouse capture not being absolutely perfect) In space, as long as you are on the ship the programming board was activated on, it should function for both in a seat, walking around and jetpacking. Note that for walking around, you need to calibrate your pitch. There are a couple more settings to change around if you want to. However, that is about all you need to know. To use the script, copy the JSON file contents found in the link below and select something like "paste Lua script" using a programming board. Connect the programming board to the core, and activate! If you have some saved waypoints using Archaegeo's script, connect the databank to it, and it should load his script's waypoints as well. Link: https://github.com/EasternGamer/AR-Library/blob/experimental/NewWaypointer.json Disclaimer: I coded this, however, Archaegeo provided the idea, hence when starting the script he is credited and used to host the script.

This project leverages the recently released screen LUA APIs to provide an interface with the programming board. With this system, you can set up a public drop off point for ore with requirements for each available ore, and set the system to show all tiers, or single tier at a time. https://github.com/jdelgado-dtlabs/DU-Ore-Manager

This script offers all shield functions on any size screen or screens. It uses touch buttons and is well tested. If you are interested, join my scripting discord at https://discord.gg/ttajxhZYXY

An expanded version of my Factory Monitoring Screen for people with crazy big factories. Basic version resulted in text overlaps and eventually script crash due to 50k characters limit per screen. This version displays Metalworks, Electronics and Glass industry on screen 1, 3D Printers, Chemical Industry, Refinersm Honeycomb and Smelters on screen 2 and, finally, Assemblers on screen 3. I figured out it should be a proper setup for most big factories tho I know some of you are crazy :P Simply connect core and 3 (or 9) screens (in any order) to Programing Board and run the script. I humbly suggest setting refresh rate (In Lua settings) to 5 to avoid possible laggy situations with a lot of industry running. Script comes with industry locator. Type help in Lua Tab to see available commands. grab it here: https://github.com/BartasRS/Factory-Monitoring-Expanded As always, tips are appreciated but not required. Enjoy

Here we have the default system information screen made by NQ. However.... It can be so much more! Ill be doing different variations of the screen to show examples of what all this screen can do. Ill start off with a simple edit and work my way to something way different. Showing off anything from in game items, Org information, and even exchange sales items. https://github.com/LocuraDU/DU-System-Information-Screen ----- I only offer help/support at https://github.com/LocuraDU https://discord.gg/TB2ecEd5rs I try to get around to helping on other channels but if you want help please use one of the above places.

for the script go to https://github.com/Davemane42/DU-Scripts#player-logger-script Log player activity to a Databank(s) and render to a screen v3.2 tested with 1300 entries with 8 databanks will import older data when upgrading (save the data using the 'dump' command just in case) Elements needed: 1x Programming board 1x Manual Switch 1x Screen 1x Detection zone 1 to 8 Databank(s) Instalation: 1. Copy the content of the link below and paste on a programming board lua config https://raw.githubusercontent.com/Davemane42/DU-Scripts/master/PlayerLogger/PlayerLogger.json 2. Connect Detection zone -> Manual Switch -> Programming Board For multiple detection zone: add an "OR operator" (only 1 needed) in between Detection zones and the Manual Switch 3. Programming Board -> Manual Switch (both way) 4. Then do the same for the databank(s) and screen . 5. Finnaly, hit ctrl+L while looking at the board add your username in line 7 of unit.start() rename the location to your liking Activate the board manualy and type "help" in the lua chat for the command list 'clear' [clear the databank(s)] 'dump' [dump the table as JSON in the screen HTML so you can copy it] 'exit' [exit debug mode] 'help' display a list of commands 'remove (indices)' [remove an entry from one of the table] 'update' [Update the screen code]