sleim22

the script is updated for the pve mission lua changes and doesnt care about how many guns or handling. make sure to download the latest versions:
https://github.com/sleim22/Sleim-Hud/releases/tag/v2.3.7
i just testet it and dont get any error

@NQ-Entropy
L-cores are weak in the current pvp meta. I have an idea about how to make them more powerful(but not too powerful) while also adding some neat complexity to ship design in DU, and without taking away from the viability of S and M cores.
_____________________________________________________________

PROBLEMS:
1. Right now, having a light ship is valuable in pvp. Being light not only gives you good accel, it gives you a higher max speed. Having high accel and max speed allows you to withdraw and vent, run away, catch slower targets, dictate battlefield positioning, or just travel faster. L-cores are naturally much heavier, so they suffer here.
 
2. Being small is also important. Having smaller cross section means less enemy hit chance, which makes you harder to kill. Tiny S-cores with a M-shield can tank just as well or better than big L-shield armored L-cores. So again L-cores are penalized for having naturally larger cross section.
_____________________________________________________________

SOLUTION:
My idea is that NQ add a new mechanic that rewards having higher mass and cross section: Shield stability.

Shield stability: Higher construct mass and volume would make your shield tougher - a separate damage modifier that reduces incoming damage like resistances do.
_____________________________________________________________
 
RULES:
The mass and volume bonuses would be on separate curves, then added into one shield stability value, listed as a base value of 100% - a damage reduction multiplier of 1. High shield stability values might be 150% - a damage reduction multiplier of 0.666(33.33% damage reduction, which gives an effective hp bonus of +50%). Both curves would never allow shield stability to get anywhere near 200% (damage reduction multiplier of 0.5) so that a smaller shield could never achieve the same effective hp as a shield of one size larger. The mass and volume bonuses would be small at the low end of the curve. The mass and volume curves would have diminishing returns at the high end so that players can't just scale their shield stability to infinity. The floor of the mass bonus curve would start at the standard mass of a L-shield(125t). The floor of the volume bonus curve would start at the volume of a L-shield(646m³). The bonus scale would be the same for all shield sizes. L shields on heavy/voluminous ships would get good value, but standard-sized S and XS ships would get little to no value from this system, since they would have to achieve extreme masses (in the multi-kiloton range) and volumes to achieve high shield stability values. Shield stability would be calculated dynamically, so it would decrease throughout a fight as fuel is burned, ammo is used, and especially as voxel is destroyed. _____________________________________________________________
 
EXAMPLE VALUES: (obviously NQ would have to decide the proper curves and bonuses)
A ship with 5,000t mass and 3000m² x 500m² x 1500m² cross section values (a very big boi) gets a shield stability value of 147% - a shield damage reduction multiplier of 0.68. With this shield stability value, a Rare Active Shield Generator L now gets an effective hp increase from 10,000,000 to 14,700,000. So it has significantly stronger shields along with a large amount of CCS from voxel. It's now a tough nut to crack for S ships, but likely very slow and easier to hit for L and M guns.

EXAMPLE GRAPH:

 
_____________________________________________________________

NOTES:
This mechanic would add more choice and variety to pvp ship design. It would allow builders to make more stylized designs that normally would be too voluminous. L-cores would be good at killing other L-cores since their guns would actually do better dps to large targets than smaller guns would. They would target each other in fleet fights. The shield stability mechanic would also make haulers naturally tougher to kill, giving them a better chance to fend off pirates and survive. This would also indirectly add value to voxel, as the mass of additional voxel would simultaneously increase effective shield hp. Heavy voxels especially might become more attractive.  
CONCLUSION:
This shield stability mechanic isn't meant to make L-cores into invincible dreadnaughts, but to give them a solid bonus to survivability in the same way that small ships get bonuses - just reversed. My hope is that it would add potential to L-core multi-crew capital ships in stationary fleet fights. These tough, heavy, expensive ships would still be a liability in cost to build and operate, as they should be, but if properly supported and utilized they could measure up to the current light/fast S-core and M-core meta.

I've tried to think through many scenarios with this mechanic to try to find problems, but I'm only one brain. Does anyone see any issues?

