NQ-Nyzaltar

@iNFiDeL
@MopnexAndreyno
@vylqun
@PauMS0418
PTS starts with the live server database from a month ago.
If you started playing earlier than a month ago, you won't start from scratch.
The dev team may also give free resources when necessary, to test on a specific topic (more info in the official announcement below)
 
 
 
@Filokwarq2
PTS is currently opened and should stay open until tomorrow.
This is however a first load test, so the duration may be short for the first time and it will reopen later.
 
Best Regards,
Nyzaltar.

Calling all Noveans! 
 
We’re nearing the final stages of preparing the Dual Universe public test server (PTS) for its upcoming grand opening, and we need your help. 

If you are an active DU subscriber, please join us for a PTS load test. During this test, we will be gathering data related to server capacity and performance and trying out the new launcher. What’s more, you’ll be getting your first taste of the 0.24 build that’s currently in development. Your character and assets from the Live server will be mirrored on PTS. 
 
Your account login information will be the same for both the Live server and PTS; however, access to PTS requires downloading, installing and running a separate client, as well as the testing of the new launcher we’re rolling out with 0.24. 
 
Get the PTS client here. 
 
Feedback and bug reports related to PTS should be posted in this designated forum. 
 
Note that we anticipate that the performance won’t be smooth. They never are with these sorts of tests - and that’s a big part of what makes them important. 
 
It’s important to mention that PTS is solely for testing purposes. We’d like to manage expectations that PTS updates may include feature prototypes and gameplay changes that might not ever come to the Live server.
 
We understand that some players prefer a more stable and polished gameplay experience. Test servers aren’t everyone’s cup of tea. Updates will be unpolished. There will be no Customer Support. The server may be offline for extended periods, wiped or taken offline without advance notice. 
 
That being said, those who choose to brave the raw environment of the PTS will find there are certain advantages. Participation on PTS will give you the chance to help shape DU by sharing your insights and constructive criticism earlier in the development process. You’ll also get sneak peeks at content before it’s deployed on the Live server and impacts the persistent universe of DU. This will afford you the chance to formulate strategies for how to get the most out of upcoming changes. In addition, there may be times when we ease the experience by providing necessary equipment and resources on a discretionary basis. For example, if we need to test a new weapon, we may provide it for free to save PTS players the time and effort of creating it for themselves.                   
                                                                    
The Novaquark team hopes that many players will choose to help us test features on the PTS in the future, as it is one of the steps we are taking to further improve the quality of our releases, make sure our features are relevant, and overall have a development approach that further involves our community of players.
 
Best Regards,
The Novaquark Team
 

Dear Noveans,
 
With the opening of the Public Test Server (PTS) available to all DU players come a few guidelines, if you want to give some feedback.
We wanted - for a long time - to give the opportunity to anyone among you to give your opinion on features before they hit the Live Server.
However, as the time window to give feedback on new features deployed on the PTS will be usually limited, it's important to get structured feedback to be taken into account by the Devs, in order to make possible changes before deploying the said features on the Live Server. Note: having a new or modified feature deployed on the PTS doesn't necessarily mean that the same will be deployed on the Live Server. Community feedback may change the Dev Team course of action.
 
In order to facilitate the follow-up of your feedback by the Dev Team, it's really important to talk about one topic/feature per forum thread.
Additionally it's highly advised to follow the template below when giving feedback on a specific topic/feature deployed on the PTS:
 
Naming clearly the feature / game mechanics involved. Your feedback on the deployed feature (what you like / what you don't like about it (in this case, please give an explanation why you don't like it)). What kind of improvement you would see for such feature.  
If your feedback is about a bug report, please follow this template:
 
Subject: [BUG] <Issue name here> Current Version Number: <Can be seen when closing the client> Impact: <Game breaking / Crash / Corruption / Item/Data loss / Inconvenience / Cosmetic> Summary: <Short outline of the issue> Description: <Description of the issue> Reproduction: <Steps taken to make this bug happen>  
Reminder: there will be no official support for the PTS.
This means you can report bugs you found/experienced on the PTS (preferably in this forum section).
It's encouraged to report bugs found on the PTS, to make sure they won't be replicated once the involved feature will be deployed on the Live Server.
However, do not send tickets to the Customer Support to fix issues you encountered on the PTS.
Why no support? The reason is quite simple: in their experimental state, things may be broken.
The Novaquark Team prefer to allocate 100% of the Customer Support resources to the Live Server, where the "real game" happens.
 
We hope you'll understand our stance on the matter.
 
Best Regards,
The Novaquark Team.
 

Calling all Noveans! 
 
We’re nearing the final stages of preparing the Dual Universe public test server (PTS) for its upcoming grand opening, and we need your help. 

If you are an active DU subscriber, please join us for a PTS load test. During this test, we will be gathering data related to server capacity and performance and trying out the new launcher. What’s more, you’ll be getting your first taste of the 0.24 build that’s currently in development. Your character and assets from the Live server will be mirrored on PTS. 
 
Your account login information will be the same for both the Live server and PTS; however, access to PTS requires downloading, installing and running a separate client, as well as the testing of the new launcher we’re rolling out with 0.24. 
 
Get the PTS client here. 
 
Feedback and bug reports related to PTS should be posted in this designated forum. 
 
Note that we anticipate that the performance won’t be smooth. They never are with these sorts of tests - and that’s a big part of what makes them important. 
 
It’s important to mention that PTS is solely for testing purposes. We’d like to manage expectations that PTS updates may include feature prototypes and gameplay changes that might not ever come to the Live server.
 
We understand that some players prefer a more stable and polished gameplay experience. Test servers aren’t everyone’s cup of tea. Updates will be unpolished. There will be no Customer Support. The server may be offline for extended periods, wiped or taken offline without advance notice. 
 
That being said, those who choose to brave the raw environment of the PTS will find there are certain advantages. Participation on PTS will give you the chance to help shape DU by sharing your insights and constructive criticism earlier in the development process. You’ll also get sneak peeks at content before it’s deployed on the Live server and impacts the persistent universe of DU. This will afford you the chance to formulate strategies for how to get the most out of upcoming changes. In addition, there may be times when we ease the experience by providing necessary equipment and resources on a discretionary basis. For example, if we need to test a new weapon, we may provide it for free to save PTS players the time and effort of creating it for themselves.                   
                                                                    
The Novaquark team hopes that many players will choose to help us test features on the PTS in the future, as it is one of the steps we are taking to further improve the quality of our releases, make sure our features are relevant, and overall have a development approach that further involves our community of players.
 
Best Regards,
The Novaquark Team
 

Dear Noveans,
 
With the opening of the Public Test Server (PTS) available to all DU players come a few guidelines, if you want to give some feedback.
We wanted - for a long time - to give the opportunity to anyone among you to give your opinion on features before they hit the Live Server.
However, as the time window to give feedback on new features deployed on the PTS will be usually limited, it's important to get structured feedback to be taken into account by the Devs, in order to make possible changes before deploying the said features on the Live Server. Note: having a new or modified feature deployed on the PTS doesn't necessarily mean that the same will be deployed on the Live Server. Community feedback may change the Dev Team course of action.
 
In order to facilitate the follow-up of your feedback by the Dev Team, it's really important to talk about one topic/feature per forum thread.
Additionally it's highly advised to follow the template below when giving feedback on a specific topic/feature deployed on the PTS:
 
Naming clearly the feature / game mechanics involved. Your feedback on the deployed feature (what you like / what you don't like about it (in this case, please give an explanation why you don't like it)). What kind of improvement you would see for such feature.  
If your feedback is about a bug report, please follow this template:
 
Subject: [BUG] <Issue name here> Current Version Number: <Can be seen when closing the client> Impact: <Game breaking / Crash / Corruption / Item/Data loss / Inconvenience / Cosmetic> Summary: <Short outline of the issue> Description: <Description of the issue> Reproduction: <Steps taken to make this bug happen>  
Reminder: there will be no official support for the PTS.
This means you can report bugs you found/experienced on the PTS (preferably in this forum section).
It's encouraged to report bugs found on the PTS, to make sure they won't be replicated once the involved feature will be deployed on the Live Server.
However, do not send tickets to the Customer Support to fix issues you encountered on the PTS.
Why no support? The reason is quite simple: in their experimental state, things may be broken.
The Novaquark Team prefer to allocate 100% of the Customer Support resources to the Live Server, where the "real game" happens.
 
