Juvenius Drakonius

it a refreshing idea, i like it!

This is a great addition to the LUA! excellent work! can we get the - Player Static URLs for images- now that we have some new fancy Screen Resolutions? You can read up the idea in 
 

The Dual Universe egg hunt has begun Noveans! 
 
From Saturday, April 16th to Monday, April 25th, please join us for An Egg-cellent Adventure!
 
All around Alioth you will randomly find colored eggs on the ground as well as some other in plain sight places. Some of them you may find often (common), some of them might be a rare find or if your egg detecting skills meet the challenge, you may find a special Novaquark staff egg! All eggs contain gifts from the Novaquark team, so do not forget to smash them open to see what’s inside!
 
There have been several players who have already found some eggs, so you’re going to need to be quick, lucky, as well as very observant!  
 
There’s more! This Egg-tastic celebration is also a competition. Each egg is worth a certain amount of point(s), which means the rarer the egg, the more points you will get. Colors include white eggs (most common), green, yellow, blue, red and the very special Novaquark staff egg which is the most valuable of them all!
 
Once you find an egg, there will be a special code inside (read carefully!). Copy the code and enter it into this simple form that is linked inside the egg and register your code to start accumulating points!

 
Helpful Hint: Start your search by looking around the Point of Interests (POIs) around Alioth.  
 
Good luck Noveans, be egg-cellent to each other. 

DU has been running for more 4 years and not having a PROPER WIKI does not help with new player retention and establish player experience . The only wiki available is the FANDOM's Dual Universe one, and it is just painfully full with ads, we need an alternative to it.
 
We at NIS made this quick mockup of a CLEAN WIKI, what could be had if we all work together to make it. https://wiki.nis.do/. It doesn't take much to make it work if enough players join in together to DU IT, no solo player can do this. We offer a start, an initial proposal to the community, lets make this a project we can all back and make happen, a GOD DAM GOOD WIKI FOR DU.
 
Join in the conversation at NIS discord, find it in https://standards.nis.do or PM me for invite in Discord #Juve2318.

DU has been running for more 4 years and not having a PROPER WIKI does not help with new player retention and establish player experience . The only wiki available is the FANDOM's Dual Universe one, and it is just painfully full with ads, we need an alternative to it.
 
We at NIS made this quick mockup of a CLEAN WIKI, what could be had if we all work together to make it. https://wiki.nis.do/. It doesn't take much to make it work if enough players join in together to DU IT, no solo player can do this. We offer a start, an initial proposal to the community, lets make this a project we can all back and make happen, a GOD DAM GOOD WIKI FOR DU.
 
Join in the conversation at NIS discord, find it in https://standards.nis.do or PM me for invite in Discord #Juve2318.

Welcome to DU! what is the story behind Nyota handle?

DU has been running for more 4 years and not having a PROPER WIKI does not help with new player retention and establish player experience . The only wiki available is the FANDOM's Dual Universe one, and it is just painfully full with ads, we need an alternative to it.
 
We at NIS made this quick mockup of a CLEAN WIKI, what could be had if we all work together to make it. https://wiki.nis.do/. It doesn't take much to make it work if enough players join in together to DU IT, no solo player can do this. We offer a start, an initial proposal to the community, lets make this a project we can all back and make happen, a GOD DAM GOOD WIKI FOR DU.
 
Join in the conversation at NIS discord, find it in https://standards.nis.do or PM me for invite in Discord #Juve2318.

DU has been running for more 4 years and not having a PROPER WIKI does not help with new player retention and establish player experience . The only wiki available is the FANDOM's Dual Universe one, and it is just painfully full with ads, we need an alternative to it.
 
We at NIS made this quick mockup of a CLEAN WIKI, what could be had if we all work together to make it. https://wiki.nis.do/. It doesn't take much to make it work if enough players join in together to DU IT, no solo player can do this. We offer a start, an initial proposal to the community, lets make this a project we can all back and make happen, a GOD DAM GOOD WIKI FOR DU.
 
Join in the conversation at NIS discord, find it in https://standards.nis.do or PM me for invite in Discord #Juve2318.

Following the discussion around yesterday’s devblog, the community asked us to look over our figures to see what we can reliably sustain in terms of construct limits. In this communication we want to take the opportunity to outline what we have decided to change from the previous devblog as well as to explain some decisions such as the mechanics of construct abandonment and our reasons for arriving at our previous figures. These proposed changes are still being developed by our design team and we welcome your continued feedback on this major update.
 
