Midacre

Scanning at this stage of the game, most players will have container augmentation talents at 5, and have had plenty of time to accumulate scanners and cores, so players can now easily scan with multiple cores and scanners. I'm using 7 small cores and 21 scanners, to scan a super-flower at once. Actually, by the time I have started scanners on the 7th core, the scanners on the 1st are ready to be read. So I can keep busy while 15 minute counters go to zero, but so is the server. What if there were a new element for scanning which could scan the whole super-flower at once, with just one element? I could scan in a radius, with a max range dictated by talents, returning results for all tiles within its range. Obviously, the longer the range, the longer for scan results to return. It should be possible for a player with the current scanners - or a smaller radius setting - to ninja someone using the system I'm proposing here. So there is a risk using a larger diameter scanning area. You wouldn't get any results until you finished the scan. The scan time versus diameter could be adjusted to give results in about the same amount of time players can achieve now with multiple cores and scanners.

Because they upgraded the LUA "backend" to 1.4 and it doesn't do that anymore, so they'd have to code a new backend to do it the old way.

Be careful what you wish for.

If I have code like if (engine.isActive) then ... The change to boolean return would not break this code snippet. However, if the code is if (engine.isActive == 0) then ... The change will break it. Is that right?

But "under the covers" booleans are still 1 and 0. So this seems like an unnecessary breakage to me. We're not writing LUA applications for use outside the game. Why does LUA inside the game need this breaking change for compatibility with LUA outside the game?

Any person who has rights to the container can set it as the schematic container for the whole construct, because access to the action is given by access to the container, not access to the construct.

We also need a RDMS right for this. Orgs need to be able to have members drop off ore, which means rights to containers. But even without any rights to operate industry units, any org member with container rights to any container on the factory construct, can take the factory offline.

Entire factories can be taken offline mistakenly with one click. Please move "Set as schematic container" to the Advanced menu so players don't accidentally take their factory offline. Anyone with container privileges can do this, even if they have no privileges to the industry units. I would have posted this to the Ideas forum but that is shutdown.

The starter outposts on Demo should include a Surrogate Pod so demo players can more easily experience the social aspects of Dual Universe. Crafting a T3 item like a Surrogate Pod is a daunting task in such a short time.

I feel like the quality of life in this game could be greatly enhanced with more right-click context functions and a more object-like interface with in-game items. Could be able to right-click an item in inventory, and go to the market page for that item, or directly to place a buy order for that item. Or barter the item to a nearby player. Just like you can equip an item or view item details. And on the item detail window, the properties could also be interactable. Could be able to open the nanopack from the item's parts list and be ready to queue up the task. But there could be more functions to items than just right click. Could be able to drag an item into chat, and produce a link to that item which other players in chat can access by right-clicking, so they could go to the market page for that item, or queue up the talents for it, instead of leaving chat to open some other screen and search for it. Items could be interactable in chat the same way we can interact with bookmarks in chat. That could make chat much more useful than it is now.

If I paid for my sub with with GTC rather than recurring subscription through the account page, will I get credit for the rewards?

If you want to limit the number of schematics and therefore factory processes a single player can run, but also plan to introduce talents to increase the number of schematic copies a single player can produce, why not just go directly to talents controlling the number of industry processes a single player can run, and skip schematics altogether? Make it work like construct slots. Some for personal use, some to donate to an org for org industry. It would be consistent with a mechanic that already exists in game, and explicitly invokes cooperation via organizations.

I believe they are saying that the implementation of energy management will be just as nonsensical as the implementation of speed limits.

Is DU a game about sculpting voxels, or is it a game about placing elements? Voxels are what makes this game worth playing. Making voxels second class citizens to elements destroys what makes this game worth playing. NQ doesn't seem to know what makes the game worthwhile.

Full wipe, but in the new game you can select/copy/paste a whole Medium Core volume in build mode.