We hope you'll understand our stance on the matter.
 
Best Regards,
The Novaquark Team.
 

Dear Noveans,
 
With the opening of the Public Test Server (PTS) available to all DU players come a few guidelines, if you want to give some feedback.
We wanted - for a long time - to give the opportunity to anyone among you to give your opinion on features before they hit the Live Server.
However, as the time window to give feedback on new features deployed on the PTS will be usually limited, it's important to get structured feedback to be taken into account by the Devs, in order to make possible changes before deploying the said features on the Live Server. Note: having a new or modified feature deployed on the PTS doesn't necessarily mean that the same will be deployed on the Live Server. Community feedback may change the Dev Team course of action.
 
In order to facilitate the follow-up of your feedback by the Dev Team, it's really important to talk about one topic/feature per forum thread.
Additionally it's highly advised to follow the template below when giving feedback on a specific topic/feature deployed on the PTS:
 
Naming clearly the feature / game mechanics involved. Your feedback on the deployed feature (what you like / what you don't like about it (in this case, please give an explanation why you don't like it)). What kind of improvement you would see for such feature.  
If your feedback is about a bug report, please follow this template:
 
Subject: [BUG] <Issue name here> Current Version Number: <Can be seen when closing the client> Impact: <Game breaking / Crash / Corruption / Item/Data loss / Inconvenience / Cosmetic> Summary: <Short outline of the issue> Description: <Description of the issue> Reproduction: <Steps taken to make this bug happen>  
Reminder: there will be no official support for the PTS.
This means you can report bugs you found/experienced on the PTS (preferably in this forum section).
It's encouraged to report bugs found on the PTS, to make sure they won't be replicated once the involved feature will be deployed on the Live Server.
However, do not send tickets to the Customer Support to fix issues you encountered on the PTS.
Why no support? The reason is quite simple: in their experimental state, things may be broken.
The Novaquark Team prefer to allocate 100% of the Customer Support resources to the Live Server, where the "real game" happens.
 
We hope you'll understand our stance on the matter.
 
Best Regards,
The Novaquark Team.
 

Dear Noveans,
 
With the opening of the Public Test Server (PTS) available to all DU players come a few guidelines, if you want to give some feedback.
We wanted - for a long time - to give the opportunity to anyone among you to give your opinion on features before they hit the Live Server.
However, as the time window to give feedback on new features deployed on the PTS will be usually limited, it's important to get structured feedback to be taken into account by the Devs, in order to make possible changes before deploying the said features on the Live Server. Note: having a new or modified feature deployed on the PTS doesn't necessarily mean that the same will be deployed on the Live Server. Community feedback may change the Dev Team course of action.
 
In order to facilitate the follow-up of your feedback by the Dev Team, it's really important to talk about one topic/feature per forum thread.
Additionally it's highly advised to follow the template below when giving feedback on a specific topic/feature deployed on the PTS:
 
Naming clearly the feature / game mechanics involved. Your feedback on the deployed feature (what you like / what you don't like about it (in this case, please give an explanation why you don't like it)). What kind of improvement you would see for such feature.  
If your feedback is about a bug report, please follow this template:
 
Subject: [BUG] <Issue name here> Current Version Number: <Can be seen when closing the client> Impact: <Game breaking / Crash / Corruption / Item/Data loss / Inconvenience / Cosmetic> Summary: <Short outline of the issue> Description: <Description of the issue> Reproduction: <Steps taken to make this bug happen>  
Reminder: there will be no official support for the PTS.
This means you can report bugs you found/experienced on the PTS (preferably in this forum section).
It's encouraged to report bugs found on the PTS, to make sure they won't be replicated once the involved feature will be deployed on the Live Server.
However, do not send tickets to the Customer Support to fix issues you encountered on the PTS.
Why no support? The reason is quite simple: in their experimental state, things may be broken.
The Novaquark Team prefer to allocate 100% of the Customer Support resources to the Live Server, where the "real game" happens.
 
We hope you'll understand our stance on the matter.
 
Best Regards,
The Novaquark Team.
 

Dear Noveans,
 
With the opening of the Public Test Server (PTS) available to all DU players come a few guidelines, if you want to give some feedback.
We wanted - for a long time - to give the opportunity to anyone among you to give your opinion on features before they hit the Live Server.
However, as the time window to give feedback on new features deployed on the PTS will be usually limited, it's important to get structured feedback to be taken into account by the Devs, in order to make possible changes before deploying the said features on the Live Server. Note: having a new or modified feature deployed on the PTS doesn't necessarily mean that the same will be deployed on the Live Server. Community feedback may change the Dev Team course of action.
 
In order to facilitate the follow-up of your feedback by the Dev Team, it's really important to talk about one topic/feature per forum thread.
Additionally it's highly advised to follow the template below when giving feedback on a specific topic/feature deployed on the PTS:
 
Naming clearly the feature / game mechanics involved. Your feedback on the deployed feature (what you like / what you don't like about it (in this case, please give an explanation why you don't like it)). What kind of improvement you would see for such feature.  
If your feedback is about a bug report, please follow this template:
 
Subject: [BUG] <Issue name here> Current Version Number: <Can be seen when closing the client> Impact: <Game breaking / Crash / Corruption / Item/Data loss / Inconvenience / Cosmetic> Summary: <Short outline of the issue> Description: <Description of the issue> Reproduction: <Steps taken to make this bug happen>  
Reminder: there will be no official support for the PTS.
This means you can report bugs you found/experienced on the PTS (preferably in this forum section).
It's encouraged to report bugs found on the PTS, to make sure they won't be replicated once the involved feature will be deployed on the Live Server.
However, do not send tickets to the Customer Support to fix issues you encountered on the PTS.
Why no support? The reason is quite simple: in their experimental state, things may be broken.
The Novaquark Team prefer to allocate 100% of the Customer Support resources to the Live Server, where the "real game" happens.
 
We hope you'll understand our stance on the matter.
 
Best Regards,
The Novaquark Team.
 

Dear Noveans,
 
With the opening of the Public Test Server (PTS) available to all DU players come a few guidelines, if you want to give some feedback.
We wanted - for a long time - to give the opportunity to anyone among you to give your opinion on features before they hit the Live Server.
However, as the time window to give feedback on new features deployed on the PTS will be usually limited, it's important to get structured feedback to be taken into account by the Devs, in order to make possible changes before deploying the said features on the Live Server. Note: having a new or modified feature deployed on the PTS doesn't necessarily mean that the same will be deployed on the Live Server. Community feedback may change the Dev Team course of action.
 
In order to facilitate the follow-up of your feedback by the Dev Team, it's really important to talk about one topic/feature per forum thread.
Additionally it's highly advised to follow the template below when giving feedback on a specific topic/feature deployed on the PTS:
 
Naming clearly the feature / game mechanics involved. Your feedback on the deployed feature (what you like / what you don't like about it (in this case, please give an explanation why you don't like it)). What kind of improvement you would see for such feature.  
If your feedback is about a bug report, please follow this template:
 
Subject: [BUG] <Issue name here> Current Version Number: <Can be seen when closing the client> Impact: <Game breaking / Crash / Corruption / Item/Data loss / Inconvenience / Cosmetic> Summary: <Short outline of the issue> Description: <Description of the issue> Reproduction: <Steps taken to make this bug happen>  
Reminder: there will be no official support for the PTS.
This means you can report bugs you found/experienced on the PTS (preferably in this forum section).
It's encouraged to report bugs found on the PTS, to make sure they won't be replicated once the involved feature will be deployed on the Live Server.
However, do not send tickets to the Customer Support to fix issues you encountered on the PTS.
Why no support? The reason is quite simple: in their experimental state, things may be broken.
The Novaquark Team prefer to allocate 100% of the Customer Support resources to the Live Server, where the "real game" happens.
 
We hope you'll understand our stance on the matter.
 
Best Regards,
The Novaquark Team.
 

Dear Noveans,
 
With the opening of the Public Test Server (PTS) available to all DU players come a few guidelines, if you want to give some feedback.
We wanted - for a long time - to give the opportunity to anyone among you to give your opinion on features before they hit the Live Server.
However, as the time window to give feedback on new features deployed on the PTS will be usually limited, it's important to get structured feedback to be taken into account by the Devs, in order to make possible changes before deploying the said features on the Live Server. Note: having a new or modified feature deployed on the PTS doesn't necessarily mean that the same will be deployed on the Live Server. Community feedback may change the Dev Team course of action.
 