Organization Constructs Slots versus Personal Construct Slots
 
There appeared to be some confusion in yesterday’s devblog between organization and personal construct slots. Personal construct slots are always independent of organization construct slots. 
 
Before outlining the details of the construct slots, it’s important to note that our position on excess construct abandoning mechanics. For the avoidance of doubt, when this change is implemented in the Panacea release. No construct will be subject to abandonment through the following mechanics for at least the first month after release.
 
This is to ensure as smooth a release as possible, and to allow our players who want to specialize in the architectural gameplay loop or the collecting of wonderful constructs, some time to accrue talent points and to adapt.
 
Personal construct slots:
 
Can only be used for constructs in the player’s ownership. Can not be assigned to organizations. Are non-transferable to other players. Are gained through talents independently of organization construct slots.  
Organization construct slots:
 
Can be assigned to any organization, regardless of membership. Can not be assigned to players. Once assigned to an organization, can not be repealed from that organization for 30 days. Once repealed, the organization will have until the next bi-weekly construct check to ensure that it meets its construct slot requirements. If that bi-weekly construct check determines that the organization has more constructs than it has slots, the organization will receive a warning and be required to ensure the constructs count is brought down to its capacity. If the next bi-weekly construct check following that warning determines that the organization still has more constructs than it has slots, random constructs from that organization will be abandoned until the organization is back in compliance with its slot capacity. All this means that even if you go over the available slot count, you have at the very minimum 14 days to correct it.  
We are keeping the random nature of selection for construct abandonment. This is because as game developers we know that if there exists a way for a game system to be broken, our players will find it. In this particular instance, given the gravity of the impact, we feel that it’s important to protect the game and our community from abuse, and the randomization is an effort to do that.
 
We hope this clears up some of the lingering questions that were remaining yesterday.
 
Player allocated slot amounts, why so low?
 
Following internal research, we determined that currently per active player there are approximately 25 constructs in the game at the present time.
 
Therefore we believed that having a total of 42 slots per player would have been enough to provide an overhead for the community to be able to distribute the available slots amongst each other and support each other's projects.
 
We do value our players and recognise that some of you own considerably more constructs than that average, and though we want to encourage collaboration and community, we don’t want to constrain those players that prefer to go it alone.
 
And, we’ve heard you. 
 
We are looking into an alternative approach that we feel will meet the majority of the community needs while also meeting our requirements for the long term sustainability and balancing of Dual Universe.
 
Talent Changes
 
We are going to increase the core allowances. In yesterday's devblog we proposed a figure of 42 total constructs. We are going to increase that through the introduction of talent changes that will require considerable time investment but keep the door open to players that wish to own many constructs.
 
The new talents are separated into three tiers, increasing in expense significantly per tier.
 
The new figures are (subject to change)

For personal construct slots:
 
The base personal construct slots will be increased from 2 to 10 slots without any talents. The first tier personal construct talent will grant 3 slots per level (up from 2), for a total of 15. The second tier personal construct talent will grant 5 slots per level (up from 1), for a total of 25. The new third tier personal construct talent will grant 10 slots per level, for a total of 50.  
This will allow for a maximum personal construct limit of 100, once all the talents are fully acquired.
 
For organization construct slots:
 
The base organization construct slots will grant 10 slots without any talents. The new first tier organization construct talent will grant 3 slots per level, for a total of 15. The new second tier organization construct talent will grant 5 slots per level, for a total of 25. The new third tier organization construct talent will grant 10 slots per level, for a total of 50.  
This will allow for a maximum organization construct limit of 100, once all the talents are fully acquired.
 
The combination of the two will allow a determined player to reach the maximum number of construct slots that we can reasonably maintain. This will take substantial time investment in order to be a specialization within the game. 
 
We will still be refunding the following Legate based talents:
 
Organization Construct Management Organization Construct Management Specialization Advanced Organization Construct Management Specialization  
These talents will be buffed to collectively increase the maximum ceiling for the organization's construct limit to 1625.
 