Library
Contains a list of useful math and helper methods that would be slow to implement in Lua, and which are given here as fast C++ implementation.
 
 
Functions
systemResolution3([table] c1,[table] c2,[table] c3,[table] c0): Solve the 3D linear system M*x=c0 where M is defined by its column vectors c1,c2,c3 [table] c1: The first column of the matrix M [table] c2: The second column of the matrix M [table] c3: The third column of the matrix M [table] c0: The target column vector of the system return [table]: The vec3 solution of the above system systemResolution2([table] c1,[table] c2,[table] c0): Solve the 2D linear system M*x=c0 where M is defined by its column vectors c1,c2 [table] c1: The first column of the matrix M [table] c2: The second column of the matrix M [table] c0: The target column vector of the system return [table]: The vec2 solution of the above system
  NEW [vec3] getPointOnScreen([table] worldPos): Returns the position of the given point in world coordinates system, on the game screen [table] worldPos: The world position of the point return [table]: The position in percentage (between 0 and 1) of the screen resolution as vec3 with {x, y, depth}

Hello noveans! As explained in the Mercury Lua devblog, the update is bringing too many changes to list them in such an article. We therefore decided to detail them on a separate thread for players interested in the details!


LUA API CHANGES

In this post, we will then go through each API, one by one, identifying the new additions and changes in the alphabetic order.

To list the general changes:
Added new `player` permanent slot. Represents the local player, usually called MasterPlayer in the API. Give access to name, id, nanopack mass/volume, headlight control, parenting, etc. Added new `construct` permanent slot. Represents the control unit construct, usually accessed through the Core Unit API. Give access to name, warp status, pvp status, more physics data, etc. Implemented new naming convention for events. Changed container content acquisition behavior to a fixed minimum inter-request delay of 30 sec. Added more item API support in containers and industry API. Added specialized API for all engine type elements, such as wings, adjusters, atmospheric engines, space engines, airbrakes, space brakes, vertical boosters, hover engines, rocket engines. Added Lua API for weapons Added Lua API for plasma extractor Re-enabled HDR color support for lights Added Lua left mouse click action for onActionStart, onActionStop and onActionLoop events, as "leftmouse". Replaced all string status values with integers for better comparisons and to be future-proof. Redesigned the Counter element API to make it more interesting. Redesigned the Telemeter element API to make it more interesting. Added several useful functions on different elements  
I invite you at the same time to study the details of the changes in the posts of this thread to see all the subtleties!

As stated in the previous devblog, our goal is to remove all depreciation at launch. However, this will remain dependent on our ability to release the new flight configuration before then and on the feedback we get from our community.
In any case, we will keep you informed if this is retained at release.


LUA API MOCKUP ON GITHUB!

In addition to that, we published a mockup of the API on our public GitHub.
We've made it as usable as possible, directly for use in Visual Studio Code, community tools, etc.
It's free to use, so please enjoy!

https://github.com/dual-universe/lua-examples

The goal will be to update it with every major update we make for the future.


CONCLUSION
 
I hope you will like these changes, from the more concrete to the more subtle ones. I can't wait to see what you'll create with all these additions! And I hope it will inspire you.
Thank you all for the support you have shown for this revamp, it encourages us to go further. Our goal is and will remain to offer you more and better Lua tools, so you can create your own content!

NEW Weapon
Displays information about the weapon's state
 
 
Functions
NEW [int] getAmmo(): Returns the item id of the currently equipped ammo NEW [int] getAmmoCount(): Returns the current amount of remaining ammunition NEW [int] getMaxAmmo(): Returns the maximum amount of ammunition the weapon can carry NEW [int] isOutOfAmmo(): Checks if the weapon is out of ammo
  NEW [int] isOperational(): Checks if the weapon is operational NEW [int] getStatus(): Returns the current weapon status return [int]: The current status of the weapon (Idle = 1, Firing = 2, Reloading = 3, Unloading = 4)
  NEW [int] getContainerId(): Returns the local id of the container linked to the weapon
  NEW [float] getHitProbability(): Returns the current hit probability of the weapon for the current target NEW [float] getBaseDamage(): Returns the base weapon damage NEW [float] getOptimalAimingCone(): Returns the optimal aim cone NEW [float] getOptimalDistance(): Returns the optimal distance to target NEW [float] getMaxDistance(): Returns the maximum distance to target NEW [float] getOptimalTracking(): Returns the optimal tracking rate NEW [float] getMagazineVolume(): Returns the magazine volume NEW [float] getCycleTime(): Returns the weapon cycle time NEW [float] getReloadTime(): Returns the weapon reload time NEW [float] getUnloadTime(): Returns the weapon unload time
  NEW [float] getTargetId(): Returns the id of the current target construct of the weapon  