In order to facilitate the follow-up of your feedback by the Dev Team, it's really important to talk about one topic/feature per forum thread.
Additionally it's highly advised to follow the template below when giving feedback on a specific topic/feature deployed on the PTS:
 
Naming clearly the feature / game mechanics involved. Your feedback on the deployed feature (what you like / what you don't like about it (in this case, please give an explanation why you don't like it)). What kind of improvement you would see for such feature.  
If your feedback is about a bug report, please follow this template:
 
Subject: [BUG] <Issue name here> Current Version Number: <Can be seen when closing the client> Impact: <Game breaking / Crash / Corruption / Item/Data loss / Inconvenience / Cosmetic> Summary: <Short outline of the issue> Description: <Description of the issue> Reproduction: <Steps taken to make this bug happen>  
Reminder: there will be no official support for the PTS.
This means you can report bugs you found/experienced on the PTS (preferably in this forum section).
It's encouraged to report bugs found on the PTS, to make sure they won't be replicated once the involved feature will be deployed on the Live Server.
However, do not send tickets to the Customer Support to fix issues you encountered on the PTS.
Why no support? The reason is quite simple: in their experimental state, things may be broken.
The Novaquark Team prefer to allocate 100% of the Customer Support resources to the Live Server, where the "real game" happens.
 
We hope you'll understand our stance on the matter.
 
Best Regards,
The Novaquark Team.
 

Dear Noveans,
 
With the opening of the Public Test Server (PTS) available to all DU players come a few guidelines, if you want to give some feedback.
We wanted - for a long time - to give the opportunity to anyone among you to give your opinion on features before they hit the Live Server.
However, as the time window to give feedback on new features deployed on the PTS will be usually limited, it's important to get structured feedback to be taken into account by the Devs, in order to make possible changes before deploying the said features on the Live Server. Note: having a new or modified feature deployed on the PTS doesn't necessarily mean that the same will be deployed on the Live Server. Community feedback may change the Dev Team course of action.
 
In order to facilitate the follow-up of your feedback by the Dev Team, it's really important to talk about one topic/feature per forum thread.
Additionally it's highly advised to follow the template below when giving feedback on a specific topic/feature deployed on the PTS:
 
Naming clearly the feature / game mechanics involved. Your feedback on the deployed feature (what you like / what you don't like about it (in this case, please give an explanation why you don't like it)). What kind of improvement you would see for such feature.  
If your feedback is about a bug report, please follow this template:
 
Subject: [BUG] <Issue name here> Current Version Number: <Can be seen when closing the client> Impact: <Game breaking / Crash / Corruption / Item/Data loss / Inconvenience / Cosmetic> Summary: <Short outline of the issue> Description: <Description of the issue> Reproduction: <Steps taken to make this bug happen>  
Reminder: there will be no official support for the PTS.
This means you can report bugs you found/experienced on the PTS (preferably in this forum section).
It's encouraged to report bugs found on the PTS, to make sure they won't be replicated once the involved feature will be deployed on the Live Server.
However, do not send tickets to the Customer Support to fix issues you encountered on the PTS.
Why no support? The reason is quite simple: in their experimental state, things may be broken.
The Novaquark Team prefer to allocate 100% of the Customer Support resources to the Live Server, where the "real game" happens.
 
We hope you'll understand our stance on the matter.
 
Best Regards,
The Novaquark Team.
 

Dear Noveans,
 
With the opening of the Public Test Server (PTS) available to all DU players come a few guidelines, if you want to give some feedback.
We wanted - for a long time - to give the opportunity to anyone among you to give your opinion on features before they hit the Live Server.
However, as the time window to give feedback on new features deployed on the PTS will be usually limited, it's important to get structured feedback to be taken into account by the Devs, in order to make possible changes before deploying the said features on the Live Server. Note: having a new or modified feature deployed on the PTS doesn't necessarily mean that the same will be deployed on the Live Server. Community feedback may change the Dev Team course of action.
 
In order to facilitate the follow-up of your feedback by the Dev Team, it's really important to talk about one topic/feature per forum thread.
Additionally it's highly advised to follow the template below when giving feedback on a specific topic/feature deployed on the PTS:
 
Naming clearly the feature / game mechanics involved. Your feedback on the deployed feature (what you like / what you don't like about it (in this case, please give an explanation why you don't like it)). What kind of improvement you would see for such feature.  
If your feedback is about a bug report, please follow this template:
 
Subject: [BUG] <Issue name here> Current Version Number: <Can be seen when closing the client> Impact: <Game breaking / Crash / Corruption / Item/Data loss / Inconvenience / Cosmetic> Summary: <Short outline of the issue> Description: <Description of the issue> Reproduction: <Steps taken to make this bug happen>  
Reminder: there will be no official support for the PTS.
This means you can report bugs you found/experienced on the PTS (preferably in this forum section).
It's encouraged to report bugs found on the PTS, to make sure they won't be replicated once the involved feature will be deployed on the Live Server.
However, do not send tickets to the Customer Support to fix issues you encountered on the PTS.
Why no support? The reason is quite simple: in their experimental state, things may be broken.
The Novaquark Team prefer to allocate 100% of the Customer Support resources to the Live Server, where the "real game" happens.
 
We hope you'll understand our stance on the matter.
 
Best Regards,
The Novaquark Team.
 

Dear Noveans,
 
With the opening of the Public Test Server (PTS) available to all DU players come a few guidelines, if you want to give some feedback.
We wanted - for a long time - to give the opportunity to anyone among you to give your opinion on features before they hit the Live Server.
However, as the time window to give feedback on new features deployed on the PTS will be usually limited, it's important to get structured feedback to be taken into account by the Devs, in order to make possible changes before deploying the said features on the Live Server. Note: having a new or modified feature deployed on the PTS doesn't necessarily mean that the same will be deployed on the Live Server. Community feedback may change the Dev Team course of action.
 
In order to facilitate the follow-up of your feedback by the Dev Team, it's really important to talk about one topic/feature per forum thread.
Additionally it's highly advised to follow the template below when giving feedback on a specific topic/feature deployed on the PTS:
 
Naming clearly the feature / game mechanics involved. Your feedback on the deployed feature (what you like / what you don't like about it (in this case, please give an explanation why you don't like it)). What kind of improvement you would see for such feature.  
If your feedback is about a bug report, please follow this template:
 
Subject: [BUG] <Issue name here> Current Version Number: <Can be seen when closing the client> Impact: <Game breaking / Crash / Corruption / Item/Data loss / Inconvenience / Cosmetic> Summary: <Short outline of the issue> Description: <Description of the issue> Reproduction: <Steps taken to make this bug happen>  
Reminder: there will be no official support for the PTS.
This means you can report bugs you found/experienced on the PTS (preferably in this forum section).
It's encouraged to report bugs found on the PTS, to make sure they won't be replicated once the involved feature will be deployed on the Live Server.
However, do not send tickets to the Customer Support to fix issues you encountered on the PTS.
Why no support? The reason is quite simple: in their experimental state, things may be broken.
The Novaquark Team prefer to allocate 100% of the Customer Support resources to the Live Server, where the "real game" happens.
 
We hope you'll understand our stance on the matter.
 
Best Regards,
The Novaquark Team.
 

Before starting to read the Lore Bible, here are three things to keep in mind:
 
- Some names and acronyms (put between brackets) in the texts below are still temporary names/placeholders. The final names will be decided in the following days. The update will be announced on the forum and on the social media. We don't want to keep these names, for different reasons varying for each case. Once in its final version, it will be published on the Community Wiki hosted by Gamepedia in a more structured way.
 
