Julius_de_Carnutie

I mean it's not like energy management was a promise since KS and Survival Mecanics an absolute need in order to make some sense out of this... unless there is no "civilisation rebuilding" ...
Just checked, in fact, this vision has been replaced by "Reboot Society", which is a bit more vague but still can be interpretated as a "Civ Rebuilder Game".
The basic needs ( food , water, clothing, shelter, occupation) are the necessary starters for any economy, then don't want to wipe because still searching the adapted mecanic, ignoring these + power management (legitimate sink) while without these there's no economy. Take a look at the actual market. 
Saturated with t1 sells, eventually with all products up to t5, with very low adversity in buy orders and sometimes even nothing about recipes parts starting from lv2.
People don't eat fixations, or leds, or screws, or pipes. These are only useful to the industrials who have the machines + schematics to process these. Best seller? Ore. Raw Ore. It's been 5 years in some months that they've been simply ignoring the basics concerning this part, which is not mince.

Tbf a lot has been accomplished regarding playability and sustainability, voxel rendition, but "rotating engines when?" if you see what i mean. It's ok to have an "upgradable" tech that you can more or less fix with time, considered the unusual scope of the game, it's less ok to put aside basics which fit the narrative. People need incentives to make it happen. We don't care quanta, as much as it's good to have some, it's preferable to grind over something that make sense in terms of "believable" needs to fulfill rather than force feeding the market to pay your rent...

I don't see more points right now, and most of all i'm never the best defender of an idea but it simply doesn't make sense to me that they don't adress the essential. A Reason To Play.

Title

Title

So far I am loving the game. No losses and no real problems. Looking forward to multiple solar systems!!the only downside is the gaggle of greifers always trying to cheat. Have to wonder how some have lost all integrity and humanity . But game is great so far?

I've been playing for almost a week now and I am very glad with the game in its current state!
It has been captivating and awesome and as a silver founder I must say: money well spent!
So thank you Novaquark for the great game and the fantastic job you did!

Then you have some problems, if such simple thing is diffucult to understand.

Hello Noveans, 
 
At this stage it’s hard to ignore that the “Market Heist” has definitely caused a stir of dialogue and reactions both in our community and on the internet.
 
We have taken some time to look at the situation in more detail: the actions of these players are not ok, not condoned, and will not be tolerated. We stand by our decision, and we’d like to better explain it. 
 
Most of what Novaquark builds within the game world, such as markets, institutes or the Arkship is not a player-owned construct. It is a part of the game play designed to serve all players. There are exceptions, like shipwrecks, which are designed for salvaging, and clearly communicated as such. 
 
We did, indeed, state to players that if RDMS is not properly set on a construct, and it results in theft, it’s part of the game and we won’t act upon it. This is to acknowledge that treason can happen in an organization, for instance, and is part of the emergent gameplay we’re trying to promote. 
 
Now, this does obviously not apply to NQ-built constructs, which are designed to serve a specific purpose in the game. It is obvious that these constructs, owned by NQ accounts or Aphelia, are not meant to be interacted with in the same manner as player constructs. Besides, they may contain some highly overpowered and unbalanced elements which were never meant to fall in the hands of players. So the situation with the market is clearly covered by section 5.2 of the EULA: “You must refrain from engaging in any behaviour that could harm NOVAQUARK’s image and/or reputation, that could harm one or more other Users or have a negative impact on their gaming experience, or that is detrimental to the proper functioning of the Game.”
 
Finally, and for the record, the issue with the market did not result in a wrongly-set RDMS, but rather in a duplication bug. Part of what we use is the same tools as players to build constructs. We create one district, then duplicate it. Something went wrong in the duplication process of one of the markets, which resulted in players being able to edit it.
 
Were we harsh? Yes. But we had previously communicated that we would no longer tolerate abuses of bugs and issues. We do realize that perhaps this started innocently enough in that someone pressed “B” while standing on a market. But it went beyond this, and that shows intention. The players involved indicated that they reported the issue, and after further investigation, one did, though not by following the proper feedback channel: they pinged a staff account on Discord in the middle of the night. We’ve clearly stated that staff do not respond to pings on Discord, and that the reporting method for exploits and bugs of this nature is either via our ticket system, or via a community manager on the forums. 
 