Events
NEW onReload([int] ammoId): Emitted when the weapon start reloading [int] ammoId: The item id of the ammo NEW onReloaded([int] ammoId): Emitted when the weapon has reloaded [int] ammoId: The item id of the ammo
  NEW onMissed([int] targetId): Emitted when the weapon has missed its target [int] targetId: The construct id of the target NEW onDestroyed([int] targetId): Emitted when the weapon target has been destroyed [int] targetId: The construct id of the target NEW onElementDestroyed([int] targetId, [int] itemId): Emitted when an element on the weapon target has been destroyed [int] targetId: The construct id of the target [int] itemId:The item id of the destroyed element NEW onHit([int] targetId, [float] damage): Emitted when the weapon has hit [int] targetId: The construct id of the target [int] damage: The damage amount dealt by the hit

With the Athena update we decided to hold 3-4 alien cores, the goal being to test our ability to defend multiple cores.

The harsh reality of alien cores
In response, our enemies have put our cores in lockdown ~fifteen times, sometimes 4 on the same day, forcing us to organize ourselves well to allow everyone to come home from work, eat, take care of their family or simply rest. For having a minimum number of people at the end of each lockdown, just in case.
The ends of lockdown follow one another and still nothing on radars, the regularity required by this feature prevents us from pirating on asteroids or pipes as we did before, but the various changes have not reinforced either the interest of them, the motivation is therefore less and less perceptible and it becomes a chore to come and defend...
So we come to this evening of May 21, 4 cores are in lockdown;
Gamma, Theta, Iota and Zeta
Theta and Gamma are respectively under siege at 18:24 UTC and 18:56 UTC, knowing that it takes 20 minutes to secure a core without enemies, the timing is tight but nothing can tell at this moment that our enemies will take advantage of it...

A well thought out plan
18:36 UTC, Theta in siege but without contacts, when suddenly the announcement falls: "CONTACT ON THETA"
10 to 15 ships on radars, the fight is easily managed but a large part of our fleet is therefore in combat lock for the next 10 minutes, preventing warp, and an attack on Gamma begins to grow in our heads. Taking advantage of the combat lock to loot some of the enemy ships, meanwhile another group forms, alerted by the first attack and start moving in direction of Gamma.
18:58 UTC, Gamma in siege and the dreaded announcement drops: "24 CONTACTS ON GAMMA"
We are all surprised and at the same time excited, @here and @everyone appears on the various discords to call Legion for mobilization, we've been waiting for this moment for a long time, impossible to miss it!
We get together in voice, we regroup in the same place in game and we jump into the fray. Focus announcements follow one another, but more surprisingly, there are not 24 contacts but 50... 70... 100... (we reached 150 contacts on the radar at one point, allies and enemies). Several ships are dummys, but the enemy is really numerous, we will have to be disciplined and use our experience in PVP but also as a group.
The confrontation was complex, the previous patch broke the radars and transponders, impossible to sort the contacts on the radar and even less those who change their name like ours (our entire fleet bore the name "WONDU" on its ships), but LUA scripts save us and maintain some semblance of order in this nameless mess.
The station sees its shield descend little by little, an alt left on it allows us to follow it live, protecting the core is impossible without killing all our enemies, it must get out of the 10 minutes of combat lock to recharge its shield. It ends up being core, we manage to regain control, the core itself is not enough, we have to hold these 10 minutes. Unfortunately the timer is constantly reset, even after taking advantage of the fight; the dead ships then repaired by our enemies, the incessant comings and goings of small fast ships and those bearing our tag, it's almost mission impossible to prevent them from approaching, the fight drags on so long as we almost destroyed the entire enemy fleet.

The Liberation
"30 seconds left" (combat timer on alien core)
Announced in voicecom, still no hostile contact... When suddenly a M core appear, rushing to the alien core.
"15"
Some of our remaining forces are concentrated on him, the burst is violent but it's not enough.
"10"
He is at 80km from the core, almost dead but he still represents the last threat of these long hours of confrontation.
"OHNO OHNO OHNO HE IS SHOOTING [filtered] MY LIFE"
...
"IT'S REPAIRED"
Nerd screams, phew of relief, Legion held on but not without difficulty.