If you have already trained Advanced Organization Construct Management Specialization to level 5, by reinvesting the refunded talent points, we estimate that you will be able to reach at least a construct slot capacity total of 80. Further, given the grace period of at least 1 month following the Panacea release, we hope that those amongst our players who value their construct capacity can increase it to a comfortable level of approximately 125 construct slots before needing to make decisions on which constructs to keep.
 
We want to thank you all for your feedback and take this opportunity to recognize the passion you our community have for the future of this game. We would love to hear how you feel about the new changes outlined above in this forum.
 

This is a test right? are you guys joking? how far do you have to change the game till its just an other very different game that what it started originally? This is more a 'DU light' version of the original "EVE meets Minecraft"

Dual Universe’s Panacea update is right around the corner, bringing with it a sizable variety of changes based on feedback from our community. 
Ahead of the update, however, we are immediately introducing revisions to territory upkeep and mining units. 
 
Read on for the full scoop! 
 
GOING INTO EFFECT ON TUESDAY, JANUARY 25th
 
Taxes will be effective again starting Wednesday, January 26th.
The day before, we are going to deploy three adjustments to address the issues mentioned in the Community Feedback regarding Territory Upkeep.
 
Territory Upkeep Reduction: 1 MM --> 500k.

Territory Upkeep was first introduced in the November 2021 Demeter update. After reviewing community feedback, we announced that territory upkeep payments would be postponed for two weeks to allow the Design team time to dig deep into the metrics and fine-tune the system accordingly. 

The upkeep rate per territory will be reduced by 50%, from 1MM to 500k quanta. Player feedback indicated that people felt they were having to sell ore too frequently to generate the funds needed to pay upkeep. In halving the upkeep costs, we will relieve the pressure to make frequent trips to the market as well as the need to sell large quantities of ore.
  Calibrations Charges:
Base calibration charge slots increase : 5 --> 25.
Talent calibration charge slots increase : 1/level --> 5/level.

Also introduced in the Demeter update, mining units were designed as an alternative to digging endless tunnels underground for ore. To keep them producing at their peak capacity requires occasional calibration; however, initial feedback from the community told us that further tweaks were needed for the calibration process. To this end, we’ve made the two changes mentioned above.

This will change the total amount of stored charges from 10 (5 base + 5 max talents) to 50 (25 base + 25 max talents).

The intention behind the charge cap was not to force a behavior in which you felt like you needed to spend charges in order not to “lose out” on charges by hitting the cap and wasting your recharge. 

In view of that, both the base and the talent bonus are drastically going up. This will not only allow you to store more charges in general, but specifically allow you to store a much longer period of time in charge recharge time, giving you much more breathing room to store charges and not waste charge recharge time.
  Calibration grace period: 48h --> 72h
  The calibration grace period is the amount of time during which a mining unit does not lose calibration. Similarly to charge slots, the intention was not to aggressively require you to calibrate mining units every 2-3 days. In our initial calculations our goal was more to hit the 5 to 6 day mark depending on what efficiency curve the player selected, and how many mining units the player was trying to maintain.
 
We are changing the calibration grace period from 48-hours to 72-hours. 
 
This change should bring us closer to the initial values we were looking for and give players more breathing room to calibrate when their mining units seem to be producing less than usual, indicating that calibration is needed.
 
CHANGES COMING WITH PANACEA UPATE (0.28) LAUNCH
 
Using industry units on offline tiles

The intention of requiring online territories for industry units was not to negatively impact industry units on planets. We initially saw it as further incentive to pay for taxes, but it was not a core requirement. This is also why industry units on Ssanctuary and space cores were left untouched.

We understand from player feedback that requiring you to operate mining units on a territory in order to not run industry units at a loss on that territory was an annoyance and many players did not want to run their industry units on the same territories as their mining units.

In view of the preferences expressed, we have decided to allow the operation of industry units on all offline territories. In combination with HQ territories, this will allow you to effectively run industry units on offline territories for extended periods of time.
  Faster extraction animations
  We are also addressing the feedback we’ve received regarding the time it takes to complete a calibration minigame, specifically the frustration from the long loading animations when calibrating a number of mining units.
 
An option has been added in the mining unit UI (tick box) that will let you significantly reduce the time these animations take, drastically reducing the period of time the animations run.
 
Additionally, a number of mining unit mini-game animations have been slightly reduced in duration, thus allowing a faster minigame completion.
 
