Merzie

Just piling on: I don't mind helping orgs to slots. But why should my ship collection on sanctuary be at risk? Why would I be limited in my (apparently a little megalomanic) building wishes? I mainly play solo and try to give what I got leftover to my fellow corp mates. But when I can't have fun solo, I'll not give to my org either. I just stop playing the game alltogether.

Limiting constructs this much is a serious downgrade in playstyle.
 

Hmmm, respectfully I completely disagree. It's not about punishment, it's about consequences. You leave your ship cluttering up someone else's space, you lose your ship. Done deal.
 
The construct owner is *very often* not the DRM holder. I build all my own ships, but I also sell them. There's dozens of my ships floating around out there that people have paid me millions to be able to fly... Releasing the DRM means that anyone could just copy my design and sell it as their own... Pretty much defeats the purpose of DRM in the first place then if anyone can just take a ship they bought, get it's DRM unlocked and copy it.
 
As I said previously, that is already going to be an issue with this system due to handing out BP's and handing out the ship. Every time a ship expires, its design has been duplicated. That I understand as a natural consequence, it has a large time and risk investment in the method for each individual payout, but just unlocking the DRM opens the door for as many copies as are desired.

Hi all!
 
After reading your feedback, we have noted that the removal of log functions was having a big impact on you. So after some internal discussions to find a solution based on your suggestions that would meet your expectations but would not be too heavy to implement, we have made a decision.
 
We plan to add with Panacea, the ability to copy to your clipboard the content of a chat channel, and clean it up.

It is certain that this will not provide a nice solution for the problems related to the lack of data export to virtual currency systems. We have some ideas for this but it won't be for a while unfortunately.

Hopefully this announcement will allay your concerns  

NQ-Ligo

Another request if you remove the obvious way to get stuff from the logfile: A nice json file with all itemnames, descriptions, ID's and recipeID's etc. Stuff like that is very hard to get out of the game otherwise...

The issue is parsing the log to do outside things, aka notify on discord or via text message etc.
 
If you intend for the log to be readable for some purposes, I would recommend a randomized delay before the log gets written so it cant be utilized for instant notification of in game events.
 
Example from log: 
<record> <date>2022-01-17T19:48:50Z</date> <millis>1642450010131</millis> <sequence>18617</sequence> <logger>D:\Bamboo1\xml-data\build-dir\WC-REL21114-CSTS\Source\game\scripting\DPUnit.cpp:212</logger> <level>WARNING</level> <class>WC-REL21114-CSTS.game.scripting</class> <method>NQ::DP::Unit::execute</method> <thread>21872</thread> <message>Executing a Lua method in the wrong thread. method='setAxisCommandValue', inFlush=true, method is Flush compatible:false, method is Update compatible:true</message> </record> The above occurs whenever a method is done in flush that isnt allowed.  If i was nefarious, i would do that intentionally and log parse for it for my nefarious notifications

Hi all!

I will try to answer your first questions. Don't worry, I'll do some more passes tomorrow.  

No possibility to copy content out of the game? @Ashford @Helediron@Wolfram
We know that these log functions are used by some people legitimately to get data out of the game, but it has never been the only way to copy data. But it was the only way to get data directly out of the game automatically.
In your case, you can use a screen and log on it. Currently you still have setHTML which will allow you to write very easily on it, without even worrying about the number of characters if your goal is just to copy the data out of the game at the end. You write your log in it, once finished you edit the content of the writing and copy the whole content.

I know that many players will express their concern at the removal of these log functions, even if their use was legitimate. However, it is important to understand that this is a decision that was made after much consideration and the balance was quickly tipped in favour of total removal. And any suggestion such as adding a Lua-only log file or segmentation of the logs, does not solve the problems as automation or drive overload. And even the fact it's executed explicitly only, it do not prevent automations and some exploits and leaks.
I'm not sure either that being able to select the Lua chat and copy it is a solution either, or even more practical than a screen anyway. 

However, we will see with the team if a better solution is possible, there is no perfect solutions currently.