A big GG to everyone, even if the game is clearly not the most pleasant for PVP currently, it's events like this that make the game live. Bravo for the organization, the execution and the destruction of the core. We had a lot of trouble keeping our precious plasmas

Some stats about those fight
The opposing forces: Legion vs "Empire, BOO, CVA, Penrose, CYT, IC, CRN, MSI, SB Nation, UA and I think another 1 or 2, just a handful from each, think IC had the most, but mostly new to PvP"
+/- 150 ships involved
~40 Legion members at the end
More than 3 hours of fight
45+ wrecks still close to Gamma this morning
Very very little amount of stasis
Too much ammo fired
Too much kills
Not enough transponder xD
 
 

Hi, can we have different colors on dynamic construct in PVP?

By priority order:
NQ Staff > Green (like actually)

Transponder match, not a NQ Staff > Blue

Transponder didn't match BUT pilot is in friendlist/orgs and not a NQ Staff > White

Transponder didn't match, not in friendlist/orgs and not a NQ Staff > Red


It's the first MMO where I can't clearly see my ennemies/allies, I take 2 minutes for color them on GIMP, with 5 minutes you can have a nice icon for sure.

I would consider duplicating construct names or even changing names good combat tactics. There is honestly no way to regulate this without artificially imposing naming restrictions for everyone and that would be very unpopular. Instead I suggest identifying targets via their construct ID. Perhaps an argument could be made that this ID should be included in the default radar HUD to help new players without sufficient lua experience. Would that be an acceptable compromise?

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).

Does not generate quanta.
I mostly like it, the details remain to be seen.
But dont claim it generates quanta please.

 There are five tiers of rarity, with lower-tier wrecks with low-value contents spawning at a higher frequency.

Any info on how close to planets or safezone? Space is too big and empty to fly around randomly to "dig a 2SU wide tunnel" and look for something. 

As soon as a player exits their construct in Aphelia territory, a 168-hour (seven-day) abandonment countdown will begin for that construct. 

Hell yes, thank you, please don’t backtrack on this one, it is the only way to really clean up markets and make them usable for everyone.
 

It's happen often that Alioth/Madis /Thades PVP asteroid spawn very close of the safe zone limit
In that case you have tens of ships at the safe zone limit, and players flying with their nanopack to the PVP asteroid, and come back to their ship as soon as their nanopack is full.
Is that really the gameplay NQ wants ? Those players completely avoid the risk/reward mechanics !
Can we just have a limit so that PVP asteroid never spawn so close of the safe zone (something like 30su)
 

The AC has grave concerns over intel received this last week of missions being introduced into the universe. There are several groups of shady organizations delivering contraband out of Feli to several surrounding planets.
 
These shady organizations in question have been disguising dangerous shipments as mundane and routine ore and mineral shipments, such as scandium and chromium. Core Samples from these intercepted shipments are rumored to have been transported to the AC's home world where their best and brightest scientists will conduct further analysis. These materials can ABSOLUTELY not reach the hands of citizens for it could be devastating to the population!
 
The AC has formed the largest fleet the universe has ever seen to combat this threat and stomp out illegal and dangerous activities. Effective immediately all vessels seen attempting to leave Feli must stop and submit to cargo inspection or be immediately disabled.
 
All civilian traffic is warned that a convoy of AC haulers transporting valuable space fuel for these operations will be transported to the planet of feli at 3pm EST. This convey is being guarded by the AC fleet and unidentified vessels will not be allowed to approach.

Hey everyone,
so the event was a few weeks ago but no one talks about what happend their.
At the moment when at every PVP Battle something wierd happens and an Member from Hyperion taken part of it, everyone says that Hyperion is using Cheats or Glitches.
Yes the two ships which takes part of this Battle uses Stacked Elements and Burried Elements, but both is allowed from NQ at the moment and thats really not the Problem.
 
After this Battle we dont know what happens, so we decided to do some research. We figured out one really big Problems that game has at the moment.
We have this Information a really long time but i dont know why my Leadership or NQ didnt put an offical Statement on the Forum or so.
 