New talents for surface harvesting
  In order to further incentivize harvesting surface rocks, and to be able to specialize in it, we are adding four talents linked to surface harvesting that will touch on harvesting speed and output.
 
The main goal is to create some surface harvesting specialization for those players who enjoy it, giving them the capability to harvest better and faster, and for longer periods of time.
 
CHANGES COMING POST-PANACEA
 
New surface harvesting controls
  To further address surface harvesting issues, we are working on quality of life-type improvements that will allow a degree of auto-harvesting similar to normal mining as well as other changes to reduce control and UX-based frustrations during surface harvesting. 
Watch for additional details as we refine our plans!
 
 New mining unit surface harvesting, rocks spawning behavior
 
Lastly, we are looking for a solution to simplify the process of gathering rocks. This is in direct response to player requests to eliminate the hassle of having to comb their territories after calibrating a number of mining units. 
 
While this is still in relatively early stages, the solution we are looking at is to spawn the rocks right under the mining unit beam, where the beam hits the ground. Players would then be able to rapidly harvest surface rocks. 
 
BUT WAIT! THERE'S MORE
 
Don’t forget that there’s a lot more to Panacea than the changes and tweaks discussed above. It’s also got some cool new stuff, like the Vertex Precision Tool which we’ll be talking about in the next devblog! 
 
Meanwhile, please join the conversation on the forum here to tell us what you think about revisions we’ve presented in this Devblog.
We’d love to hear from you! 
 
---

The Novaquark team

Round can create confusion...make a circle a circle it's a function of radius....but an ellipse is a function of its axis...2xrx , 2xry.....so its better just o make a new function...a more accurate formula is: 
 
addEllipse(layer, x, y, x-diameter[a], y-diameter[b])
that way it's just to plot the thing x²/a²+y²/b²=1
 

no.

Add the ability to draw elipses on screen lua, good with orbital mechanics graphs. Something like:
 
addEllipse(layer, x, y, y-axis-length, y-axis-length )
 

Wallet feeling a little light lately? Get ready to remedy that when the Panacea update hits, bringing with it two lucrative, quanta-producing possibilities: space wrecks and inactive asset requisitioning (IAR).
 
SPACE WRECKS
 

You’re going about your business, flying through space from one market to another or heading out to join some friends when your radar unexpectedly reveals something. Curious, you move closer to investigate and find wreckage. There’s no indication of who left it behind or why. Finders keepers, right? It’s yours now. And you’ve got some choices to make.
 
DECISIONS, DECISIONS
Will you: 
salvage the ship for materials and elements? tokenize and sell the whole ship? sell the information about where the wreck is located? create a mission to get someone else to salvage it? The decision is all up to you.
 
RADAR AND RARITY
No special equipment is needed to locate these space wrecks, your standard radar is enough to detect them.
They will spawn randomly throughout Helios. There are five tiers of rarity, with lower-tier wrecks with low-value contents spawning at a higher frequency. The highest-tier wrecks will be harder to find; those who discover and harvest them will be rewarded with high-value materials and elements.
 
INACTIVE ASSET REQUISITIONING
 
This system is being introduced to address one of the chief complaints we’ve heard from Noveans, namely abandoned constructs cluttering up the universe, especially in public markets.
 
The purpose of IAR is to:
create salvaging opportunities for players around the game world. ensure cleanliness and performance around markets and other Aphelia zone hot spots. clean up older, unowned constructs.  
In other words, IAR has the potential to create a less cluttered environment for everyone and a fatter wallet for you.
 
ABANDONED CONSTRUCTS DEFINED
Players with a subscription, even if they have not logged in for a while, are in no danger of having their constructs flagged as “abandoned”, with the exception of constructs parked in Aphelia territory as noted below.
 
In effect, constructs belonging to unsubscribed users and not on their owners’ sanctuary zones will eventually lose their ownership, putting them in an abandoned state and making them vulnerable to be salvaged by other players. Likewise, constructs owned by an organization will lose their ownership when the org’s last remaining legate ends their subscription.
 
During the unsubscribe process, players will be reminded that their constructs will be in danger of becoming abandoned. When the constructs lose ownership, a blueprint will be placed in the owner’s inventory should they choose to return to Helios at a later date.
 
TIME’S TICKING 
When an account becomes inactive due to a canceled subscription, a countdown will begin on all constructs belonging to that account. After a period of time, those constructs will lose their ownership and other players will be able to salvage or capture them.
 