- It was a difficult decision but we have to consider that some parts of the short story written by Alain Damasio will be modified or removed. We all agree in the team that Alain Damasio has made a short story of the highest quality, but this short story was written more than a year ago (July 2015) and at that time, too many points regarding the game universe were unclear or undecided. With all the recent additions to the Lore Bible (those released today publicly and those which remain hidden as "secrets" for the time being), it generated some inconsistencies difficult to solve. We tried to find solutions or workarounds, without success. Some points were also not possible to represent in-game, gameplay wise. While the short story will be updated in the near future to fit with the current Lore Bible, in the meantime here are the specific points from the short story you should not take into account when writing a Fan Fiction for Dual Universe (if you want it to be eligible for being integrated to the official backstory of the game, of course. If not, you are not bind to such limitation).
Unfortunately, Sohan Decker is not a member of the Alpha Team, as he woke up just a few weeks before the Arkship landing on Alioth and do not participate in the neural simulation that will take place more than a year and a half before the landing. Aphelia memory must have had a glitch when talking to Sohan for the first time. When approaching some Kyrium, the matter doesn't reflect human faces aging or growing younger. Sohan Decker has probably some hallucinations, a possible side-effect of the long cryogenic sleep. While probably convinced of it, Sohan Decker didn't communicate with an invisible entity by using elements and he didn't get some schematics of a high-performance reactor in Kyrium as a reward. The proof? When asked to show it, he's not able to find it anywhere! Poor Sohan. Probably another hallucination. Cryogenic sleep seems to have a lasting side effect on him.  
- The Novaquark might slightly change the Lore Bible over time, but we will try to keep those changes to a minimum, to ensure that it doesn't contradict fanfictions that have been already integrated to the official lore. These changes will occur mainly when an inconstancy is discovered in the official lore. And in this regard, we count on your feedback to track down every little detail that might seem inconsistent (some details may be awkward on purpose though ). As always, we remain open to your feedback on the Official Lore. Let us know what you think about it!
 