So what we figured out:
If your ship gets enough DMG from PVP fights your PC uses much ressources.
In this Fight the most AC members shoot with Railgun which makes good Damage but the Damage per Seconds are low. Both Hyperion ships shot with laser which has after Cannons the highest DPS.
Both Ships got 4 Seats of Laser which means per Ship 24 Lasers. At the moment Hyperion engaged the Boo Ships their getting so much damage in an shot time that their PCs are "Burning".
The pc off the Pilot is the "bottleneck" in this Part, on his PC the Ship gets calculated. But the biggest Issue in PVP fights at the moment where the Damage at the Voxels, at every shot your PC Downloads the "new Voxels" of your ship. The Boo Ship got a really big Part of Gold Voxel which creates microvoxels with every shot/damage so your PC Downloads really much Voxel changes.

We tested it and the Download is the biggest Problem in the actual PVP.
My PC in the Video got:
i7-8700k(overclocked to 5.0Ghz), 32GB Ram, Readon RX 6800XT, Samsung 970Evo M2 and and 1Gbit Internet Connection.

First test
11 Gunner, 50 Missiles, 4 Railguns to a Plate of Gold Voxels
Most shots missed, network spike 40Mbit/s, lowest FPS around 20
 
Second Test:
8 Gunner, 48 Lasers to a Plate of Gold Voxels
Min of FPS: 2, Network spike to 254Mbit/s

Third Test:
8 Gunner, 48 Lasers to a Plate of Iron Voxels
Min of FPS: 5, Network spike to 159Mbit/s

Fourth Test:
Ethernet Limited to 16MBit/s 
8 Gunner, 48 Lasers to a Plate of Iron Voxels
Min of FPS: 5, it takes around 2 Minutes to load every Voxel Change.

You can watch these Results in the Video:

RIP Dual Universe. 
 
It was fun while it lasted.
Kind of?
 
I remember accidentally stumbling across a video of Dual Universe, the alpha feature showcase running ~50 minutes long. Boy oh boy was I impressed. In the past I've played things such as starmade, and empyrion, and always loved the idea of a space sci-fi and as a star wars fan myself, always building large scale stuff like star destroyers and blah. As fun as these games were to play, they always suffered from having next to no major interaction in multiplayer. As you can guess, the whole idea of Dual Universe being a space sci-fi sandbox in an MMO setting was an incredibly grand and alluring idea. I had plenty of fantasies and imaginations of how awesome DU could turn out to be, as many many others had too. Unsure of what exactly I can say without breaching NDA, I'll keep it vague. Playing the Alpha build was pretty frustrating lol. However, the community made up for a lot of DU's pitfalls. I had discovered a sort of 'role play' civilisation building community that spanned over years of living under a shell of tight NDA alpha development, which was quite interesting. Everyone was eager for DU to enter beta, and to get serious. To let go of needing to 'Role play' and just be able to take their metagaming to the next level in the persistent world of Dual Universe.

The Beta launch was certainly a real mouthful. Everyone rushed out the gates to make their mark in the world, a race to cement their existence into DU's solar system. Damn were there a lot of people, compared to the current population it's almost unbelievable. Even NQ didn't expect such a huge influx of players to jump in. This caused a lot of dumpster fires during the start of beta, and a lot of NQ's efforts were directed toward putting them out. It was choppy as hell, but it seemed like DU really had a major ingredient to succeed, player population. Regardless of the hugely buggy nature of the game which many people criticized as being no way near beta ready, especially paid beta ready, people still trucked on hopeful of what DU could be. One extremely common phrase among critics and players alike, was that DU had so much potential, and every one of them were right. 
 
With the introduction of larger than alpha resource nodes amongst all of the planets, and meganodes for each ore, DU experienced a huge boost in progression, as everyone grinded their brains out to collect as much ore as they could. Mega factories popping up left and right, in every nook and cranny. Production and resource exploitation at an all time high left NQ worrying about the fast paced progression they seemed to be quite uncomfortable with.
 