Then, all unowned constructs will have a countdown timer and it will count down from the moment it is unowned, regardless of why they are unowned (PvP destruction, IAR, abandonment, etc.) At the end of this timer, the construct will simply be removed from the game world.
 
The ‘ownership’ timer for unsubscribed players’ constructs is three months (90 days/2160 hours). The timer is the same for organization-owned constructs and begins when the last active legate of the owning organization’s subscription expires.
 
Each time a construct is unclaimed, whether due to an owner’s inactive game account or if abandoned via PvP, a one-month countdown to decay is set and is visible to everyone. If no one salvages the construct, it will be permanently removed from the game.
 
As with most newly introduced systems, this is subject to change in the future depending on the metrics we see as time passes.
 
SPECIAL RULES FOR MARKETS 
A modified version of IAR will be used on Aphelia territories, including all market zones.
Regardless of whether or not the owner is an active subscriber, all constructs on Aphelia territories are subject to IAR. As soon as a player exits their construct in Aphelia territory, a 168-hour (seven-day) abandonment countdown will begin for that construct. This is considerably shorter than the default IAR timer. Once that countdown reaches 0, the construct will lose its ownership. A new countdown timer of 48-hours (two days) before deletion will start ticking.
 
HAPPY HUNTING
 
Will you be among the happy scavengers scouring the skyways and byways for wrecked ships and abandoned constructs? Join the conversation about this devblog here.

THE FUTURE OF DU
We’ve seen a lot of positive feedback following the release of our devblog series on the future of DU. We’re  thankful to our community for the great feedback and encouragement. We’ve collected what seem to be the most burning questions following the publication of the blogs and wanted to do a follow-up to address them the best we can. Not all questions have an answer at this point, and we’ll try to fill in the gaps as we’re able in future communications. 
 
Are you going to launch the game in 2021? 
Realistically speaking, we have too much to do with the time that’s left  this year to get to a state where we feel the game is ready for launch. Our current plan is “at some point in 2022”, and we’re targeting mid-year. That projection is tentative, depending largely on our progress and  the feedback we get from our community, so please don’t hold this as a commitment. It could be sooner, it could be a bit later. The state of the game will dictate the date.
 
Why is the game not working on Shadow (cloud gaming platform) and do you plan to support it?
We believe cloud gaming platforms are a great way to enjoy DU if you want to play the game but don’t meet the proper PC specs or want to benefit from the latest hardware improvements without investing in upgrades for your gaming rig; however, we need to clarify that we are not yet officially supporting cloud gaming platforms, including Shadow. Our releases are not tested on these platforms or Windows emulations on Mac and Linux, and we can’t guarantee compatibility at this point. The game is still in beta, and we are focusing our efforts on native Windows PC support.
 
We plan to officially support these platforms at some point, and would like to ensure that when we do we are able to offer ongoing compatibility with adequate testing and collaboration with the platform holders to make a long-term commitment. 
 
We recently started working with a cloud gaming platform in an official manner, and we are hopeful to announce our official support of that platform soon. In the meantime, compatibility with cloud gaming platforms can’t be guaranteed. We log bugs and look at potential quick wins, but we can’t commit to a timeframe for fixing them. Please also note that there is a waiting list of one year to have access to one of the machines of Shadow, which makes debugging all the more difficult.
 
Will there be an updated roadmap?
At the moment, there is no plan to release an official roadmap with dates. We tried to explain why in the three devblogs. We’re changing many things in the way we develop DU, and it’s hard right now to have a clear idea of our future velocity. We don’t want to give you dates that we might not hold. We think it’s more important to have the freedom to adapt to your feedback rather than trying to hit the dates on a public roadmap. We hope you will see this as a sign that things are changing for the better and that we’re being more realistic in our approach.
 
Why don’t we have more frequent releases?
Dual Universe is an extremely complex game to develop. Many of the systems we have already in place are interdependent, and changing or adding a feature has ripple effects on other features and systems both in terms of code and in terms of feature design. For example, RDMS has to be carefully considered in many things we do, as does  the role of organizations in the introduction of new features, etc. Most of the tech we use is custom and not off-the-shelf. It’s one of the secret sauces of the game, and it also makes features much more difficult to work on because we develop the tech AND the features at the same time.
 