That being said... Happy reading!
 
 
  Dual Universe Lore     Dual Universe takes place about 10.000 years after the Grand Exodus when humanity left the Earth to establish itself in new star systems. The information below is meant to help answer the most common questions about the game environment and try to set the general framework where fan fiction can be written.     Main historical dates     2027: Discovery of the doomsday Neutron Star that is heading towards the Earth. Collision will happen in 498 years. There are margins of error, so we don’t yet know if it means annihilation or simply major disruption in the solar system’s planets, but the end result is the same: the Earth will not be able to host humanity anymore. The event is nicknamed the [“Star Kiss of Death”], or [SKiD]. It’s basically the Armageddon.   2049: Creation of the United Earth Federation (UEF), a transnational institution in charge of coordinating humanity’s efforts and response to the SKiD. After concluding there was no hope to save Earth, the “Rebirth Program” is launched to analyze possible responses and escape strategies. New measures are voted to encourage natality in the population, to fight against a nihilist movement that advocates a “no future” philosophy and maintain a sufficient level of humans in the long run to fuel the Rebirth Project’s considerable needs.   2084: Better measurements have narrowed the margin of error. We are now certain that the neutron star will hit our solar system, and will actually collide with the Sun, turning into a black hole that will ultimately swallow or eject into deep space all the planets, Earth included. There is no hope anymore. Major funding is directed towards the Rebirth Program. All nation states must contribute at least 20% of their resources   2100: Mankind is entering a new era where robotics and AI have profoundly transformed society. Work as we know it has long disappeared, and social influence has replaced money as the currency of value. People do not “work” anymore, they have “activities” that can get them socially recognized. Money is still used, via a Universal Revenue, mainly as a way to control the scarcity in production, and balance the availability of goods against their rarity.   2130: AI have reached a threshold of global sentience. It is active in political, economic and social debates, and, while its benefits are recognized because it allowed the transition to the post-work era, more and more concern is raised about the sentient aspect and the potentially uncontrollable dimension of the AI agenda. Irrational fear rises. The AIs try to reassure the population that they have no rational reason to threaten humanity, but it only increases the level of suspicion within society.   2145: Massive rebellions all around the world signals the end of sentient AI, introducing a permanent universal ban on this technology, enforced by the very powerful UEF. Against all expectations, sentient AIs accept this and willingly shut down without any form of violent action.   2150: Society is reorganizing itself, as many “jobs” that needed sentient-level AI (surprisingly many, including low skill manual work), are once again left to humans to perform. Robots, in general, are banned also, as most of them required sentient-level AI to function properly. Early attempts at designing automated non-sentient robots all failed in the late 21st century, as it was discovered that sentience was a necessary byproduct of any sufficiently sophisticated AI for it to be able to interact with a complex world.   2200: A major summit of the UEF signals the alarming lack of progress on project Rebirth at the dawn of the 23rd century. Debates continue for years afterward about priorities, what technology to use to build Arkships that could help evacuate Earth, who would be eligible if we cannot host the 3 billion people still in the current population.   2200-2400: Major political events keep slowing down humanity and the UEF in its attempts to advance the technologies needed to build functional Arkships. Many wars, economic crisis, and nihilist terrorism are plaguing the progress.     2400: A period of calm and peace opens up. Major progress is suddenly made in the technologies needed to build the Arkships. Some are scheduled to be built within the next decade.   2440: Several key technologies are unlocked: cryosleep modules, nanoforming technology, nanopack condensers, resurrection nodes (it is unfortunately too late to use this to save humanity, as we would need to install billions of them out of the solar system, on a hospitable planet. There is not enough time for this).   2450: The Arkship technology is now mastered. Mass production begins. The race is on to produce as many as possible.   2500: Terrifying high-resolution images of the neutron star are provided by our most powerful telescopes. Riots break out all around the world over the selection process that dictates who gets to board the Arkships. The process was created by a scientific committee from the UEF, aimed at gathering the maximal amount of genetic diversity, plus a lottery to offset the fact that not everybody could go. Massive euthanasia programs were organized for those who had to stay, in order to provide them with a painless death at the time of their choosing.   2510-2536: The first Arkships leave Earth. Each Arkship is heading towards a particular part of the galaxy. One of them, the Novark, is heading towards the Scutum-Centaurus arm.   2538: The neutron star annihilates the solar system. Arkships are on their way, heading towards different regions of the galaxy.   12477: The Novark arrives on Alioth with a mighty thud as it deploys itself into the planet surface. From afar the planet shows many similarities to that of Earth, a blue and green marble sitting in the goldilocks zone of its star. Large continents surrounded by equally large oceans define the planet's appearance. Mountain ranges suggest continental drift, and large forests have taken hold over most of the planet. Primitive lifeforms are abundant. There are no obvious signs of advanced lifeforms.   Year 0 after arrival (0 AA): It will be your turn to write History in-game.     The world in 2500     In the century that preceded the Grand Exodus, the Earth’s population had dropped considerably, down to something less than 1 billion people. The “no future” movement had gained a considerable momentum. people were simply trying to tend to their immediate needs; losing any vision for the future or any concern for the consequences of their actions. Natality had dropped to an all-time low, crime had been continuously rising, and nation-states, as we know them, had long disappeared.    The UEF was the last large-scale social structure still holding, among a myriad of medium to small sized city-states. UEF representatives and offices, research centers, production units, etc, were scattered all around the world within the largest city-states. The UEF’s role now extended far beyond its initial goals, including a feared and powerful armed force to maintain order and ensure that the proper funding was collected from all city-states, in order to fuel the Rebirth Program.   A global language shared by all people on the planet started to emerge at the end of the 21st century. By the end of the 22nd century, almost everyone was speaking at least two languages: the global language (the “common”) and their local native language, each city-state having somehow evolved a variant from their original country’s language.     Economy     During the first half of the 21st century, the Internet quickly decentralized the economy, removing intermediaries and frictions. Anyone was able to open their own marketplace online, with powerful central aggregators to help integrate available offers. This was both true of goods and services. This highly distributed model of economy stood the test of time, both during the sentient AI era, and even after, up until the last century.   One of the main challenges of the last century, after the city-states model had become the norm, was logistics. Transporting goods over long distances carried the risk of being attacked by pirate hordes living outside of the city-states. The UEF and other independent security groups were in charge of ensuring protection, but still, the risk made inter-city trade dangerous, and local markets were the preferred method for basic commerce.   A global currency, the [U2] [(Universal Unit)], is installed by the UEF at the beginning of the 22nd century. It has acquired a growing support over the years and is still used as a reference currency on Alioth to help organize the exchanges of goods and services between colonists.     Culture & Society     At the moment of the Grand Exodus, humanity, and more precisely the UEF, was divided into four main political movements, essentially different from each other in the way they decided to answer one simple fundamental question: what is the main driving force in the development of humanity? Behind this question lies the promise of a political agenda on how to best rebuild civilization after the Grand Exodus and where to put priorities.   The [Luminous] are the first group. They consider the main driving force to be knowledge and wisdom. They value science, industry, and technology as the main sources of progress, and were heavily involved in the Rebirth Program, which led to the construction of the Arkships. They are, of course, very much respected for this even if some may criticize them for their all too rational take on things.   The Alphas are the second group. For them, the main driving force is, well, … force. They believe that people will respond mostly to strength and balance of power. They favor military action as a way to control and orient the evolution of the world in an attempt to avoid chaos and prevent instability. Their intentions are good, but they often fall to scandals involved with their expeditious way of handling subtle situations.   The [Ethereans] constitute the third group. They believe in the power of culture and arts. For them, humanity needs to be driven by dreams, beauty, and ideals before anything else. This is what gives us meaning. They are not against more practical endeavors but like to see these activities as a way to expand and support their vision. They have many supporters but are also often criticized for their lack of pragmatic action.   The [Emporium] is the final group. They believe in the power of money and commerce. They think that this has been the life and blood of human societies for millennia and, even if they will gladly regret it in private, they think this is nevertheless what gets the job done and can really set people in motion. Some point to them as a cause of an ever greater inequality, but they know how to silence critics and make people happy.   None of these movements are inherently good or bad, they all value human life and sincerely want to help drive humanity to success again.     Science & Technology     After the early 2400 years, science and technology suddenly advanced very rapidly. Incredible innovation occurred, becoming the foundation of the industrial, societal and economical program of Project Rebirth. Here are some of the most prominent breakthrough:   Nano fields: an expected advance in theoretical physics led to the discovery of a new force in nature, called the nano force due to its scale, that allows the fine control of the molecular dynamics of matter with incredible precision using high-frequency nano fields. Nano fields can be focused and modulated in a very precise way to destructure, collect or deploy and assemble matter in a short range radius. This is the core technology that gave birth to the nanoformer that every colonist is now equipped with.   Calabi-Yau Compactification: the science behind CYC has been inexplicably lost in the Arkship archives. It is the technology that powers nanopacks, which are extra small containers (that colonists wear on their suit), capable of amazing volume and weight reductions of almost anything contained in them. All we know is that it seems to work based on the possibility of storing matter within the extra dimensions of space-time allowed by String Theory, inside what is called the Calabi-Yau space. The exact science and understanding behind them have been lost and attempts at reverse engineering have all failed. Due to the limited number of Nanopacks available and their considerable value, further attempts to reverse engineer them are discouraged.   Nano fields displacement: this is a direct application of nano fields, used to collect, store and maintain matter within containers. The matter constituting objects is analyzed and de-structured first then stored using stable nano fields and can then be retrieved later via a reverse process that reconstructs the original object. Unlike with CYC, only limited volume gain can be obtained, and no weight reduction is possible.   Nano 3D printing: based again on the versatile nano fields, advanced 3D printers became possible. They are capable to assemble matter from reservoir sources to build small sized technological parts; from electronic to industrial units. Coupled to the automated assembly, this quickly became the basis of the industrial chain.   Quantum branching: Quantum Branching is at the heart of the Resurrection Node technology and is based on the “Many Worlds Interpretation” of quantum mechanics. At any moment, in particular, when you die violently, several versions of the universe coexist in parallel. Scientists working on EPR pair experiments unexpectedly found a way to instantly switch one universe with another, and in particular to switch the universe where you die with another one where everything would be exactly the same, except that your body position would be inside a Resurrection Node. The amount of matter to switch increases the energy cost of the operation, so RN teleport only the minimal set of mass to get the desired effect, which is... your naked body. A Resurrection Node is paired with your body and cannot be used by somebody else. It will make you virtually immortal, even if natural aging will probably get you out of the loop at some point.   Propulsion Engines: the conquest and exploration of the arrival star system, as well as nearby other stars, is a clear objective of the UEF for each arkship colony. Several engine technologies have been perfected as part of the Rebirth Program to allow for various flight modes, either within the atmosphere or in space. Warp drive technology was near completion and should become available a few years after the arrival, and even stargate instant transport has been sketched as a not too distant possibility but was unfortunately still not available at the time of the Grand Exodus. Warp drive speed is believed to be in the range of 100 times the speed of light, while super warp probes, that could be used to seed stargates, could reach up to 10.000 times the speed of light Making it possible to cross the entire galaxy in just 10 years.      Environment & Alioth     Alioth is a rocky planet orbiting a yellow dwarf star, very similar to the Sun. It has been selected due to its very similar Earth-like environment, including oceans, forests, mountains, and lakes. It has a moderate fauna and flora. The temperature during the day is similar to what can be found on Earth, but nights can be extremely cold.   The planet underground contains all the usual materials needed for basic industry, but more rare resources may have to be later harvested from one of Alioth’s three moons, or even from more distant planets in the system.   The planet day/night cycle is only 5 hours, and its weather pattern is relatively stable. Overall, Alioth is a very life-friendly planet, carefully chosen to facilitate the starting years of colonists.     The Arkship     The Arkships are a marvel of technology. They can host millions of people in cryosleep for extended periods of time. Made out of Kyrium, they can sustain incredible amounts of deceleration or acceleration, and absorb the corresponding crushing forces for whatever stand inside them. The origin of Kyrium is not well documented, and it seems that the material cannot be produced from a known industrial process, but has probably been found during some mining operations within the solar system.   Designed to travel close to the speed of light for extended periods, the Arkship engines are also not part of the colonist UEF documentation and no assembly schema could be found within the archives. There is much debate over why the UEF would intentionally withdraw such potentially useful information.    Each Arkship is controlled by a proto-sentient AI that was allowed to be built against the very strong UEF AI ban because it was argued that it would have been to hazardous to let the fate of humanity rest with dumb automatic machinery that would possibly not be able to react to unexpected situations. While being an exception to the AI ban rule, the onboard AI is still however not allowed to take control of any machinery or robot beside the Arkship itself. The Novark AI is called “Aphelia”.   Once on approach to the destination planet, the Arkship is designed to literally “plant” itself into the planet, to allow the deployment of deep geothermal energy collectors that should sustain the ship functions for potentially unlimited amounts of time. One of the key functions of the ship once arrived, is to deploy a 20km radius safe zone area where colonist would be free from any form of aggression from the outside, or… from themselves. It was indeed decided that the potentially violent nature of mankind under stressful situations should be mitigated with appropriate supervision. Within the safe zone, Aphelia is in charge of maintaining order and providing support and information to colonists.   Regrettably, one known consequence of prolonged cryosleep periods is that the subject will suffer from a loss of episodic memory, as well as most high-level cognitive memory like expertise, skills or know-how. To mitigate this side-effect, the Arkship archive contains large data banks that are transferable to colonists via a wireless data transfer process involving brain implants capable of stimulating neural activity. The process is slow and can take days for the most advanced skills, but is an effective way to re-enable lost knowledge for long time space travelers.   The Arkship extreme energy efficiency, designed to allow the ship to travel for millennia, forced trade-offs on what could be embarked in order to minimize the total mass, and of course, human bodies were preferred over any other “mass”. For this reason, and because nano 3D printing would make it possible to easily rebuild them, no ship or industrial machine was included inside the Arkships’ cargo. Humanity would have to rebuild civilization from scratch. A large set of Resurrection Nodes tuned to each registered colonist where however installed inside the Arkship to avoid any loss of precious life once arrived on the destination planet. For these reasons, the inside of the Arkship, besides the propulsion machinery, is mostly occupied by cryosleep pods, as well as Resurrection Nodes.     Alpha Team     While most of the Arkship passengers will wake up after the Arkship landing, a few thousand among them become half awakened between a few years and a few weeks before the arrival: the Alpha Team. While their bodies are still asleep, their brains are awakened and connected to an advanced neural/computer network that immerses them collectively within a virtual reality that is meant to simulate their first steps on the destination planet, for education and testing purposes.   During this simulation, of course, nobody can die (this represents the Alpha phase in-game). They are given easier access to certain resources in order to help them experience various stages of the tasks they will have to face in real life when arrived. The Alpha Team will then be in charge of guiding newcomers and helping to bootstrap the first months of civilization rebuilding on the destination planet.     Mysteries     The cryosleep memory loss side effect and the apparently incomplete archive has given birth to several mysteries for which colonists have developed many “theories”:   Kyrium is an absolute mystery. Nothing is available in the Arkship archives about its nature, how it was found, how to create it or even manipulate it. No colonist have the slightest memory about the Kyrium. If Aphelia is asked for information on Kyrium, the Novark’s AI will just give an elusive answer, explaining its lack of information as memory loss. Obviously, this is not a satisfying answer.
  Aphelia is in charge of the Novark and the well-being of all the passengers. She seems as caring as invasive in the private life of the colonists. While she doesn’t seem brutal, hostile or coercive by default, her behavior is perceived as if she monitors every action of each human that has been aboard the Novark. She also seems to avoid disclosing information on some specific topics - at least that’s the feeling of some passengers - despite the fact she always says if she doesn’t give a satisfying answer, it’s because the answer is beyond its capabilities. For these two reasons, many colonists think the AI is not trustworthy. Aphelia seems to have incredible defenses against hacking, far higher than anything the most experienced colonists in hacking have ever seen, reinforcing the feeling that the AI might hide a lot of things. The Arkship light speed engine is completely undocumented. No schema is available to rebuild one using 3D nano-printing, or by any other means.
  There seems to be no trace of the records pointing to the destination of the other Arkships within the galaxy.  
 
 