On a personal note this time, I would suggest adding to your systems to allow your users or you, the developer, to connect a screen that serves as a console.
A bit like you do with a car, it's a closed system, a black box, but it can provide us with controller or error data through their control port.


What about reading the log ?
We see the logs as a tool for community projects, such as an external community market platform, so we want to keep the logs as accessible and readable as possible.
 
Therefore, we try to remove sensitive information from them as we did in the case of Market Orders. However, it is possible that some of the information may not have been considered dangerous at first sight. In this case, please let us know @Archaegeo . We would rather "secure"/"censor" the data on the lgos, than have to remove them completely. Of course, I can't guarantee that in the future this will be assured, if it becomes unavoidable we will get to that point. But that is not our goal.


More possibilities for the game camera? @EasternGamer
First of all, thank you for your topic, I have read it and it is interesting.

It's the kind of thing we could consider in the potential future, but as you said it can be complex and even more so to secure it. I'd like to say that I'm looking forward to seeing what you do with it and see what we can do or not.

Thank you for these suggestions though, they are complex suggestions, so it's hard to say whether or not this is something we could or would want to do right now.


Sound API, missing volume control. @Archaegeo
Indeed, this is something that is currently missing. The volume of the sound played will only depend on its base amplitude and the audio settings of the game.
This is something we'd like to add, but to be honest, it requires some deep changes to be done.
Anyway, as mentioned in the devblog, this is a first iteration that may evolve in the future.


I hope that these answers will help you all the same and help you to understand the situation on the logs, on some aspects, they are globally complex subjects.

We are never out to hurt anyone, however we do have to protect the security of the game. On top of which, what you're describing above is very much not in accordance with the EULA and will see you get into trouble for it. Reading the log files alone however, does not. There are a number of other concerns, such as the ability to write directly to a players hard drive through the logs. Which is one of the primary concerns about the logging functions.
 
We have also been very clear about this from day one when players found this function. We were not enforcing it, but it was never a "feature", and never included in the codex. I have mentioned on multiple occasions in multiple locations that the logging functions would likely one day be redacted but we would observe what came from them in the meantime.
 
As such, the audio feature is being developed to provide a suitable replacement for the community created audio framework.
 
 
To be clear, this was also very clearly stated in the patch notes. If you read them carefully you'll notice that the VR capable talents that are mentioned are the ones that count towards the generation of Calibrations. Not the ones that consume them.
 
 
The camera Lua feature set does not permit a Lua script to take control of your camera. It grants the Lua the ability to read orientation of the camera. Allowing for such things as accurate "Alternate reality" HUD designs, that move with the background and allow you to have virtual "panels" around you. It does not however allow a Lua script to force your camera to look at something.

Another request if you remove the obvious way to get stuff from the logfile: A nice json file with all itemnames, descriptions, ID's and recipeID's etc. Stuff like that is very hard to get out of the game otherwise...

Another request if you remove the obvious way to get stuff from the logfile: A nice json file with all itemnames, descriptions, ID's and recipeID's etc. Stuff like that is very hard to get out of the game otherwise...

The asteroid spawning is entirely automated. It got interrupted by a situation which was supposedly impossible but is not. We will sneak in a patch at next minor release to prevent this from happening again. Meanwhile this was manually fixed and asteroids are spawning again, yay.

This is the output of a script that dumps all global variables. Lua coders may find this somewhat useful.
 
The script was run in r0.21.2 on a hovercraft seat that has 2 fuel tanks and a radar linked. Some functions were called with pcall. The first value indicates whether the call was successful, the second is the actual return value or the error message.
 
 
To see only elements' functions, visit this topic.
 
Dumping script
The script used for dumping is based on something I found on Stack Overflow, with some extensions.
 
In unit start(): https://gist.github.com/d-lua-stuff/180707c172382d06d2c80213a1638f66
In system update():
coroutine.resume(dumping_coroutine) The script will run for a few seconds and then automatically turn off. Output is saved to Dual Universe 's log files in %LOCALAPPDATA%\NQ\DualUniverse\log
 