Now, with the introduction of the PTS, we hope to make more frequent releases, including releases of prototypes, such as the Lua technology for screen units. How frequently will depend on what goes in these releases and how much work needs to be done after we receive feedback from the PTS. We estimate that you can expect three to four additional major releases in 2021, and smaller releases in-between, but that’s only a ballpark estimate for now.
 
What’s going on with long-standing beta bugs? Are you going to fix them?
Yes we will fix them as quickly as possible although we aren’t able to pinpoint an exact date. Some bugs are easier to squash than others, and some even require a rework of an entire complete backend system to resolve. These processes need to be scheduled accordingly, also taking into account that we want to avoid reworking the same thing multiple times if we suspect that the development of an upcoming feature will force us to rework the same system again. The more critical the bug, the higher the priority. When we’re focused on fixing bugs,  that means we’re not working on the plan we presented to you, so it’s a balancing act. We wish we could give you a list of bugs and a timeframe for each one, but that would be highly unrealistic. These bugs are not being forgotten, that’s the best we can tell you right now.
 
Can we expect a more frequent communication from Novaquark?
We’d love to, just understand that the frequency of our communications really depends on the cadence of the game releases. The way it works is that as soon as the content of a new release is established (at least a content draft), we sit down and make a plan for how and when we’re going to talk about these features/this content. Often we have to wait until a feature is stable enough in terms of game design and/or coding to be able to talk about it or show it, as a feature can evolve a lot along the development process and the unfolding of our sprints. We simply want to ensure that the information we give you isn't misleading, as early communication means the end result may differ significantly once development is complete and the feature is released.
So between releases, there is indeed a communication gap. 
 
There are different general topics we could discuss between releases, but they wouldn’t really bring anything concrete to the table and that communication could be seen as shallow and vague. It’s actually an interesting topic we’d like to explore with you: what is it exactly that you expect in terms of communication? How can we balance having meaningful content to present with what seems to be the need of our players to see ongoing communication? Based on reactions we’ve seen in the past, we  believe that communicating simply for the sake of it when we have nothing really new to talk about is never well-received.
 
What about PvE? Are you planning to add PvE features to make the game more varied?
Our current focus is on enabling emergent content between players. PvE is not one of our priorities at the moment. This doesn’t mean that it won’t ever come to the game, but it is not going to be added before the official release of the game. That said, one could potentially consider the challenges that we’re currently working on as some form of PvE, though not in the sense that you’ll be shooting NPCs or wildlife.
 
Will we see a return of NQ employee Interviews and AMAs?
We would love to do things like livestreams and AMAs again when the time is right. We feel like these formats are better suited when there is a clearly defined topic to focus the discussion, such as a major release for instance. It is duly noted that these interactions with the community are appreciated, and we will include them whenever possible.
 
You mentioned the changes in the industry gameplay, but it wasn’t clear if schematics will stay or go?
The honest answer is that we don’t know yet. When we introduced schematics, it was a major disturbance in the forc… in the economy of the game.  We don’t want to rush into more changes after that, especially given that players invested a lot of hard-earned quanta in buying them. Removing schematics is ONE of the options we’re looking at, as well as changing their prices or adding more recipes. Reverting to the way it was before the introduction of schematics is also on the table. We know we want to do something with the current state of the industry to add back some of the fun that was taken away with 0.23, but how exactly we’ll do it is yet to be decided.  
 
Is there going to be a wipe?
We see that the debate on the topic has been pretty hot in the community for a while, and it’s about the same at Novaquark. We’re uncertain if the changes we are planning to introduce will require a wipe or not, and we’ve started (intense) internal discussions on the topic. Our priority is to try to preserve the time and effort that our players have put in the game since the beta started. Once we’ve got a better idea of how much the changes we discussed in the third  “Future of DU” devblog will impact the game’s economy, we’ll make a decision. If there is a wipe (and it’s a big IF), it may be a partial one only affecting certain aspects of the universe. Our  priority will be to mitigate the impact for long-time players.

Join us in our feedback thread here!
 

Dear Noveans,
We are glad to inform you that several QA jobs have just opened at Novaquark. As having a deep knowledge of the game is a big plus and some of our devoted players may be interested in breaking into the video game industry, we wanted to announce it here first before posting outside the community. 
 
This is a permanent, full-time, remote position. 
 