Even a proper attempt to inform us about an exploit doesn’t mean that it’s OK to go on and abuse it. Communicating an exploit to the NQ staff doesn’t serve as a way to absolve the players, it’s only meant to ensure that we fix the issue - it’s not a free pass to use an exploit. The banned players destroyed a player market by dismantling it, and the fact that they communicated with us via Reddit with a request not to be banned shows that they knew what they were doing was wrong. They posted on Reddit, proud of their ‘achievement’ and of the destruction. 
 
In the end, repairing the damage cost us hours of manpower across multiple departments, which could have been invested into further progressing the game. 
 
That is why we take this seriously. 
 
Here are a couple of things that we’d like to reiterate:
We are in beta.  Things aren’t always going to work as intended. But we have a persistent, single-shard universe, and altering its foundations impacts all players. Bug Fixes aren’t instant. They take manpower time to find, investigate, fix, test and roll out. We try to make sure that fixing a bug doesn’t introduce a dozen more. As beta players, we count on you to help us and report bugs, not abuse them. We believe that this is fairly standard for most games.   We genuinely hope this brings some clarity to the situation, and ask you all to remember this is a communal effort. We’re in this together.
 
Sincerely,
The Novaquark Team
 
 

Hey folks,
 
thank you all for your input. There's nothing wrong with having a debate, but the fronts have hardened and I don't think the opposing sides will come to an agreement any time soon.
 
To not let it be lost in the stream I'll link the follow-up statement by @NQ-Naerais one more time for others to find and after that I'm going to lock this thread.
 
As I see it this settles the matter. There have been complaints in the past that the rules are not being enforced properly and I've seen many fights about rule interpretation too. I even entered those discussions on occasion and shared my personal point of view - especially regarding the advice to take a "better safe than sorry" stance - and those comments of mine have been on top of official clarifications and announcements. That we have two strongly opposing sides in this argument is not new and didn't come with the Market 15 incident. I hope that as things become clearer and more streamlined, most of you will find a way to get comfortable with the rules in place.
 
Let's move on, continue to enjoy the game and build Dual Universe.
 
Mellow greetings
Mondlicht

Where did they report it? even so. DONT USE THE EXPLOIT.  If you report it and they fail to act it is what it is, you wont get banned.  BUT JUST BECAUSE NQ DIDN'T FIX IT IN 2 SECONDS DOESN'T MEAN LOLOLOL I GUESS ITS OK.  Use your fucking brain.  

The fact that they Wrote Pls NO Ban, just shows that they knew that they would be banned. This is a Beta game still in development and part of being in the beta is your testing and reporting bugs. Which you should have reported it and left the building alone. This was just a blatant bad response that you knew would affect many things in the Beta, but you choose to do it anyway. 

You knew you would be banned and you still did it. So you deserver what you knew was going to happen in the first place.

The devs are not players, their mistakes are just bugs. There was fair and broad warning before this: 
 

They should ban them too.  If but just because they haven't been banned yet, doesn't mean THESE people should get off.  At some point NQ needs to start enforcing rules and handing out BANS.  This is a step in the right direction regardless of their failures before this.  If someone steals using an EXPLOIT in RDMS, and epsecially doesn't report.  Perma ban.  If someone sets a perm or gives someone access, then thats intended gameplay.  I would be very frustrated if I lost my base to an exploit, especially if the people involved didn't get banned and there was evidence.  This is still a good thing.  NQ needs to grow a backbone.  Hopefully more bans will be coming in the future. 

I wanted to officially protest against the possibility of building kilometer-long tower structures closer than 50 km from district; market; it is a danger; such structures should automatically collapse !!!!

who is in favor please support it here

https://cdn.discordapp.com/attachments/758994403057991720/768900946608390184/unknown.png

No...
 
It is one thing to discover a bug like that and report it.  Even going as far as to put a small change to the structure.  But removing most of the structure then posting it all over Reddit with snide remarks and mocking NQ.  That is what got them banned.  
 