Dump analyzer
To avoid having to look through the logs manually, a Python script was written. It extracts the output of the globals dumping script from Dual Universe's log files, and creates separate files for dumped globals and for members of each linked element.
 
Usage:
pip install six python dump_analyzer.py C:\Path\To\Log\File.xml Change log
2020-09-01. Posted the first version outside the NDA forums section.

Often when either trying to move, or just brake down a construct you run into the problem where we can't easily find all the parts.
 
Normally it is a few hidden voxels which are so small you can't see them, maybe they are under the ground.
 
Often the only way to do it is to get a GM to assist.
 
Other times you just want to move one of your buildings, so you take a blueprint and then have to take ages stopping every industry, removing their schematics and then removing the machines one by one.
 
What would be nice would be either a tool, or a right click option on the core which when selected would take a blueprint of the construct, then completely deconstruct it and place all the elements, honeycomb, schematics, container contents etc into your linked container; or tell you it can't due to not enough size. 
 
- If you don't have rights to take a blueprint it would warn you that there will not be a blue print to check if you wish to procees.
- If you don't have the rights to deconstruct the construct normally, or any single part of the construct it would naturally not work and tell you of lack of permissions.
 
This would be of great assistance to use players, and also reduce a common request which is placed on the GMs as shown in the attached image
 

Big missed opportunity here.. 
Invert this mechanic (need permission to use "gravboots") and you instantly fix the problem with stowaways on ship hulls .
 
Also.. not sure how this is worthy of a separate devblog.. but I digress

[Updated Nov 19, 2020 @ 3:02 PM EST]: The rules outlined below apply to teleporting both avatars and constructs. This means that, outside of the list of approved scenarios, we won't be able to fetch your ship and bring it to your location. 
__________________________________________________________________________________________________________________________________________________________

Good day fellow Noveans,
 
I come bearing support-related news! More specifically, I’d like to address teleportation requests with all of you.
 
For a while now, we’ve allowed players in need of a port to say the word on Discord and - voila - your wish would be granted! ✨
That worked well for a time, but our Discord support channel is now beginning to slip under the veritable wave of port requests… and we’d like to rescue it and all those in need of a ‘lift’.
 
As of November 19th, we would like everyone in need of teleport-related assistance to use the in-game chat support, or submit an official support ticket. By using the in-game chat function instead of Discord, you’re likely to receive an answer quicker because our GMs are ready and waiting for you there!

Having said that, we’d also like to inform everyone that we will no longer grant port requests if you’re simply out of fuel, stuck in one of your own constructs, or just generally stranded. All port requests will now be investigated, verified and potentially denied if the request falls outside of approved scenarios.

Some examples of when to ask for a port (approved scenarios):
 
if you’re stuck in an Aphelia construct if you’re trapped in any other player-owned tile (unable to dig) if you’re unable to get past the loading screen upon logging in
  What to do if you’re just stuck/out of fuel/stranded: 
 
Don’t forget: there are plenty of player organizations available to assist in your travels through space! Be sure to check out the organizations and services provided on Discord and our Forums. Some organizations will be happy to provide you with transportation, refueling, repairs, building help and so much more!! ?

How to contact support:

To access in-game chat support, simply click the “support” tab in-game, as depicted below.


 
From here, it’s as easy as typing up your request, starting the message with "@NQ" and sending it off!
 
To submit an official support ticket, please click HERE. ?

Then, select the hyperlinked text that says “submit a request” in the top-right corner of the page. Once you see the screen featured below, select the appropriate category for your issue and go to town!


 
(Quick note for those submitting crash reports: PLEASE do not forget to include a crash log and/or XML logs with your ticket!!)

And there you have it! Let’s all do our part to keep the Discord server free and clear of port requests so that players with big ol’ bugs and other issues to report can receive the visibility they deserve.

~NQ-Naunet

PS - I want to give a special shout-out to all of our support staff for everything they do!! Thank you, all!!