The idea behind DU was that it was oriented to group play in such a way that people would build organisations, alliances, countries, and civilisations. Unfortunately, apart from marketing efforts DU wasn't really setup to encourage any of this. Being weary of needing to RP to really do any of this, most older groups began to grow uneasy. The cause for this controversially being the implementation of safezones, and lack of territory warfare, which was a desired addition for the beginning of beta. Initially, the idea was that the only safe place in the solar system would be the Sanctuary moon. The absolute only reason for its current existence. Instead of a creative solution to allow organisations/nations to create their own safezones, their own mark in the solar system, we were given a very, very lenient absolute safe space. In my opinion, the sole existence of any safezones aside from the sanctuary moon works only to remove any incentive or encouragement for a nation or country to emerge in any part of the solar system. Everyone joined into DU with their own dreams, and their own desires of creation. And everyone was very much free to move about and do as they wished, on their own. It's likely NQ were forced along this path due to simply not having enough time to develop critical gameplay mechanics, coupled with problems among the studio itself, with none of the original team who initially worked on DU no longer even working at NQ. DU now has effectively turned itself from a promising civilisation building MMO, into a quiet, enormous and extremely overpriced museum for sci-fi voxel creations.
 
The PVP, and effects of it are nothing short of Pitiful.
 
NQ's move to stifle progression and control it's rate among DU, backfired miserably and completely decimated DU's saving grace, its player population. The introduction of update 0.23 unsettled and enraged SO many people, eesh. If you're reading this and your opinion is that 0.23 was a great patch, you clearly don't see the incredible damage that it's done to DU, NQ, and their PR. Enjoy your giant space museum while it lasts. NQ certainly took a major step back in communication in the aftermath of update 0.23, which only further annoyed the playerbase.

Recently a new Community Manager that went by NQ-Naunet was hired, and made strides in engaging with the remaining DU community. Only just recently, after only 4 months of working at NQ, Naunet has left NQ without a word. Naunet was much appreciated by the community, and her departure left a gaping hole in the communities confidence in NQ's ability to manage a community, sparking a recent freefall dive (absolute shitshow) in NQ's temporarily completely unmoderated Forums, with only NQ-Naerais left to hold the reins on a fragile and wavering community.
 
Another recent incident involving NQ deciding to completely remove ingame support, and discord support has also caused unease and frustration throughout the entire playerbase. Leaving the only form of support to the ticket system, which is famous taking up to a month or more for a response, and often the responses were extremely unhelpful. The removal of NQ's ingame support system basically blew up any players hope for help in navigating DU's buggy and problematic nature.

The ingame support team did an incredible job of handling many of the problems thrown at players, most of which simply made no sense to wait months for. Most of the tech support workers have left NQ after this move.
Their names are:
NQ-Wokk
NQ-Blacksun
NQ-Gallion
NQ-Astratum
NQ-Samaritan
NQ-Stargazer
NQ-Orion
NQ-Reaper
NQ-StarFire
NQ-Xeno
 
Apologies for anyone I've missed, but they've singlehandedly been through the rivers of buggy shit to ensure that players had the best possible experience in DU.\
 
Now that the support team is gone, Naunet is gone, any Liason between community and NQ non-existant, most people just want to see DU put out of its misery. Was a fantastic concept, but it seems like it'll just never work. With the whole idea of DU having millions of players, but only being attractive to a very niche group of resilient and hardcore players, and the recent decision of NQ, DU has just lost it's much needed momentum, and as we can see with numbers pulling out of NQ's roster, including more prominent and notable names, faith in NQ's ability to deliver DU as advertised, promised, and pitched, are at an all time low.
 
Even JC's in rough shape after 0.23, poor dude.
 

 
As for JC himself, mad respect for the dude. Starting a brand new company to develop and handle his dream game (as was ours), was bold and brave of him. We all wished him the best in his endeavours, and are all sad to see what is to come of DU.
 
If you're new and wanting to get into DU, I'd advise against it. If you have friends to play with and wanna muck around DU, all power to you. DU isn't really that pricey, probably won't last for another 3 months anyway.
But for anyone looking for what DU was pitched as, it's looking like a hard skip. 

And now some random memes to dust off the post.


 

 

 
 

 

 

 

 

 

 

 

 

 

 


RIP, nobody wanted you here. Except for maybe your competitors, although they probably feel guilty about it now.

Whether it's rude or not has nothing to do with the rules. If a group is playing basket ball at a park;  you can run onto the court, kick the ball, and yell "Let's play soccer!" If you don't steal the ball, it's not illegal. It's still rude.

this devblog sounds very promising! looking forward to it

Hey there, Noveans!

As we ramp up for the next Dual Universe update, we wanted to begin sharing information about some of the interesting new features you can look forward to with the arrival of 0.24.
 