If anything the devs were quite adult about their response.  Harsh, but adult.  
 
This is prime example of bone head moves by players.  You know what you are doing is wrong, yet keep doing it, then when you realize you will get in trouble for it you ask not to be banned.  That is like taking the wheels off of a cop car and asking to not go to jail for vandalism and theft.  

Hello Noveans, 
 
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! 
 
Sincerely,
The Novaquark Team
 

Ok look all, you're not getting to play football / soccer / basketball / whatever team sport on your own. Makes no sense. Is it that hard to understand that a "civ building game mmo" is a team game? No it's easy because everyone here have at least 2 braincells. Want to lonewolf a team game? That's on you, i don't see any need to cater to that.
Good luck with this pipedream hope.

Have you unbalanced your ship?  I also notice you didn't say you'd put adjusters on the bottom.
 
Ah..  it just hit me.  Have you moved the core?  If so check that its arrow is still pointing forward and on top of the cube.

Why adopt an anti-cheat system?
It’s no secret: Cheating is prevalent in many multiplayer games. It’s an even bigger problem in a Single-Shard metaverse with PvP, like Dual Universe. Therefore, we needed to put several safety measures in place to ensure a fair game for all players. Our client anti-cheat implementation is one of these measures. The main goal of the EQU8 anti-cheat system we adopted is to prevent modification of the game client as a lot of cheats rely on these modifications in order to access hidden data, automate actions, or display extra information to the cheater. For example, a "wall hack" usually reads the other players positions in the game memory and overlays these on the game’s interface. The anti-cheat system has other roles too, but we don't want to enter into too technical details here. We’re no anti-cheat experts, especially client-side. On the other hand, EQU8 has a dedicated team working on it full time. They also gather experience from other games, so it makes sense to use their solution, which is already up and running, as well as their experience and availability to help us in that regard.  
Why using a client side solution instead of securing the Server ?
 
Client-side security is usually considered a bad thing, as the computer is controlled by the player. Indeed. In an ideal world, all controls and all security measures should be server-side. 
 
However, there are two good reasons to also use a client-side anticheat:
There are controls which are difficult to implement server-side, and which we don’t have any clever solution yet, nor the time to work on for now. For example, loading the game physics for all players at the same time, and ensuring no one is passing through walls, is nearly impossible to do in real-time. In security, there is also a notion called “in depth defense”. It acknowledges a system can never be 100% secured and thus requires several layers of security. If one fails, the second prevents further escalation.  
We know a client-side anticheat cannot be 100% bullet-proof. However, it does increase the technical requirements of any client-side attack. The better the anticheat solution is, the more skills and time are required… up to the point where the effort is not worth the gain.  This means two things: less active cheats in the game, and more time for us to identify those who fall between the cracks. Of course, it does not mean we are leaving our Server unprotected; Another reason why we delegated the client-side anticheat to an external partner is that it leaves us more time to work on the Server. And just to be clear, what we’re saying is not a challenge to attract any sort of attack here ?
 