Best Regards,
The Novaquark Team

Chers Novéens,
 
Bien que nous ayons fait peu de communication jusqu’ici dans la langue de Molière, cela ne nous a pas empêché d’écouter vos demandes de voir le jeu entièrement traduit en français, de même que les annonces, les nouvelles ou même simplement les interactions entre l’équipe Novaquark et la communauté francophone.
 
Certains parmi vous savent déjà que si cela ne s’est pas fait plus tôt, ce n’est pas par manque d’envie de notre part - surtout pour un studio d’origine française - mais plus pour des questions d’effectifs. Nous devions faire un choix entre communiquer dans une langue où une majorité de joueurs au niveau international pourraient comprendre nos communiqués, ou choisir de communiquer dans notre langue d’origine, mais toucher beaucoup moins de joueurs d’emblée, ce qui aurait rendu les choses beaucoup plus compliquées pour développer le jeu à l’international par la suite.
 
Aujourd’hui, ce choix difficile que nous avons dû faire est en train de s’estomper, avec l’arrivée de NQ-Nishtar, qui se consacrera principalement aux interactions avec la communauté francophone! Nous comptons sur vous pour lui faire bon accueil !
 
L’équipe communautaire Novaquark.

Chers Novéens,
 
Bien que nous ayons fait peu de communication jusqu’ici dans la langue de Molière, cela ne nous a pas empêché d’écouter vos demandes de voir le jeu entièrement traduit en français, de même que les annonces, les nouvelles ou même simplement les interactions entre l’équipe Novaquark et la communauté francophone.
 
Certains parmi vous savent déjà que si cela ne s’est pas fait plus tôt, ce n’est pas par manque d’envie de notre part - surtout pour un studio d’origine française - mais plus pour des questions d’effectifs. Nous devions faire un choix entre communiquer dans une langue où une majorité de joueurs au niveau international pourraient comprendre nos communiqués, ou choisir de communiquer dans notre langue d’origine, mais toucher beaucoup moins de joueurs d’emblée, ce qui aurait rendu les choses beaucoup plus compliquées pour développer le jeu à l’international par la suite.
 
Aujourd’hui, ce choix difficile que nous avons dû faire est en train de s’estomper, avec l’arrivée de NQ-Nishtar, qui se consacrera principalement aux interactions avec la communauté francophone! Nous comptons sur vous pour lui faire bon accueil !
 
L’équipe communautaire Novaquark.

Hi everyone.
 
Until now, we couldn’t manually manage (remove/promote) Legates in an organization easily on the administration side.
Since Yesterday, we are able to use a feature simplifying considerably the process. 
 
As we already mentioned many times in the past, we (Novaquark) don’t want to involve ourselves in the management of organizations created by players. However, we are also aware that the current (and temporary) state of the management system contains obvious flaws. You know it. We know it. As this is still “work in progress”, we hoped that organizations creators will be reasonable enough to avoid abusing the well-known flaws of the system and would wait that all the rules are implemented before trying to sabotage other organizations. 
 
So we are going to state the obvious here:
It’s ok to “play a bad guy” and use dirty tricks once all the rules are implemented. However, it’s absolutely not ok to start exploiting the flaws of a work in progress system: this is not “playing a bad guy”, this is just toxic behavior and trying to gain an advantage while not playing by the rules.
 
That’s why - despite our will of non-involvement - we will make exceptions until the full implementation of the RDMS (Rights & Duties Management System) for the Organizations.
 
Why did we decide to intervene? 
Two reasons:
1) In the current state, a Legate has much more power than in the final system, due to the minimalistic mechanisms temporarily in place. If in the current system, any Legate has the right to promote a member to Legate status by himself alone, in the final system the default rights will be completely different: promoting a legate will be done only with a vote by majority rule, or the right to promote someone will be given to specific persons and not every Legate.
2) In the current state, a Legate cannot be demoted by any mean (even by the creator of an organization). In the final system, default configurations will allow to demote a Legate with a vote by majority rule. A Legate could also be demoted by specific persons who have been given the right (most probably by the Organization founder) to do so.
 
How is this going to work?
Each organization is going to have one "wild card": if there is a problem with the Legates in an Organization, you can contact the support team at support@novaquark. However, keep in mind we (Novaquark) reserve the right to intervene (or not) on a case by case basis. 
 
Example of a case where we will intervene:
Some Legate using the flaw of the current temporary system to vandalize (or generate troubles in) an organization.
 
Example of a case where we won’t intervene:
Two organizations have merged in one, and now both creators of previous organizations want to mutually exclude each other from the organization. In this kind of case, we won’t remove anyone. We won’t favorize one creator above another. However, we will do our best to help finding a satisfying solution for both parties.
 
As a global reminder:
If someone finds a loophole in the rules in place (that may happen), and this loophole is used to generate trouble and spread a toxic behavior, we won’t stay idle watching the situation deteriorating. 
 
Best Regards,
Nyzaltar.

We want this forum to be a place where everyone feels empowered to have an open and friendly discussion with us (the Novaquark team) as well as other community members.  To help make this possible we have created rules we feel will keep things positive and ensure that proper netiquette is observed.

By posting on this forum, either publicly or through private message or other means, you explicitly agree to follow the rules and guidelines posted here. If you do not agree with these rules – in whole or in any part – then do not post. All members will be treated as if they have read and understood these rules and guidelines.
 
(I) Be respectful and courteous.
The Dual Universe forums and community site are provided for Dual Universe players and those interested in discussing topics directly related to Dual Universe. We understand that community members may disagree with each other, and even with us, but we expect opinions to be expressed in a reasonable and polite manner.  It is important to maintain an atmosphere of civility and respect, so that all voices may be heard.
 
(II) Communicate constructively.
All communication, whether between players, moderators or Dual Universe staff, must be constructive. Posts without constructive commentary can distract from the topic at hand, reduce the visibility of valuable communication, and discourage others from participating in the conversation.
 
(III) Following actions are prohibited:
Posting off-topic replies or replies that are likely to drag the discussion off topic. Necroposting on old threads (unpinned threads in which the last reply is older than 2 months). Spamming on a specific topic. This includes creating multiple discussions on the same topic in the same or multiple forums. Cross-posting a specific reply. This is also a form of spamming. Posting an image without a meaningful text. A meme is not a response to a discussion. They are usually disruptive and can be easily misinterpreted. The same is true for animated GIFs. Calling out other players or community members by name to shame them for actions or opinions you may disagree with. Naming and shaming is not tolerated. Posting in any manner that disrupts an official thread. Official threads are topics created by the Novaquark team for the purpose of collecting feedback and opinions. Threatening legal action. Unfortunately, this kills all conversation immediately as we must refer all further discussion to our legal team. To preserve the conversation intact and unaltered these types of responses may be immediately archived. Trolling (provoking) people. Flaming (insulting, attacking) people. Picking fights isn’t a good way to make your point. It usually means you don’t have one and are just trying to cause trouble. Using profanity. Including creative spelling or character substitution to bypass word filters. Using the report system in an abusive manner. This is a form of harassment and a tremendous waste of time for both staff and moderators. Discussions and comments involving real life politics, ideology or religion. These can be incendiary topics and will usually lead to inappropriate behavior and uncomfortable situations. Publicly posting any private discussions, conversations, or other material between a user and a Novaquark employee (confidentiality policy). Refusal to follow the directions of Novaquark staff or representatives.
The use of an alternate account to circumvent a forum suspension is forbidden at all times. Additionally, the use of alternate account(s) to influence or misrepresent opinions is strictly prohibited. All forum accounts must adhere to the forum rules and Code of Conduct. Failure to comply can result in disciplinary actions against all associated accounts.
 