One of the key highlights of 0.24 is the Mission system, affording the movers and shakers an opportunity to, well, move and shake their way to a wealthier DU lifestyle. And who doesn’t love the delicious sound of quanta cascading in their coffers? ?
 
OUR MISSION

In listening to player feedback, we know that players have been looking for more ways to make money. The Mission system will provide those opportunities in a number of ways that suits a wide swath of playstyles and experience.
 
The intent of Mission system is to:
 
Offer new ways for players, especially new players, to make money. Allow merchants to focus on creating goods rather than spending time traveling to markets to sell their wares. Give those who enjoy traveling more than making things a lucrative reason to take to those beautiful, wide-open skies. Create more traffic in space, hence more opportunities for pirates. Help organizations to coordinate internal work.
  The long-term goal is to enrich the Mission system with more mission types, starting with “taxi” missions, SoS, and later adding PvP and various other “formalizable” activities. For now, we’re introducing the Mission system with transport-type hauling missions.

It all starts with the Mission Panel, a dedicated dashboard tab for job and hauling missions. It is equivalent to other dashboard tabs such as the organization dashboard tab. Within the Mission Panel, you’ll find the "Job Forum" section and the "Hauling" section. Each of these contains a similar page: a home page, a search page, a creation modal, etc.

THE JOB FORUM

The Job Forum allows players to create jobs with various specifications. (Please note that the UI for the Mission system is still in progress. The images below are samples of what it will look like.)


 
The upper part of the interface lists “Aphelia” jobs, which are created by Novaquark to provide information about game events, like discovering new wreck ships, etc.
Players can inspect job details in a dedicated window and engage in a conversation with the job issuer in a mini-chat integrated to the mission.


 
You will also find Aphelia (NPC) missions that will provide new ways of making money. And, lastly, issuers can limit their missions to fellow org members only as a way to keep transactions and missions in-house.

HAULING MISSIONS

These come with formal guarantees on the rewards, collaterals, time, etc. It is tightly-coupled with the possibility to create sell orders so that you can express your intention to sell a good on a distant market and simultaneously create a transport mission to arrange transport of the goods to the said market.
The definition of a hauling mission includes:
 
Start/end point + indication if this is in PvP zone or not. Collateral (lost by the mission responder if the mission is not completed). Time limit. Reward.
The game enforces these, picking the rewards and putting collateral in escrow when the mission is created. The content of the mission is to be retrieved either from a “mission container” (a new type of container dedicated to hauling missions, think of it as a mailbox) or from a market container. It is then stored as a package with the content hidden for the mission responder. (Opening the package voids the mission and the collateral is paid.) The package can be retrieved or delivered by interacting directly with the associated container (via context-menu entries) or within a 2km range by using the controls on the interface.

Failing a mission can occur if:
 
The responder does not deliver within the given time frame (including if the package is destroyed). The package is opened by either the responder or someone else (i.e. pirates). The destruction of the destination container does not fail the mission. Instead, the mission responder can keep the package and open it without penalty; however, this means the mission cannot be completed anymore.
  CAVEAT EMPTOR

What is important to remember is that negotiations about rewards, or even the job description and purpose, are entirely declarative and non-binding. It is there as a statement, made clear with various warnings and “Are you sure?” windows.
 
There’s often an element of danger involved when doing business. For some, the lure of pulling one over on an unsuspecting stranger has an even larger allure than the money to be made. Sure, you can scam sweet, trusting little lambs for a time, but eventually you’ll be the one to pay the price. Both the Job Forum and the Mission system have the possibility to rate the interaction for the issuer and the responder. Scores between 0 and 5 are attached to players as responders or issuers of missions (both formal and jobs), which will help to identify and potentially weed out scammers.
 
YOUR FIRST MISSION STARTS HERE

Your mission now, should you choose to accept it, is to head over to this section of the forums to share your thoughts about this devblog. Which do you anticipate doing the most: creating missions, doing missions, or pirating missions?

"As we ramp up for the next Dual Universe update"
right on queue
 
I was wondering where is the rest of the devblog as it seems it's incomplete 
 
So if I get his correct, the mission system wil take several patches to roll out, starting with hauling.. That begs the question, will NQ plan to actually have the mission system done by the time they "release" as it feels like this wil be something that gets shoved in, ticked off and then revisited sometime next year.