| Dual Universe is currently under a .|
All players with access to the game are strictly prohibited from sharing any details about their experience or gameplay.
As such, information on this wiki may be inaccurate or outdated.
We have begun migration of most wikis to our new host, Amazon Web Services. All but the top 100 wikis are in read-only mode until the migration is complete. Estimated completion: End of Week.
Distributed Processing Units[edit | edit source]
DPUs can be used by players to set up automated behaviors or reactions in constructs that activate in response to pre-set conditions. Players can add Lua scripts to DPUs, and each DPU has "slots" into which elements can be inserted, which allows the DPU to use its Lua scripts to effect the inserted element. Each DPU has several event handlers, each with its own filter, which allows the player to set conditions that activate the DPU. When the filter conditions for an event handler are met, the corresponding Lua code for that filter is executed. The code can use or assign any of the values associated with the elements that are connected to the DPU.
For example: A player can connect a DPU to a locked door and a series of sensors, with the filter requirement being set to unlock the door when the sensors are triggered in a certain order.
Multiple Players and Scripts[edit | edit source]
Scripts run from the computer of the script owner, but the text of the script is synchronized with all players within render distance, so its effects can still be seen and/or triggered even if the player running the script isn't within visual rang of the one triggering the script. The script's actions are synchronized by the server for all players. Even though scripts are run on the client's computer, several players can still simultaneously run different scripts that were created by a single player (and thus running on that one players computer), and all players can see the script and its effects. The only exception is that there cannot be two players controlling the same element at the same time. A player having rights (via RDMS) to use the scripted machine will have access to the in-game scripting editor, and will be able to reverse engineer the script.
In-Game Editor[edit | edit source]
The in-game script editor will be the primary tool for creating, editing, and viewing Lua script. The editor screen is broken into elements on the left-hand side, event handlers in the middle, and the raw code on the right. The editor enables user to quickly create script by providing a series of predefined functions that can be invoked and events that can occur associated with each element.
Limitations[edit | edit source]
Certain limitations have been implemented to ensure that some aspects of the game are not devalued for players.
- Scripts will only run if a player is within a particular distance of the Core Unit running the script.
- Weapons, when scripted, will be extremely inefficient or underpowered compared to unscripted weapons used by players (for example by limiting number of actions per second achieved by the script). This is to make the game more balanced.
- Mining cannot be scripted to any extent; mining can only be done by a player using their Nanoformer.
Note[edit | edit source]
In time, this page will become a much more comprehensive guide on scripting with Lua. For now, with so little information available, it is merely a summary.
See Also[edit | edit source]
External Links[edit | edit source]
References[edit | edit source]
- Dual Universe YouTube Channel, "Dual Universe DevDiary Updates - July 2017 | Pre-Alpha Video", Timestamp: 0:48 - 1:56. https://www.youtube.com/watch?v=4Vrf50dZrv4. 07/31/2017.