Violating these guidelines may trigger a warning, followed by either a temporary or permanent suspension of forum privileges depending on the severity and frequency of the violations.
 
(IV) The following actions may result in the immediate suspension of forum privileges:
There are some actions severe enough to result in immediate temporary or permanent suspension of posting privileges without prior notification. Serious or sustained offenses may result in suspension of not only the user's forum account but game account as well.
 
Threatening other members or Novaquark staff. No, “just joking’ is not a defense. We take this very seriously. Publicly revealing account or personal information of any person, community member or Novaquark staff. Posting harmful links pointing to viruses, malware, worms or trojans. Posting sexually explicit content. Including posting links to such content. Hate speech is not tolerated in any form. Attacking any ethnic group, religion, gender or sexual preference/identity. Promoting exploits, cheating programs, piracy or any sort of illegal activity. Attempt to impersonate Novaquark staff or another member of the community.  
Violations of these rules may result in further steps taken with outside authorities or agencies. This may include your Internet Service Provider (ISP) and local or national Law Enforcement agencies.
 
(V) Abide by moderators and Novaquark employee’s instructions.
 
If you disagree with a moderator or employee's actions, do not discuss or challenge the matter in forum posts. Send an e-mail to forum@novaquark.com, and be sure to include your forum handle (name displayed on the forum), but NOT your password, and clearly state your concerns.
 
IMPORTANT: Forum content is moderated at Novaquark's sole discretion, and content may be modified, removed, or otherwise restricted by Novaquark employees and/or moderators.
 
Best Regards,
The Novaquark Team.

I) About Dual Universe (and/or a DU Organization) Advertisement
 
(a) It's fine to advertise the game and/or your DU Organization(s) to players you already know or with whom you have already played with in other games without harassing them. If they aren't interested, do not insist.
 
(b) It's absolutely not acceptable to enter other gaming communities with the only intent being to randomly advertise Dual Universe or your DU Organization to players you don't know. Being polite isn't enough. Participating in said group with the intention to legitimize your advertisement is not enough either. You won't fool many people with this method. While one player may be convinced to join your Organization, it will most likely antagonize significantly more players, making them hostile toward you and Dual Universe due to these cheap and inappropriate practices. 
 
If you don't understand why this is wrong, just imagine players coming from 10 different game communities and invading your Discord, subReddit, or Steam group, falsely pretending to be interested in the game you’re playing while instead being there to make advertisements for the game he plays in your channels. Any person would quickly be tired of this behavior and ban them all, as well as form a negative image of the game that has been advertised. Please don’t do this.  Not only is this rude, this can be considered harassment in addition to brand damage, which could result in a ban from Dual Universe for such behavior.
 
(c) While it didn’t seem clear for everyone so far (despite being in our EULA and in our forum chart here), here is a strong reminder: impersonating Novaquark staff is a serious offense. This will result in a permanent ban without further notice or discussion. There is also no limitation period for this offense (meaning: if we got proof of Novaquark staff impersonation several months or even years later, the sanction will still be applied).
 
(d) While this has been some kind of grey area until now, there won’t be sanctions applied to involved Organizations for the past actions. However, from now on, Organizations that will benefit from the aforementioned bad practices could see their member list reset at Novaquark’s sole discretion. We wish to make it clear that there is nothing to gain from such advertisement and recruitment practices as well as inform other gaming communities that the Novaquark staff will not tolerate these methods of advertisement and recruitment.

II) About Gifting Practices as a Recruitment Incentive
 
Novaquark has not enforced any strict rules regarding gifting practices so you are free to gift DACs or Supporter Packs as you see fit. However, we don’t encourage use of this freedom as a recruitment incentive unless you are perfectly fine with the definition of "gifting" (giving something for free to someone else without expecting anything in return for this gift). 
 
Before gifting a DAC or a Supporter Pack, you should carefully consider that a player could leave your Organization or simply never join it at all. In this situation, this will be your responsibility and we will not refund nor reverse the gift you made to another player. The Novaquark team will not step in to oblige the receiver to fulfill his part of the bargain either (if there was any).
 
So choose and gift wisely.
 
If you have any further questions on the topic, please let us know.
 
Best Regards,
The Community team.

Hi @Nightranger
 
Thank you for standing up against misleading information.
However, why it's understandable that you may be frustrated, there is an explanation for every point you've mentioned:
 
1) The difference in time to apply the punishment:
A mod may not have seen immediately the rule broken by the other community member. It could also be a different mod who see the other player posts and yours.
Moreover, until recently, we had a very relaxed policy in terms of moderation on the Discord. We are all (the Novaquark team and the Moderator team) for the freedom of speech. However, recently, with the populations growth and recent technical problems, some people abused clearly this freedom and made the Discord a lot less friendly that it used to be. The frustration is understandable when there are issues, but some community have crossed the line. So it has been asked to the Moderator team to enforce a moderation rules in a stricter way. The moderation has become suddenly heavy, maybe a bit too heavy, and some adjustments probably need to be made. Perfectly balanced moderation is not something  that easy, especially on a Discord with thousands of players. Though they may have had a heavy hand in that case, The mods have done their job.
 
2) Regarding the fact that the other involved person was a backer: 
It was never taken into account in the sanction. If he was let free to speak as he did until now, it wasn't because he was a backer, but because he started to do it during a time where the moderation policy was more relaxed. A few backers started to have an unacceptable behavior on Discord, and they got heavily sanctioned (and among them were some backers with a much higher level than the one you interacted with. Being a backer is not a protection nor a freepass to have a toxic behavior, no matter the backer level). 
 
3) The reason for the sanction:
On a global level, calling someone "shitmongering idiot" fall into the profanity field. You were not really muted for the word "idiot", but more for "shitmongering". While it was probably deserverd this time, it's a slippery slope to allow it, as others may use in other context, provocative and not necessary deserved. Though it's totally understandable that you feel frustrated to have been pushed while fighting disinformation, the punishment (30 minutes) wasn't that strong, even if it was maybe a bit heavy, due to the context. A simple warning could have work too, but again, keep in mind that there are thousands of players on the Discord now and it's not always easy to make the perfect call on the spot. After discussing with the Moderation team it was clearly nothing personal. Also, yes, though your post were removed (and a bunch of others), there is proof as some bot is logging removed posts.
 
4) The 24 hours mute reason:
Well, the rule you broke this time was pretty clear. It's the same on both Discord and the Forum, and it's a fairly common rule among internet communities:
"Do not challenge/call out publicly a Mod decision." 
@Braddock512 is right: If you have an issue, try to talk in private with the Moderator or at least one Moderator who is available. If you're not convinced by the explanation and you have very solid reasons of not accepting the mod decision, then you can escalate to a Community Manger (NQ-Naerais, NQ-Nomad or I). By challenging/calling out publicly, it can be interpreted as a way to make trouble and not really a will to find an explanation or a solution. It never ends with a happy ending when done in public. Because of what has just been explained, this rule will never change.
 
Ultimately, if you see someone starting spreading disinformation, if it seems the person cannot be reasonned, do as @blazemonger said: ping the mods. That's a valid reason to ping them. Do not take the risk of putting yourself in trouble by starting saying profanity. It's not because some around do that and haven't been moderated (yet) that it's okay to do it yourself in return. Moderators may not have eyes everywhere at any time, and again, keep in mind that the discussion flow is quite fast, making it difficult to spot everything, because the Discord hosts thousands of players. 
 
All in all, we'll try to improve the moderation of the Discord, to make it more adapted to the Community growth.
We just ask you to be a bit more patient.
 
Best Regards,
Nyzaltar.

Hi @Nightranger
 
Thank you for standing up against misleading information.
However, why it's understandable that you may be frustrated, there is an explanation for every point you've mentioned:
 