Why EQU8?
It’s less intrusive than other, similar third-party solutions, and aims to respect players' privacy.
For example, EQU8 only gathers information when the game is running (and few personal data altogether). They also insisted to not get any personal data from us (like players emails or username); we only send an anonymous player identifier. You can check their FAQ at https://equ8.com/faq, and their privacy policy at https://equ8.com/assets/privacy.pdf for more details. It has low performance impact (actually, it’s almost imperceivable) and good reputation regarding false positives and potential crashes. The EQU8 team is very responsive and engaged. This is a big strength of theirs, and we greatly appreciate their unconditional support! The solution is very flexible and configurable, which is important because Dual Universe is a complex game that often requires specific tuning. Oh, and the most important: it detects cheaters efficiently. ?  
Launcher changes
The anti-cheat needs to install a Windows service on its first run to work properly. This requires administrator privileges, which is why the launcher requests them. This service only runs with the game. If the game is stopped, so does the service. Please also keep in mind that stopping the service on purpose triggers a kick, as it’s interpreted as a cheating attempt. The launcher currently requests administrator privileges on each launch. This is a bug which will be fixed soon. With the introduction of the anticheat, the client will refuse to start if run directly from the binary (Dual.exe). This is expected and is a technical constraint. You need to start the game from the launcher every time.  
What is authorized or forbidden
Modifying the game files is forbidden, (except for the "Game/data/lua" folder (this is the only location where you can add or modify files). Modifying the game cache is forbidden (by default it is located in the directory C:\Users\<user>\AppData\Local\NQ\DualUniverse\) ; Reading or modifying the game memory is forbidden. Disabling, modifying, or attempting to evade the anti-cheat in any way is forbidden. Playing at the same time with two or more accounts is authorized, but please note, that any form of automating multiple accounts is forbidden Helping someone, or driving someone, to do forbidden actions is obviously forbidden too. Discovering or knowing an issue, bug, or exploit and benefiting from it instead of reporting it to Novaquark is forbidden. Sharing accounts between different people is forbidden. Any action performed on your account is the responsibility of its owner. The Customer Support team won’t be able to help regarding any issues happening due to account sharing. The owner is responsible for any action made with the account. Trying to degrade the game performances of other players for any reason is forbidden. Creating new Lua files for debugging purposes is authorized as long as these are new files imported from in game scripts. In this case, you should put the files in the Game\data\lua\ folder to be able to import them. Using macro programs (like AutoHotKey) or similar hardware tools is authorized as long as you don’t automate gameplay. We consider gameplay as automated (and, thus, forbidden) when the macro or script:
- Takes decisions based on game feedback
- Executes actions for more than a few seconds
- Executes without any user input or when not actively playing the game.
For example, using a macro to keep a button pushed instead of maintaining it is authorized. But using a macro to send a message every hour is forbidden, especially if you are not even in front of your screen.  
What happens to cheaters ?
Our policy is to not issue automatic bans. There is always a human review when the anti-cheat system detects any unauthorized behaviour. Nonetheless, you may temporarily be kicked out of the game if the anti-cheat cannot initialize correctly. Sanctions include (at the discretion of the Novaquark team):
- Removing access to the game, temporarily or permanently (aka ban),
- In case of recurring offenses, the player may get a hardware ban (in this case, the player won’t be able to play the game with any current or future account, even if those accounts were never used for cheating).
- Plus any action required to revert any change made to the game world (removing Quantas or items, restoring constructs state, etc.).
- This list is not exhaustive and may be updated by Novaquark as the team sees fit.  
Why is it forbidden to modify Lua files or import custom DLL ?
 
We know some players or organizations have used local libraries (aka. DLLs) with great success and with good intentions. 
However, this option gives unfair advantages compared to pure in-game scripts (extra CPU capabilities, the ability to execute Internet requests or load/store data on the computer disk for example).
 
Moreover, we don't want players to massively share and use these custom libraries because it has severe security and privacy implications that we cannot control and we want to protect our players (for example, a player in an organization would need to install the organization library to use its scripts and constructs, but this library may as well read all his/her files without his/her knowledge nor consent on the disk, and send them to the author or do almost anything on the computer). Keep in mind that libraries could contain malware too. You don’t want that.
 
Finally, adding or modifying a DLL allows users to modify the game behavior in an arbitrary way, which directly leads to heavy cheating. For example, it allows access to the game’s memory and to escape the anti-cheat verification. We can't secure this at all, so player-made libraries are clearly a no-go security wise.
 
Therefore, after careful examination, we decided to forbid any modification to the game files. This restriction also includes the local Lua files as they contain security measures to ensure the game integrity and players privacy (for example, you could load a library by editing the global.lua file; this file is also responsible to make sure in-game scripts cannot read personal documents on your computer). The exception to this rule are files found in: "Game/data/lua" folder (this is the only location where you can add or modify files
 
Developers may still create new Lua files for debugging purposes if they want to (these files will be under control because global.lua is loaded first and sets up safeguards for any file loaded after itself).
 
 
Could player-made libraries be integrated after NQ’s validation ?
 
Having a process to submit, review, and integrate libraries looks good on the paper. However, code review is a tedious process. It is a lot harder than checking an image. There would be technical challenges to integrate them into the game too. Also note that we don't want to transform Lua scripts into full-fledged operating systems. They are simply supposed to be lightweight scripts, not full-fledged operating systems. ?️
 
Thus, we don't want to engage this process, at least in the near future. We simply don’t have the time or resources for this at the moment.
 
 
EQU8 is not compatible with Linux / consoles
 
Unfortunately, EQU8 does not work under Linux, even with Wine. This is due to the Windows functions it uses to protect the game’s integrity, which are different from other operating systems. This is a trade-off we had to make between having a fair game (without cheats) and compatibility.
 
Most players and games are on Windows. Thus, very few anti-cheat solutions support Linux (even less with good support). Because of this, we did not find an anticheat solution which works on Linux and suits our needs. However, please note that this decision doesn't prevent us from adding an alternative anti-cheat solution in the future, in case we decide to officially support Linux systems or consoles later on. Nothing prevents us from having a different anti-cheat for each platform. ?
 
We hope you found this FAQ about anti-cheats useful and helped to understand better why we chose EQU8.
 
Best Regards,
The Novaquark team
 
Last updated: October 5, 2020

Dear Alpha testers,
 
The Beta launch is coming in just a few weeks and as you might expect it, so is the pre-Beta wipe! You will have 2 last test sessions before the wipe, during which we ask you to save all the Constructs you want to keep under the form of a Blueprint. 
 
We know that this official announcement comes on short notice, but as you can imagine, the whole team is on a tight schedule to deliver the Beta at the end of the month and we’re trying to inform you as much in advance as possible with the time constraints.
 
The last test sessions before the wipe will occur will be:  
 
From Thursday, August 6th at 14:00 UTC
To Monday, August 10th at 14:00 UTC
  From Thursday, August 13th at 14:00 UTC
To Monday, August 17th at 14:00 UTC  
Remember, everything will be wiped following this session, except the normal blueprints located in your Player Inventory (Nanopack), so be sure to keep those previously on your character, and not anywhere else (like in a container).
 
Last but not least, we also want to apologize for the inconvenience regarding the very short notice about the extended PvP zone and the issues that may have resulted from the situation. However, if you’re in a situation where some of your Constructs have been damaged before you can make an up-to-date blueprint of the said Constructs, please contact our Customer Support as soon as possible so you can get help from our team before the next test session. If you’re in such a situation, please read carefully the process described in the previous announcement published here.
 
Best Regards,
The Novaquark team.
 
 

Hi everyone!
 
The new character model is an artistic re-imagining of the original design, and is one of many steps we’re taking to update the look and feel of the game. The goal of this redesign was not only to create something functional and realistic for interstellar travel, but also come up with something memorable, appealing, and instantly recognizable.
 
 
The Novaquark team.

if you have a second PC you can do that, but DU will not run 2 times on the same PC
play together with others and help make multiboxing useless
the challange is to find enough people to play with so you dont need to multibox
its much more effective than try to play DU two times or more at the same time...
Im just curious how this would look like in Star Citizen or Counter Strike xD
i really dont know why anyone would do that

Hello i'm Metis
 
old player of Mankind
 
i'm french and i hope dual universe is a great game.
 
 

Hi,
I'm old, I'm Bill and I'm from the UK. My philosophy in life has been finely honed over the years, it can be summed up as "Hope for intelligence, plan for incontinence". I've been around a few other MMOs etc. Notably Anarchy Online, LOTRO, NMS. This one sounds like it could be where I end up for the long haul. I look forward to meeting with many of you, hopefully not as a target in your crosshairs.

Congrats Yamamushi for joining the Novaquark team!  
If you want to join us in congratulating Yamamushi (and/or give your feedback on the Novaquark Employee Policy), you can post below in this topic!  
 
Best Regards,
Nyzaltar.

Bien le bonjour ! Ravie de découvrir DU  A+ in game