Responsibilities:
Create test plans and test cases for assigned areas of the game based on production expectations containing accurate verification points, including edge case test scenarios and potential knock-on issues over other areas that could be impacted by specific integrations. Execute test, document results, and measure impact. Report on the user experience and test results, escalating when necessary. Analyze information provided by the Development and Production teams and identify risk areas. Partner with Development, providing solid communication and collaboration. Ensure all test tool data is high quality and updated daily. Document and maintain all necessary testware. Participate in test closure activities; i.e. testware evaluation, knowledge transfer. Always champion the customer experience.  
Requirements:
Able to develop and foster strong working relationships with development partners, customers, support teams, and management. Excellent verbal and written communication skills, including accurate and timely reporting. Excellent organization and time management skills. Passion for software quality and a keen eye for detail. Able to analyze and interpret data/workflows, recognize critical issues, and raise concerns. Previous experience with issue tracking databases (JIRA, Hansoft, DevTrack, Mantis etc.) Good troubleshooting skills. Fluent in English (written and spoken).
Pluses:
Gray-box and white-box testing experience. Certified ISTQB advanced test analyst or equivalent. Experience with application lifecycle and test case management tools. Previous quality assurance experience with an online title, preferably a MMO.  
Qualified applicants should send their resumes to jobs@novaquark.com. 

The Novaquark Team.
 

And all of this to be completed by the end of the year?
Why is NQ not coming clean and out by making it clear that release of the game will be pushed out
 
There is a lot in this blogpost that could be good, also a lot that could not. It's a lot of "working on, planning, looking at, considering, might, may". Where is the actual roadmap update that frankly is clearly needed as from this blogpost one can easily deduct that most of what is still to be done is not even in implementation stages yet and still on the drawing board if not in the conceptualize stage leading in to that stage.
 
Based on this blogpost, a release ready game is at least 18 months away, probably longer.
 
 
Also, IMO too much here seems to imply NQ is looking to make the game "more accessible" for new players. I am not sure how that is even needed. Why should surface gathering yield even more resources? and why do I get the feeling that NQ is actually trying to find a way to roll back schematics and "reimburse" those who bought them instead of designing and creating gameplay solutions that will allow _players_ to find and create schematics which can then be researched, enhanced, copied and brought to market.
 
for most of the mentioned mechanics there is no change or even a signal of progression in the concept of these from what was shared in December. Why is NQ rather clear in part 2 that they need to fix the back end and the core of their technology and then in part 3 just goes back to their usual spin on all the kewl things that are coming.
 
Overall, these three blogposts have not told us anything we did not yet know outside of maybe giving more clear signals that NQ is very, very far away from getting close to a game that could be released.
 
The actual value of these posts is minimal at best. It's fluff and filler. While I get that currently the company has other things to get sorted, why not communicate that more clearly and create time for yourself to make that happen. This just feels like it's mostly ignoring the reality of what NQ is going through which unfortunately is more of the same.
 
 

Has any game maker tried a node/distributed tec? like come to think about it you could have players host servers of "map volxel service" to distribute and offload data off NQ....and NQ pays in ingame currency for the service....humm going to reserch this a bit....good feedback!

Has any game maker tried a node/distributed tec? like come to think about it you could have players host servers of "map volxel service" to distribute and offload data off NQ....and NQ pays in ingame currency for the service....humm going to reserch this a bit....good feedback!

To have a cost efficient data structure is a good step forward for the longevity of the game. I hope similar efforts are done to the quality of content generation.

To have a cost efficient data structure is a good step forward for the longevity of the game. I hope similar efforts are done to the quality of content generation.

What we are building here is ground breaking, it has a lot of potential for both NQ to make profit as well as player to experience an unprecedented MMO content, But with out honest feedback synergy is wasted.
 
A very positive push to right direction this is, thank you and keep it up we are here to help.

What we are building here is ground breaking, it has a lot of potential for both NQ to make profit as well as player to experience an unprecedented MMO content, But with out honest feedback synergy is wasted.
 
A very positive push to right direction this is, thank you and keep it up we are here to help.

it's a big barrier entry barrier and would love to help out! Like Klap we are also part of an all Spanish speaking org and would really want to help with this. It's a 400 Million people market, 2nd most spoken language in the world....that's a big chunk of a player base that could be added to the game.