Install & Usage:
For the first version, connect the screen first, then up to 9 machines. Screen can be any size.
If you wish to give the machines a custom name:
Right click the programming board and click Edit Lua Script.
Click System then the very bottom start, just below update.
On line 16 add the names you wish the machines to be called. (See line 17 for examples)
Then on line 22 change:
name[i] = "Machine " .. i
to:
--name[i] = "Machine " .. i
Finally: Click Apply and restart the programming board.
Using the monitor / databank version:
Connect the screen and databank to the main programming board. (Main PB)
Connect every other programming board to the databank first, then up to 9 machines. (Mach PB)
Turn on all the Mach PB's first, then turn on the Main PB.
Thanks to all the people who contributed to this. If you have any suggestions or feedback, or have a bit of code you would like to contribute to this project, feel free to email me
*** This version now works without the screen glitch where everything blinks.
Here is a quick video tutorial on how to install and some basic usage for this version.
➡️Video Tutorial⬅️
This is the databank version of this script. It's for monitoring machines only. Eventually I'll add more features to this, but I don't want to overwhelm the simplicity in its intent. It's meant for larger industries, so you can have a central monitor that shows you which machines are running and which need attending.
There was a problem pasting the JSON into the spoiler, so I have made it available to download. Right click and Save as, or click the link and copy the entire page of the new window.
Here is the JSON code. Just copy/paste it to the programming board that will be hooked up to the screen and databank.
➡️ Main PB⬅️
Here is the JSON code. Just copy/paste it to the programming board that will be hooked up to the databank and the industry machines.
➡️ Mach PB⬅️ *Updated 9-29-2020
**note: If you need to remove machines from the machine PB's, you need to do 1 of 2 things.
1: Edit LUA on the PB you removed the link from. On the left you will see the names of everything connected. db and mach1 - mach9. The mach# must start at 1 and can't skip any numbers. So if you have 3 machines and you remove mach2, you must rename mach3 to mach2.
2: (The easiest method) Repaste the JSON code to the PB. This will rename everything for you.
***You also need to clear the databank. Turn off all the PB's then, edit LUA on the main PB. Click System and the very top start. Change --db.clear() to db.clear and click apply. Turn the PB on then off then change db.clear() back to --db.clear(). Finally, turn all the machine PB's on first, then the main PB.
I'm working on a fix to make this easier.
Here is a quick video tutorial on how to install and some basic usage for this version.
➡️Video Tutorial⬅️
It was brought to my attention that the spoilers were giving errors when pasted to the programming boards. The spoilers were removing bits of the JSON for some reason. So instead, I have added links to the code located between these ➡️⬅️. You can either right click the link and Save As. Or you can click on the link which will open a new page. You copy and paste the entire page into your programming board.
This is a work in progress. The development is completed, but it is constantly being refined and upgraded. I encourage and welcome feedback and you are more than welcome to submit your own code, in the comments, for consideration. You can also email me using the link in the first comment.
See 1st comment for more info.
Here is the JSON code. Just copy/paste it to the programming board.
There was a problem pasting the JSON into a spoiler, so I am making it available for download. Right click and Save as, or just click the link and copy the entire page and paste to PB.
See video link at top of this post for a tutorial.
***I wasn't able to get rid of the graphics glitch entirely, but I significantly reduced the shift. Now, it's a minor annoyance instead of a massive pain.
➡️ New Industry HUD.⬅️
We realize there is some confusion regarding whether certain scenarios occurring within the game world are permitted or not, and would like to clarify these points for everyone. In short, we’d like to ask our community to use common sense when encountering issues in the game; If it looks like an exploit, smells like an exploit (do pixels smell?), or sounds like an exploit, chances are it is an exploit. Don’t DU it! Report it. (support.dualthegame.com)
We are in a testing phase, and reporting these bugs/issues is important. Abusing them may lead to sanctions against accounts, up to and including removal from the game. We will not take ignorance as an excuse, especially in the following list of scenarios. Please note this is not an exhaustive list, and we will continue to expand upon it as needed:
“ALT + F4 Emergency Brake”: We acknowledge this is not an intended game play loop that is being intentionally used by players. We do plan to counter this action in the future but do not consider it high priority at this time. At this time, we will not take action against an account for using such. [Allowed]
Parenting Ships - Dragged to PVP Space: This is a hot topic and one we wish to be very clear on. Intentionally parenting any construct without permission of the owner is not intended for game play. A fix has been rolled out that will address the ability to parent constructs together via the maneuver tool. As we have not previously clarified this point, we will not retroactively punish this abuse, as of this moment forward abusing similar bugs/tools to replicate this maneuver in its current state can result in disciplinary actions on an account. [Not Allowed]
Attacking PVP Zone from Safe Space: Our team has been investigating complaints of ships being attacked in the PVP zone from ships outside of the zone. Our investigations strongly point to sync issues between clients. We will continue to work with this feature, but recommend players consider the zone lines for PVP to be somewhat fluid and not absolute. Our version of the neutral zone! We ask that you continue to report cases with positions, but will not action accounts at this time, unless an additional exploit is discovered. [Allowed]
Overlapping engines with other elements (obscuring): A fix will be rolled out that will prevent this from occurring. No action will be taken, unless additional abuse is occurring. [Allowed]
Theft Via RDMS: RDMS permissions and settings are the sole discretion of each player. We advise you take the time to get to know and understand the system and be cautious when making a construct or element usable by unknown players, including the use of your friends list. Not every player has your best interest at heart. We can not get involved with permission based theft, whether as an individual or an organization. We encourage you to review your friends list each time you add or remove someone and ensure your construct permissions are set accordingly. The context menu options that set public access currently do not have a confirmation prompt, be careful as setting public access to said construct will allow every player in Dual Universe to go into build mode and remove/place elements and voxels. [Allowed]
Environmental Walls/Creations: Use of the environmental and voxel tools allows the manipulation of terrain on owned and unowned tiles. You may build walls or other structures up to the allowed height, however, said constructions must not:
Block access to market places or tutorials
Must abide by our Community Standards (phallic/sexual, political, religious or otherwise offensive shapes are not permitted)
Must not be placed with the intention of interfering with neighboring players. When players can not agree, the final decision on what is and is not acceptable is decided on a case-by-case basis by Novaquark staff.
Marketplace Construct Parking: Players are permitted to park at marketplaces with their transport vehicles so long as they are not preventing use to other players or obstructing entry or exit points. Vehicles whose purpose is advertising (organization, service or otherwise) must abide by the following rules.
Organizations and individuals wishing to advertise at markets may have one advertising construct per district maximum
Constructs may not be larger than “Small” sized
Constructs may not block access to any building, entry points or dispensers
Advertisements must not be placed/parented on constructs that don’t belong to you
Constructs that violate these terms will be removed from the game without warning or compensation.
Mass Manipulation in Transportation: Players who utilize bugs to bypass the weight penalty of their inventory, other players, other constructs, etc to move mass through the game are not permitted. This includes:
Adding additional mass to an already piloted ship [Fixed]
Docking mass to an already piloted ship [Fixed]
Circumventing linked container range [Fix Pending] [Not Allowed]
Item Duplication: Any method of duplicating items or resources (including quanta) is not allowed at any time. Any incidents of bugs of this nature must be reported to the support team at support.dualthegame.com [Not Allowed]
Boarding without permission: As the deployment of the docking update is pending, the boarding of other players' constructs without consent will be considered an exploit. [Not Allowed]
Offenders will be teleported away; repeat offenders may be subject to more serious repercussions.
If you are boarded by another player and wish to have them removed, please report it either by creating a ticket here or by messaging @gm through the in-game Help channel.
We do recommend you keep regular backups of your constructs in the form of blueprints in the case you lose a ship (through intended means (sale, give away etc),or undesired results such as in PVP, you can still recreate it later.
How to Blueprint (to save your ship/build):
Enter build-mode on the construct, right click anywhere on the construct and click “Create Blueprint”. The blueprint will then be generated inside your currently active inventory. It is wise to keep hold of a copy of any of your blueprints inside your personal nanopack, as these are safe and not lost upon respawning.
We realize this is not an exhaustive list, and we will expand upon it as time goes on. We also understand some members of our community feel that using a bug or exploit prior to acknowledgement by Novaquark is considered okay. We’d like to state that any intentional use of a bug or exploit will be treated harshly going forward. This is the one and only warning we will issue on this topic. Please just don’t DU it!
On behalf of the entire team, we thank you for helping us make Dual Universe a better place!