1) The difference in time to apply the punishment:
A mod may not have seen immediately the rule broken by the other community member. It could also be a different mod who see the other player posts and yours.
Moreover, until recently, we had a very relaxed policy in terms of moderation on the Discord. We are all (the Novaquark team and the Moderator team) for the freedom of speech. However, recently, with the populations growth and recent technical problems, some people abused clearly this freedom and made the Discord a lot less friendly that it used to be. The frustration is understandable when there are issues, but some community have crossed the line. So it has been asked to the Moderator team to enforce a moderation rules in a stricter way. The moderation has become suddenly heavy, maybe a bit too heavy, and some adjustments probably need to be made. Perfectly balanced moderation is not something  that easy, especially on a Discord with thousands of players. Though they may have had a heavy hand in that case, The mods have done their job.
 
2) Regarding the fact that the other involved person was a backer: 
It was never taken into account in the sanction. If he was let free to speak as he did until now, it wasn't because he was a backer, but because he started to do it during a time where the moderation policy was more relaxed. A few backers started to have an unacceptable behavior on Discord, and they got heavily sanctioned (and among them were some backers with a much higher level than the one you interacted with. Being a backer is not a protection nor a freepass to have a toxic behavior, no matter the backer level). 
 
3) The reason for the sanction:
On a global level, calling someone "shitmongering idiot" fall into the profanity field. You were not really muted for the word "idiot", but more for "shitmongering". While it was probably deserverd this time, it's a slippery slope to allow it, as others may use in other context, provocative and not necessary deserved. Though it's totally understandable that you feel frustrated to have been pushed while fighting disinformation, the punishment (30 minutes) wasn't that strong, even if it was maybe a bit heavy, due to the context. A simple warning could have work too, but again, keep in mind that there are thousands of players on the Discord now and it's not always easy to make the perfect call on the spot. After discussing with the Moderation team it was clearly nothing personal. Also, yes, though your post were removed (and a bunch of others), there is proof as some bot is logging removed posts.
 
4) The 24 hours mute reason:
Well, the rule you broke this time was pretty clear. It's the same on both Discord and the Forum, and it's a fairly common rule among internet communities:
"Do not challenge/call out publicly a Mod decision." 
@Braddock512 is right: If you have an issue, try to talk in private with the Moderator or at least one Moderator who is available. If you're not convinced by the explanation and you have very solid reasons of not accepting the mod decision, then you can escalate to a Community Manger (NQ-Naerais, NQ-Nomad or I). By challenging/calling out publicly, it can be interpreted as a way to make trouble and not really a will to find an explanation or a solution. It never ends with a happy ending when done in public. Because of what has just been explained, this rule will never change.
 
Ultimately, if you see someone starting spreading disinformation, if it seems the person cannot be reasonned, do as @blazemonger said: ping the mods. That's a valid reason to ping them. Do not take the risk of putting yourself in trouble by starting saying profanity. It's not because some around do that and haven't been moderated (yet) that it's okay to do it yourself in return. Moderators may not have eyes everywhere at any time, and again, keep in mind that the discussion flow is quite fast, making it difficult to spot everything, because the Discord hosts thousands of players. 
 
All in all, we'll try to improve the moderation of the Discord, to make it more adapted to the Community growth.
We just ask you to be a bit more patient.
 
Best Regards,
Nyzaltar.

Hi @Nightranger
 
Thank you for standing up against misleading information.
However, why it's understandable that you may be frustrated, there is an explanation for every point you've mentioned:
 
1) The difference in time to apply the punishment:
A mod may not have seen immediately the rule broken by the other community member. It could also be a different mod who see the other player posts and yours.
Moreover, until recently, we had a very relaxed policy in terms of moderation on the Discord. We are all (the Novaquark team and the Moderator team) for the freedom of speech. However, recently, with the populations growth and recent technical problems, some people abused clearly this freedom and made the Discord a lot less friendly that it used to be. The frustration is understandable when there are issues, but some community have crossed the line. So it has been asked to the Moderator team to enforce a moderation rules in a stricter way. The moderation has become suddenly heavy, maybe a bit too heavy, and some adjustments probably need to be made. Perfectly balanced moderation is not something  that easy, especially on a Discord with thousands of players. Though they may have had a heavy hand in that case, The mods have done their job.
 
2) Regarding the fact that the other involved person was a backer: 
It was never taken into account in the sanction. If he was let free to speak as he did until now, it wasn't because he was a backer, but because he started to do it during a time where the moderation policy was more relaxed. A few backers started to have an unacceptable behavior on Discord, and they got heavily sanctioned (and among them were some backers with a much higher level than the one you interacted with. Being a backer is not a protection nor a freepass to have a toxic behavior, no matter the backer level). 
 
3) The reason for the sanction:
On a global level, calling someone "shitmongering idiot" fall into the profanity field. You were not really muted for the word "idiot", but more for "shitmongering". While it was probably deserverd this time, it's a slippery slope to allow it, as others may use in other context, provocative and not necessary deserved. Though it's totally understandable that you feel frustrated to have been pushed while fighting disinformation, the punishment (30 minutes) wasn't that strong, even if it was maybe a bit heavy, due to the context. A simple warning could have work too, but again, keep in mind that there are thousands of players on the Discord now and it's not always easy to make the perfect call on the spot. After discussing with the Moderation team it was clearly nothing personal. Also, yes, though your post were removed (and a bunch of others), there is proof as some bot is logging removed posts.
 
4) The 24 hours mute reason:
Well, the rule you broke this time was pretty clear. It's the same on both Discord and the Forum, and it's a fairly common rule among internet communities:
"Do not challenge/call out publicly a Mod decision." 
@Braddock512 is right: If you have an issue, try to talk in private with the Moderator or at least one Moderator who is available. If you're not convinced by the explanation and you have very solid reasons of not accepting the mod decision, then you can escalate to a Community Manger (NQ-Naerais, NQ-Nomad or I). By challenging/calling out publicly, it can be interpreted as a way to make trouble and not really a will to find an explanation or a solution. It never ends with a happy ending when done in public. Because of what has just been explained, this rule will never change.
 
Ultimately, if you see someone starting spreading disinformation, if it seems the person cannot be reasonned, do as @blazemonger said: ping the mods. That's a valid reason to ping them. Do not take the risk of putting yourself in trouble by starting saying profanity. It's not because some around do that and haven't been moderated (yet) that it's okay to do it yourself in return. Moderators may not have eyes everywhere at any time, and again, keep in mind that the discussion flow is quite fast, making it difficult to spot everything, because the Discord hosts thousands of players. 
 
All in all, we'll try to improve the moderation of the Discord, to make it more adapted to the Community growth.
We just ask you to be a bit more patient.
 
Best Regards,
Nyzaltar.

@Kyllian @ToothlessRaider @LouHodo
The current waiting queue for the Customer Support is exceptional and temporary
The Customer Support had a decent response time in Alpha (around 48-72 hours). However, the surge of requests exploded with Beta Launch, and we are currently scaling up our Customer Support team to catch up with the amount of requests. Please be patient. If you have no answer yet, it's not because the Customer Support doesn't want to answer you. It's just that there are way too many tickets to handle each of them as quickly as the team would like. 
On a side note, this forum has rules: insults, provocations & flaming are not tolerated.
I will put the posts above on the (understandable) frustration, but if this continues we will moderate without further notice.

Best Regards,
Nyzaltar.

@Kyllian @ToothlessRaider @LouHodo
The current waiting queue for the Customer Support is exceptional and temporary
The Customer Support had a decent response time in Alpha (around 48-72 hours). However, the surge of requests exploded with Beta Launch, and we are currently scaling up our Customer Support team to catch up with the amount of requests. Please be patient. If you have no answer yet, it's not because the Customer Support doesn't want to answer you. It's just that there are way too many tickets to handle each of them as quickly as the team would like. 
On a side note, this forum has rules: insults, provocations & flaming are not tolerated.
I will put the posts above on the (understandable) frustration, but if this continues we will moderate without further notice.

Best Regards,
Nyzaltar.

@Kyllian @ToothlessRaider @LouHodo
The current waiting queue for the Customer Support is exceptional and temporary
The Customer Support had a decent response time in Alpha (around 48-72 hours). However, the surge of requests exploded with Beta Launch, and we are currently scaling up our Customer Support team to catch up with the amount of requests. Please be patient. If you have no answer yet, it's not because the Customer Support doesn't want to answer you. It's just that there are way too many tickets to handle each of them as quickly as the team would like. 
On a side note, this forum has rules: insults, provocations & flaming are not tolerated.
I will put the posts above on the (understandable) frustration, but if this continues we will moderate without further notice.

Best Regards,
Nyzaltar.