Megabosslord

Agreed.  It's an example of a problem which would have been best fixed at the time when it actually mattered.
 
If NQ is actually reading this, I'd take a DAC instead of mine ...

At this point there's really not anything NQ can do to make up for the lost progress that having a sanctuary tile would have provided during the bottleneck of the first few days.
 
It wouldn't have made a huge difference.  But it would have been nice to have it.

Why not? It's tax free and the only place with Natron surface rocks so I hear
 
Anyways, yeah it sucks but whether we get interactions from devs or not doesn't change how long it's going to take so why bother

NQ is again demonstrating a fundamental misunderstanding of player psychology. You can't force people into PVP zones when they don't have the tools to make a proper evaluation of the risks and rewards. People will always try to minimize their risk and maximize the reward, but PVP is such a black box for most players that few are willing to risk what is probably the only mining ship they have against a threat they don't understand for a potential reward they cannot estimate. Why would someone go out solo in a ship that is probably completely helpless against pirates, spend up to an hour hunting down an asteroid only to find that the aforementioned pirates have been waiting there to pick them off the moment they get within range? What are the odds of that happening? I don't know! That's the whole point! I don't have enough information to calculate the risks or the rewards and the cost of a miscalculation is my whole ship being destroyed in an instant.
 
A basic asteroid in the safe zone might not make you rich, but it won't cost you your new ship unless you're a bad pilot. I'm aware that there are tricks players use (which I will not describe here) to find asteroids without quite as much risk. However, pirates will eventually adapt to that and once they do, the only rational choice players will be able to make is to join an org with mining ops well protected enough to run off or destroy any pirates that come by. Before long, large orgs will have it so that they're in a PVP zone but are at no risk of actual PVP (losses anyway) while small orgs and solo players are largely stuck sucking overcrowded rocks in horrific lag for what will soon become a chump change reward until they finally get sick of it and either join a larger org or quit entirely.
 
And don't get me wrong: large, organized orgs were always going to get access to the best content anyway, but joining up with them shouldn't be the ONLY way to do it; not in a game that's advertised as allowing people to play however they want.

Think this is on the same level as "you will get your gifts at launch"  STU? Pets? AVA? Larger cores? player markets?

Same video Deckard had said "Not ready for launch." when referencing other features. And IMHO those 4 words shouldn't be next together in any fashion during your games launch announcement. 
 
We know the game wasn't ready for launch, the devs know it wasn't ready despite the cognitive dissonance brought on by management forcing a launch and stating it was ready. 
 
And announcing a feature during your launch announcement for launch... and then quietly stating in a post it won't be ready for launch before... launch, while also stating its ready for launch. Sorta set the tone for me going into launch. 
 
Assuming NQ won't talk about any new features till they're ready for release at this point to avoid the creation of expectations that they could potentially fail to meet.
 
With more funding and a larger team with a more diverse skill set and this game can still be amazing. I just hope NQ and management can dig deep to give it the resources needed to be what it can be with the right TLC. 

Yep, promisses made are broken again and already i have i think 50 to 100 bp from past builds all right for the scrapper

We don't even have building to strive for. Our structures were wiped. Our BPs can't be placed again because they reneged on core snapping and stealth nerfed building height. NQ have repeatedly griefed us on even this. 

Too late to avoid it being a slap in the face... but I could go for stopping after ten slaps in the face.
 
BTW, I did finally get a response to my ticket on this, but it was just "we're working on it." Too little too late.

Indeed  @NQ-Admin STU When?
 
And to be clear, I already have mine but these missing STU and other missing "gifts" are just symptomic and really hurt part of the community.
This has to be fixed and there is no excuse to have to wait over 2 weeks.
the main reason the value is already lower for these STU is because they are not yet placed, the STU i was able to place provided me with enough materials to be able to craft my first Static L core yesterday, bit slow i know but i am helping out my friends who are less lucky.
 
Just make this a priority instead of a slap in the face of contributors.
 

It doesn't take 2 weeks to figure out who got a STU and who didn't, unless they're not really trying.

Let's set aside for a moment that wiping beta player constructs at launch was always unfair, given past commitments. NQ have now heaped insult on injury with a number of stealth nerfs at launch:
 
Alioth T2 Distribution: 
I did 80 territory scans on Alioth at a ~3 tile spacing and found zero T2. None at all. Zip. Nada. No T2 - after spending 3 days building the XL assembler and scanner. This is a broken gameplay loop. Combined with the removal of Malachite from Alioth, the stealth nerf of ore distribution on Alioth resulted in a week of wasted effort. Forcing effort with no payoff is not gameplay. 
 
If NQ had been transparent with us before launch, said they were going to nerf T2 on Alioth, I wouldn't have wasted that critical week. I would also have rebuilt my base before launch so the BP wasn't made of 500,000M3 of Copper. Now, to deploy my BP I have to swap copper for another honeycomb, and then go back and untangle where the new material has blended with the same material already in the BP. More rework, on top of the wasted time.
 
1000m Build Height: 
This was self-evidently dumb. By choosing a 1000m cap instead of 1128m, it's impossible to build a 1000m AGG pad without placing your foundation core at an exactly multiple of 128m (since you won't be able to place the top core if there is less than a 128m gap.) Even then, you can put nothing on your 1000m pad, no elements, no structure. And you have to either use smaller cores for your top layer (increasing server load) or build your base from the top core, down - which means tall temporary scaffold structures first to place top cores and work back down - while others complain about griefing the entire time. 
 
A large number of pre-launch bases had AGG pads at or slightly above 1000m. All these pre-launch base BPs are now bricked.
 
This misstep demonstrates a fundamental ignorance of their game's own mechanics by devs, and poor understandng of players. To make matters worse, the change wasn't even included in patch notes. The only place it was mentioned - just wks before launch - was in 'Ask Aphelia #12. Few players had any opportunity to fix their builds before launch. This mistake (1000m vs 1128m) would easily have been picked up if players had been warned.
 
In summary, not only did NQ reneg on prior commitments to honour our builds in their 'persistent' universe - the only compensation being retained blueprints - they went on to stealth nerf the BPs we kept. 
 
[EDIT: Because this rule is not yet being enforced, and it is still possible to place a core above 1000m, this will create even more pain for players uncertain or unaware of the rule - should NQ decide to delete structures after they are built. And for as long as the rule is unclear, it is impossible to safely place the foundations of a tall structure.]
 

 
Missing STUs for 'Contributors' (and Surface Natron):
By making Sanctuary the only place with surface natron near Alioth, Alpha contributors already had a significant advantage at launch - since natron is needed to make many popular elements: screens, lights etc.. NQ then messed up further, by jacking up the distribution of STUs meaning only some Contributors received them. ~10 days later, this still has not been fixed. This means a small number of players, purely by chance, have the only access to surface natron near Alioth.
 
HTML/SVG nerf and Indiscriminate LUA Changes: 
The disabling of HTML screens was long rumoured, but took so long to be done it appeared to have been abandoned. Waiting till launch to tell players all SVGs and HTML are also now bricked is also poor form and counter-productive. Because a large number of ship BPs from pre-launch contain screens using HTML, and virtually every factory monitoring set-up, any player flying these ships or running these factories, will now simply go to settings and re-enable HTML, to be able to play the game - undermining the point of the exercise to phase out HTML, and prolonging the inevitable pain and frustration when it is finally done. This pain is now unavoidable given the original misstep of building a new API with zero compatibility with HTML/SVG. (The new API should always have been implemented in a way to minimise the effort of reworking existing content for players - rather than forcing ground up rebuilds of all screens. Better still, existing content should ideally have been ported on behalf of players.)
 
Combine this with the frivolous renaming of a number of LUA cmds, additional rework has also been created for players to reimplement scripts written before launch - for no apparent reason. 
 
STILL No Static BP Placement Snapping!: 
We asked for this in the Alpha Trello 3 yrs ago. It was poorly implemented on day one - snapping new cores only. Hundreds of players have asked for it to be fixed for static BPs over the years. It never made sense that new cores snap into place, but static BPs work of a bizarre raycast that doesn't even align with the player camera and - annoyingly - nudges by 2 voxels instead of 1. This feature was already long overdue, but now made more critical since it is essential to redeploying any mult-core construct after the wipe. Finally... finally, it was coming! In the launch livestream it was promised for launch here, at timecode 35:38:
 
Instead, we now learn this was skipped, rendering all multi-core static construct blueprints useless. 
 
Summary:
 
- Forcing players to constantly rework their builds is not gameplay.
- Reworking existing content is a poor proxy for new gameplay loops.
- Player input is invaluable. 
- Last minute, uncommunicated changes rarely if ever have a positive outcome.  
 
The culture at NQ of disregarding the time and effort of players, and lack of consideration of impacts on our gameplay, is worrisome. More worrisome, is the tendency to continuously rework existing content - mechanics, terrain, boolean noise - rather than develop significant new features, many of these features requested years ago. NQ are still missing the winning strategy of successful 'player generated content' franchises like Minecraft, where the focus of the first several years was on adding new gameplay loops - as opposed to continuously reworking existing ones. Reworking existing content decays player satisfaction by forcing the constant rework of our own builds. And making changes by stealth only magnifies the problem.
 
Until this is understood, the future of this franchise is fraught. 

We don't even have building to strive for. Our structures were wiped. Our BPs can't be placed again because they reneged on core snapping and stealth nerfed building height. NQ have repeatedly griefed us on even this. 

The whole premise of “entirely player driven and built” is a laughing stock.  This was actually a reply deep in a thread somewhere so I just thought I’d dig it out and post it here. Sorry if you’ve read this already. 
 
bots control our hex-rent. Bots control our schematics. Bots control our sales taxes. Bots hand out and receive missions. Bots sell pretty much everything anyone needs. Bots buy stupid almost unlimited amounts of ore and bots hand out a daily stipend. And bots control whether or not we can fire weapons. 
 
what is there actually left to play and strive for other than building?
 
why is there no energy required to run anything? Why is there no oxygen requirements for our habitats?
why is there no food or farming? 
 
why are there no threatening box life forms that raid our camps?
 
why are there no mysteries beyond a few lowest possible effort alien cores?
 


 
what an absolute joke. 

As poor a source of information as this forum can be, it’s still what I come here for. Thanks for the info. It is useful.

Accurate.

Not to mention; no FPS or atmospheric combat ... no VOIP ... breaking the economy by selling all of the basic parts so nobody needs to craft them, buying ore, and selling super OP ships at the beginning ....

Yep. NQ managed to FUBAR and SNAFU in the same release. Good job.
 
Not only do I not have my STU, but they haven't even acknowledged the two tickets I've filed about it. Maybe I should start filing a new ticket every hour until they do.

It's msoul, so this is expected. Really not worth replying with more than a single line.

You missed the point on most of this. 

- Removing Malachite from Alioth (leaving scant T2) isn’t a ‘belief’. 
 
- Bricking AGG platforms, if intentional,  is even more a stealth nerf.
 
- It doesn’t take 2 wks to figure out who your contributors are and whether they got their STU. 
 
- Read it again. Forcing players to go re-enable HTML in settings solves nothing. 

- Exactly. They said it would be done for launch, took our money, then kicked it down the road. Your point?
 
As for the audience for this post, I’d love to think devs actually listen but 3 yrs of evidence now suggests otherwise.
 
There are several things here most players won’t have discovered yet, and in the absence of clear comms from NQ, no comprehensive change logs, information scattered across a variety of streams, I’m trying to save fellow players from wasting days making the same disappointing discoveries. 

Let's set aside for a moment that wiping beta player constructs at launch was always unfair, given past commitments. NQ have now heaped insult on injury with a number of stealth nerfs at launch:
 
Alioth T2 Distribution: 
I did 80 territory scans on Alioth at a ~3 tile spacing and found zero T2. None at all. Zip. Nada. No T2 - after spending 3 days building the XL assembler and scanner. This is a broken gameplay loop. Combined with the removal of Malachite from Alioth, the stealth nerf of ore distribution on Alioth resulted in a week of wasted effort. Forcing effort with no payoff is not gameplay. 
 
If NQ had been transparent with us before launch, said they were going to nerf T2 on Alioth, I wouldn't have wasted that critical week. I would also have rebuilt my base before launch so the BP wasn't made of 500,000M3 of Copper. Now, to deploy my BP I have to swap copper for another honeycomb, and then go back and untangle where the new material has blended with the same material already in the BP. More rework, on top of the wasted time.
 
1000m Build Height: 
This was self-evidently dumb. By choosing a 1000m cap instead of 1128m, it's impossible to build a 1000m AGG pad without placing your foundation core at an exactly multiple of 128m (since you won't be able to place the top core if there is less than a 128m gap.) Even then, you can put nothing on your 1000m pad, no elements, no structure. And you have to either use smaller cores for your top layer (increasing server load) or build your base from the top core, down - which means tall temporary scaffold structures first to place top cores and work back down - while others complain about griefing the entire time. 
 
A large number of pre-launch bases had AGG pads at or slightly above 1000m. All these pre-launch base BPs are now bricked.
 
This misstep demonstrates a fundamental ignorance of their game's own mechanics by devs, and poor understandng of players. To make matters worse, the change wasn't even included in patch notes. The only place it was mentioned - just wks before launch - was in 'Ask Aphelia #12. Few players had any opportunity to fix their builds before launch. This mistake (1000m vs 1128m) would easily have been picked up if players had been warned.
 
In summary, not only did NQ reneg on prior commitments to honour our builds in their 'persistent' universe - the only compensation being retained blueprints - they went on to stealth nerf the BPs we kept. 
 
[EDIT: Because this rule is not yet being enforced, and it is still possible to place a core above 1000m, this will create even more pain for players uncertain or unaware of the rule - should NQ decide to delete structures after they are built. And for as long as the rule is unclear, it is impossible to safely place the foundations of a tall structure.]
 

 
Missing STUs for 'Contributors' (and Surface Natron):
By making Sanctuary the only place with surface natron near Alioth, Alpha contributors already had a significant advantage at launch - since natron is needed to make many popular elements: screens, lights etc.. NQ then messed up further, by jacking up the distribution of STUs meaning only some Contributors received them. ~10 days later, this still has not been fixed. This means a small number of players, purely by chance, have the only access to surface natron near Alioth.
 
HTML/SVG nerf and Indiscriminate LUA Changes: 
The disabling of HTML screens was long rumoured, but took so long to be done it appeared to have been abandoned. Waiting till launch to tell players all SVGs and HTML are also now bricked is also poor form and counter-productive. Because a large number of ship BPs from pre-launch contain screens using HTML, and virtually every factory monitoring set-up, any player flying these ships or running these factories, will now simply go to settings and re-enable HTML, to be able to play the game - undermining the point of the exercise to phase out HTML, and prolonging the inevitable pain and frustration when it is finally done. This pain is now unavoidable given the original misstep of building a new API with zero compatibility with HTML/SVG. (The new API should always have been implemented in a way to minimise the effort of reworking existing content for players - rather than forcing ground up rebuilds of all screens. Better still, existing content should ideally have been ported on behalf of players.)
 
Combine this with the frivolous renaming of a number of LUA cmds, additional rework has also been created for players to reimplement scripts written before launch - for no apparent reason. 
 
STILL No Static BP Placement Snapping!: 
We asked for this in the Alpha Trello 3 yrs ago. It was poorly implemented on day one - snapping new cores only. Hundreds of players have asked for it to be fixed for static BPs over the years. It never made sense that new cores snap into place, but static BPs work of a bizarre raycast that doesn't even align with the player camera and - annoyingly - nudges by 2 voxels instead of 1. This feature was already long overdue, but now made more critical since it is essential to redeploying any mult-core construct after the wipe. Finally... finally, it was coming! In the launch livestream it was promised for launch here, at timecode 35:38:
 
Instead, we now learn this was skipped, rendering all multi-core static construct blueprints useless. 
 
Summary:
 
- Forcing players to constantly rework their builds is not gameplay.
- Reworking existing content is a poor proxy for new gameplay loops.
- Player input is invaluable. 
- Last minute, uncommunicated changes rarely if ever have a positive outcome.  
 
The culture at NQ of disregarding the time and effort of players, and lack of consideration of impacts on our gameplay, is worrisome. More worrisome, is the tendency to continuously rework existing content - mechanics, terrain, boolean noise - rather than develop significant new features, many of these features requested years ago. NQ are still missing the winning strategy of successful 'player generated content' franchises like Minecraft, where the focus of the first several years was on adding new gameplay loops - as opposed to continuously reworking existing ones. Reworking existing content decays player satisfaction by forcing the constant rework of our own builds. And making changes by stealth only magnifies the problem.
 
Until this is understood, the future of this franchise is fraught. 

Let's set aside for a moment that wiping beta player constructs at launch was always unfair, given past commitments. NQ have now heaped insult on injury with a number of stealth nerfs at launch:
 
Alioth T2 Distribution: 
I did 80 territory scans on Alioth at a ~3 tile spacing and found zero T2. None at all. Zip. Nada. No T2 - after spending 3 days building the XL assembler and scanner. This is a broken gameplay loop. Combined with the removal of Malachite from Alioth, the stealth nerf of ore distribution on Alioth resulted in a week of wasted effort. Forcing effort with no payoff is not gameplay. 
 
If NQ had been transparent with us before launch, said they were going to nerf T2 on Alioth, I wouldn't have wasted that critical week. I would also have rebuilt my base before launch so the BP wasn't made of 500,000M3 of Copper. Now, to deploy my BP I have to swap copper for another honeycomb, and then go back and untangle where the new material has blended with the same material already in the BP. More rework, on top of the wasted time.
 
1000m Build Height: 
This was self-evidently dumb. By choosing a 1000m cap instead of 1128m, it's impossible to build a 1000m AGG pad without placing your foundation core at an exactly multiple of 128m (since you won't be able to place the top core if there is less than a 128m gap.) Even then, you can put nothing on your 1000m pad, no elements, no structure. And you have to either use smaller cores for your top layer (increasing server load) or build your base from the top core, down - which means tall temporary scaffold structures first to place top cores and work back down - while others complain about griefing the entire time. 
 
A large number of pre-launch bases had AGG pads at or slightly above 1000m. All these pre-launch base BPs are now bricked.
 
This misstep demonstrates a fundamental ignorance of their game's own mechanics by devs, and poor understandng of players. To make matters worse, the change wasn't even included in patch notes. The only place it was mentioned - just wks before launch - was in 'Ask Aphelia #12. Few players had any opportunity to fix their builds before launch. This mistake (1000m vs 1128m) would easily have been picked up if players had been warned.
 
In summary, not only did NQ reneg on prior commitments to honour our builds in their 'persistent' universe - the only compensation being retained blueprints - they went on to stealth nerf the BPs we kept. 
 
[EDIT: Because this rule is not yet being enforced, and it is still possible to place a core above 1000m, this will create even more pain for players uncertain or unaware of the rule - should NQ decide to delete structures after they are built. And for as long as the rule is unclear, it is impossible to safely place the foundations of a tall structure.]
 

 
Missing STUs for 'Contributors' (and Surface Natron):
By making Sanctuary the only place with surface natron near Alioth, Alpha contributors already had a significant advantage at launch - since natron is needed to make many popular elements: screens, lights etc.. NQ then messed up further, by jacking up the distribution of STUs meaning only some Contributors received them. ~10 days later, this still has not been fixed. This means a small number of players, purely by chance, have the only access to surface natron near Alioth.
 
HTML/SVG nerf and Indiscriminate LUA Changes: 
The disabling of HTML screens was long rumoured, but took so long to be done it appeared to have been abandoned. Waiting till launch to tell players all SVGs and HTML are also now bricked is also poor form and counter-productive. Because a large number of ship BPs from pre-launch contain screens using HTML, and virtually every factory monitoring set-up, any player flying these ships or running these factories, will now simply go to settings and re-enable HTML, to be able to play the game - undermining the point of the exercise to phase out HTML, and prolonging the inevitable pain and frustration when it is finally done. This pain is now unavoidable given the original misstep of building a new API with zero compatibility with HTML/SVG. (The new API should always have been implemented in a way to minimise the effort of reworking existing content for players - rather than forcing ground up rebuilds of all screens. Better still, existing content should ideally have been ported on behalf of players.)
 
Combine this with the frivolous renaming of a number of LUA cmds, additional rework has also been created for players to reimplement scripts written before launch - for no apparent reason. 
 
STILL No Static BP Placement Snapping!: 
We asked for this in the Alpha Trello 3 yrs ago. It was poorly implemented on day one - snapping new cores only. Hundreds of players have asked for it to be fixed for static BPs over the years. It never made sense that new cores snap into place, but static BPs work of a bizarre raycast that doesn't even align with the player camera and - annoyingly - nudges by 2 voxels instead of 1. This feature was already long overdue, but now made more critical since it is essential to redeploying any mult-core construct after the wipe. Finally... finally, it was coming! In the launch livestream it was promised for launch here, at timecode 35:38:
 
Instead, we now learn this was skipped, rendering all multi-core static construct blueprints useless. 
 
Summary:
 
- Forcing players to constantly rework their builds is not gameplay.
- Reworking existing content is a poor proxy for new gameplay loops.
- Player input is invaluable. 
- Last minute, uncommunicated changes rarely if ever have a positive outcome.  
 
The culture at NQ of disregarding the time and effort of players, and lack of consideration of impacts on our gameplay, is worrisome. More worrisome, is the tendency to continuously rework existing content - mechanics, terrain, boolean noise - rather than develop significant new features, many of these features requested years ago. NQ are still missing the winning strategy of successful 'player generated content' franchises like Minecraft, where the focus of the first several years was on adding new gameplay loops - as opposed to continuously reworking existing ones. Reworking existing content decays player satisfaction by forcing the constant rework of our own builds. And making changes by stealth only magnifies the problem.
 
Until this is understood, the future of this franchise is fraught. 

Let's set aside for a moment that wiping beta player constructs at launch was always unfair, given past commitments. NQ have now heaped insult on injury with a number of stealth nerfs at launch:
 
Alioth T2 Distribution: 
I did 80 territory scans on Alioth at a ~3 tile spacing and found zero T2. None at all. Zip. Nada. No T2 - after spending 3 days building the XL assembler and scanner. This is a broken gameplay loop. Combined with the removal of Malachite from Alioth, the stealth nerf of ore distribution on Alioth resulted in a week of wasted effort. Forcing effort with no payoff is not gameplay. 
 
If NQ had been transparent with us before launch, said they were going to nerf T2 on Alioth, I wouldn't have wasted that critical week. I would also have rebuilt my base before launch so the BP wasn't made of 500,000M3 of Copper. Now, to deploy my BP I have to swap copper for another honeycomb, and then go back and untangle where the new material has blended with the same material already in the BP. More rework, on top of the wasted time.
 
1000m Build Height: 
This was self-evidently dumb. By choosing a 1000m cap instead of 1128m, it's impossible to build a 1000m AGG pad without placing your foundation core at an exactly multiple of 128m (since you won't be able to place the top core if there is less than a 128m gap.) Even then, you can put nothing on your 1000m pad, no elements, no structure. And you have to either use smaller cores for your top layer (increasing server load) or build your base from the top core, down - which means tall temporary scaffold structures first to place top cores and work back down - while others complain about griefing the entire time. 
 
A large number of pre-launch bases had AGG pads at or slightly above 1000m. All these pre-launch base BPs are now bricked.
 
This misstep demonstrates a fundamental ignorance of their game's own mechanics by devs, and poor understandng of players. To make matters worse, the change wasn't even included in patch notes. The only place it was mentioned - just wks before launch - was in 'Ask Aphelia #12. Few players had any opportunity to fix their builds before launch. This mistake (1000m vs 1128m) would easily have been picked up if players had been warned.
 
In summary, not only did NQ reneg on prior commitments to honour our builds in their 'persistent' universe - the only compensation being retained blueprints - they went on to stealth nerf the BPs we kept. 
 
[EDIT: Because this rule is not yet being enforced, and it is still possible to place a core above 1000m, this will create even more pain for players uncertain or unaware of the rule - should NQ decide to delete structures after they are built. And for as long as the rule is unclear, it is impossible to safely place the foundations of a tall structure.]
 

 
Missing STUs for 'Contributors' (and Surface Natron):
By making Sanctuary the only place with surface natron near Alioth, Alpha contributors already had a significant advantage at launch - since natron is needed to make many popular elements: screens, lights etc.. NQ then messed up further, by jacking up the distribution of STUs meaning only some Contributors received them. ~10 days later, this still has not been fixed. This means a small number of players, purely by chance, have the only access to surface natron near Alioth.
 
HTML/SVG nerf and Indiscriminate LUA Changes: 
The disabling of HTML screens was long rumoured, but took so long to be done it appeared to have been abandoned. Waiting till launch to tell players all SVGs and HTML are also now bricked is also poor form and counter-productive. Because a large number of ship BPs from pre-launch contain screens using HTML, and virtually every factory monitoring set-up, any player flying these ships or running these factories, will now simply go to settings and re-enable HTML, to be able to play the game - undermining the point of the exercise to phase out HTML, and prolonging the inevitable pain and frustration when it is finally done. This pain is now unavoidable given the original misstep of building a new API with zero compatibility with HTML/SVG. (The new API should always have been implemented in a way to minimise the effort of reworking existing content for players - rather than forcing ground up rebuilds of all screens. Better still, existing content should ideally have been ported on behalf of players.)
 
Combine this with the frivolous renaming of a number of LUA cmds, additional rework has also been created for players to reimplement scripts written before launch - for no apparent reason. 
 
STILL No Static BP Placement Snapping!: 
We asked for this in the Alpha Trello 3 yrs ago. It was poorly implemented on day one - snapping new cores only. Hundreds of players have asked for it to be fixed for static BPs over the years. It never made sense that new cores snap into place, but static BPs work of a bizarre raycast that doesn't even align with the player camera and - annoyingly - nudges by 2 voxels instead of 1. This feature was already long overdue, but now made more critical since it is essential to redeploying any mult-core construct after the wipe. Finally... finally, it was coming! In the launch livestream it was promised for launch here, at timecode 35:38:
 
Instead, we now learn this was skipped, rendering all multi-core static construct blueprints useless. 
 
Summary:
 
- Forcing players to constantly rework their builds is not gameplay.
- Reworking existing content is a poor proxy for new gameplay loops.
- Player input is invaluable. 
- Last minute, uncommunicated changes rarely if ever have a positive outcome.  
 
The culture at NQ of disregarding the time and effort of players, and lack of consideration of impacts on our gameplay, is worrisome. More worrisome, is the tendency to continuously rework existing content - mechanics, terrain, boolean noise - rather than develop significant new features, many of these features requested years ago. NQ are still missing the winning strategy of successful 'player generated content' franchises like Minecraft, where the focus of the first several years was on adding new gameplay loops - as opposed to continuously reworking existing ones. Reworking existing content decays player satisfaction by forcing the constant rework of our own builds. And making changes by stealth only magnifies the problem.
 
Until this is understood, the future of this franchise is fraught. 

Let's set aside for a moment that wiping beta player constructs at launch was always unfair, given past commitments. NQ have now heaped insult on injury with a number of stealth nerfs at launch:
 
Alioth T2 Distribution: 
I did 80 territory scans on Alioth at a ~3 tile spacing and found zero T2. None at all. Zip. Nada. No T2 - after spending 3 days building the XL assembler and scanner. This is a broken gameplay loop. Combined with the removal of Malachite from Alioth, the stealth nerf of ore distribution on Alioth resulted in a week of wasted effort. Forcing effort with no payoff is not gameplay. 
 
If NQ had been transparent with us before launch, said they were going to nerf T2 on Alioth, I wouldn't have wasted that critical week. I would also have rebuilt my base before launch so the BP wasn't made of 500,000M3 of Copper. Now, to deploy my BP I have to swap copper for another honeycomb, and then go back and untangle where the new material has blended with the same material already in the BP. More rework, on top of the wasted time.
 
1000m Build Height: 
This was self-evidently dumb. By choosing a 1000m cap instead of 1128m, it's impossible to build a 1000m AGG pad without placing your foundation core at an exactly multiple of 128m (since you won't be able to place the top core if there is less than a 128m gap.) Even then, you can put nothing on your 1000m pad, no elements, no structure. And you have to either use smaller cores for your top layer (increasing server load) or build your base from the top core, down - which means tall temporary scaffold structures first to place top cores and work back down - while others complain about griefing the entire time. 
 
A large number of pre-launch bases had AGG pads at or slightly above 1000m. All these pre-launch base BPs are now bricked.
 
This misstep demonstrates a fundamental ignorance of their game's own mechanics by devs, and poor understandng of players. To make matters worse, the change wasn't even included in patch notes. The only place it was mentioned - just wks before launch - was in 'Ask Aphelia #12. Few players had any opportunity to fix their builds before launch. This mistake (1000m vs 1128m) would easily have been picked up if players had been warned.
 
In summary, not only did NQ reneg on prior commitments to honour our builds in their 'persistent' universe - the only compensation being retained blueprints - they went on to stealth nerf the BPs we kept. 
 
[EDIT: Because this rule is not yet being enforced, and it is still possible to place a core above 1000m, this will create even more pain for players uncertain or unaware of the rule - should NQ decide to delete structures after they are built. And for as long as the rule is unclear, it is impossible to safely place the foundations of a tall structure.]
 

 
Missing STUs for 'Contributors' (and Surface Natron):
By making Sanctuary the only place with surface natron near Alioth, Alpha contributors already had a significant advantage at launch - since natron is needed to make many popular elements: screens, lights etc.. NQ then messed up further, by jacking up the distribution of STUs meaning only some Contributors received them. ~10 days later, this still has not been fixed. This means a small number of players, purely by chance, have the only access to surface natron near Alioth.
 
HTML/SVG nerf and Indiscriminate LUA Changes: 
The disabling of HTML screens was long rumoured, but took so long to be done it appeared to have been abandoned. Waiting till launch to tell players all SVGs and HTML are also now bricked is also poor form and counter-productive. Because a large number of ship BPs from pre-launch contain screens using HTML, and virtually every factory monitoring set-up, any player flying these ships or running these factories, will now simply go to settings and re-enable HTML, to be able to play the game - undermining the point of the exercise to phase out HTML, and prolonging the inevitable pain and frustration when it is finally done. This pain is now unavoidable given the original misstep of building a new API with zero compatibility with HTML/SVG. (The new API should always have been implemented in a way to minimise the effort of reworking existing content for players - rather than forcing ground up rebuilds of all screens. Better still, existing content should ideally have been ported on behalf of players.)
 
Combine this with the frivolous renaming of a number of LUA cmds, additional rework has also been created for players to reimplement scripts written before launch - for no apparent reason. 
 
STILL No Static BP Placement Snapping!: 
We asked for this in the Alpha Trello 3 yrs ago. It was poorly implemented on day one - snapping new cores only. Hundreds of players have asked for it to be fixed for static BPs over the years. It never made sense that new cores snap into place, but static BPs work of a bizarre raycast that doesn't even align with the player camera and - annoyingly - nudges by 2 voxels instead of 1. This feature was already long overdue, but now made more critical since it is essential to redeploying any mult-core construct after the wipe. Finally... finally, it was coming! In the launch livestream it was promised for launch here, at timecode 35:38:
 
Instead, we now learn this was skipped, rendering all multi-core static construct blueprints useless. 
 
Summary:
 
- Forcing players to constantly rework their builds is not gameplay.
- Reworking existing content is a poor proxy for new gameplay loops.
- Player input is invaluable. 
- Last minute, uncommunicated changes rarely if ever have a positive outcome.  
 
The culture at NQ of disregarding the time and effort of players, and lack of consideration of impacts on our gameplay, is worrisome. More worrisome, is the tendency to continuously rework existing content - mechanics, terrain, boolean noise - rather than develop significant new features, many of these features requested years ago. NQ are still missing the winning strategy of successful 'player generated content' franchises like Minecraft, where the focus of the first several years was on adding new gameplay loops - as opposed to continuously reworking existing ones. Reworking existing content decays player satisfaction by forcing the constant rework of our own builds. And making changes by stealth only magnifies the problem.
 
Until this is understood, the future of this franchise is fraught. 

Let's set aside for a moment that wiping beta player constructs at launch was always unfair, given past commitments. NQ have now heaped insult on injury with a number of stealth nerfs at launch:
 
Alioth T2 Distribution: 
I did 80 territory scans on Alioth at a ~3 tile spacing and found zero T2. None at all. Zip. Nada. No T2 - after spending 3 days building the XL assembler and scanner. This is a broken gameplay loop. Combined with the removal of Malachite from Alioth, the stealth nerf of ore distribution on Alioth resulted in a week of wasted effort. Forcing effort with no payoff is not gameplay. 
 
If NQ had been transparent with us before launch, said they were going to nerf T2 on Alioth, I wouldn't have wasted that critical week. I would also have rebuilt my base before launch so the BP wasn't made of 500,000M3 of Copper. Now, to deploy my BP I have to swap copper for another honeycomb, and then go back and untangle where the new material has blended with the same material already in the BP. More rework, on top of the wasted time.
 
1000m Build Height: 
This was self-evidently dumb. By choosing a 1000m cap instead of 1128m, it's impossible to build a 1000m AGG pad without placing your foundation core at an exactly multiple of 128m (since you won't be able to place the top core if there is less than a 128m gap.) Even then, you can put nothing on your 1000m pad, no elements, no structure. And you have to either use smaller cores for your top layer (increasing server load) or build your base from the top core, down - which means tall temporary scaffold structures first to place top cores and work back down - while others complain about griefing the entire time. 
 
A large number of pre-launch bases had AGG pads at or slightly above 1000m. All these pre-launch base BPs are now bricked.
 
This misstep demonstrates a fundamental ignorance of their game's own mechanics by devs, and poor understandng of players. To make matters worse, the change wasn't even included in patch notes. The only place it was mentioned - just wks before launch - was in 'Ask Aphelia #12. Few players had any opportunity to fix their builds before launch. This mistake (1000m vs 1128m) would easily have been picked up if players had been warned.
 
In summary, not only did NQ reneg on prior commitments to honour our builds in their 'persistent' universe - the only compensation being retained blueprints - they went on to stealth nerf the BPs we kept. 
 
[EDIT: Because this rule is not yet being enforced, and it is still possible to place a core above 1000m, this will create even more pain for players uncertain or unaware of the rule - should NQ decide to delete structures after they are built. And for as long as the rule is unclear, it is impossible to safely place the foundations of a tall structure.]
 

 
Missing STUs for 'Contributors' (and Surface Natron):
By making Sanctuary the only place with surface natron near Alioth, Alpha contributors already had a significant advantage at launch - since natron is needed to make many popular elements: screens, lights etc.. NQ then messed up further, by jacking up the distribution of STUs meaning only some Contributors received them. ~10 days later, this still has not been fixed. This means a small number of players, purely by chance, have the only access to surface natron near Alioth.
 
HTML/SVG nerf and Indiscriminate LUA Changes: 
The disabling of HTML screens was long rumoured, but took so long to be done it appeared to have been abandoned. Waiting till launch to tell players all SVGs and HTML are also now bricked is also poor form and counter-productive. Because a large number of ship BPs from pre-launch contain screens using HTML, and virtually every factory monitoring set-up, any player flying these ships or running these factories, will now simply go to settings and re-enable HTML, to be able to play the game - undermining the point of the exercise to phase out HTML, and prolonging the inevitable pain and frustration when it is finally done. This pain is now unavoidable given the original misstep of building a new API with zero compatibility with HTML/SVG. (The new API should always have been implemented in a way to minimise the effort of reworking existing content for players - rather than forcing ground up rebuilds of all screens. Better still, existing content should ideally have been ported on behalf of players.)
 
Combine this with the frivolous renaming of a number of LUA cmds, additional rework has also been created for players to reimplement scripts written before launch - for no apparent reason. 
 
STILL No Static BP Placement Snapping!: 
We asked for this in the Alpha Trello 3 yrs ago. It was poorly implemented on day one - snapping new cores only. Hundreds of players have asked for it to be fixed for static BPs over the years. It never made sense that new cores snap into place, but static BPs work of a bizarre raycast that doesn't even align with the player camera and - annoyingly - nudges by 2 voxels instead of 1. This feature was already long overdue, but now made more critical since it is essential to redeploying any mult-core construct after the wipe. Finally... finally, it was coming! In the launch livestream it was promised for launch here, at timecode 35:38:
 
Instead, we now learn this was skipped, rendering all multi-core static construct blueprints useless. 
 
Summary:
 
- Forcing players to constantly rework their builds is not gameplay.
- Reworking existing content is a poor proxy for new gameplay loops.
- Player input is invaluable. 
- Last minute, uncommunicated changes rarely if ever have a positive outcome.  
 
The culture at NQ of disregarding the time and effort of players, and lack of consideration of impacts on our gameplay, is worrisome. More worrisome, is the tendency to continuously rework existing content - mechanics, terrain, boolean noise - rather than develop significant new features, many of these features requested years ago. NQ are still missing the winning strategy of successful 'player generated content' franchises like Minecraft, where the focus of the first several years was on adding new gameplay loops - as opposed to continuously reworking existing ones. Reworking existing content decays player satisfaction by forcing the constant rework of our own builds. And making changes by stealth only magnifies the problem.
 
Until this is understood, the future of this franchise is fraught. 

Let's set aside for a moment that wiping beta player constructs at launch was always unfair, given past commitments. NQ have now heaped insult on injury with a number of stealth nerfs at launch:
 
Alioth T2 Distribution: 
I did 80 territory scans on Alioth at a ~3 tile spacing and found zero T2. None at all. Zip. Nada. No T2 - after spending 3 days building the XL assembler and scanner. This is a broken gameplay loop. Combined with the removal of Malachite from Alioth, the stealth nerf of ore distribution on Alioth resulted in a week of wasted effort. Forcing effort with no payoff is not gameplay. 
 
If NQ had been transparent with us before launch, said they were going to nerf T2 on Alioth, I wouldn't have wasted that critical week. I would also have rebuilt my base before launch so the BP wasn't made of 500,000M3 of Copper. Now, to deploy my BP I have to swap copper for another honeycomb, and then go back and untangle where the new material has blended with the same material already in the BP. More rework, on top of the wasted time.
 
1000m Build Height: 
This was self-evidently dumb. By choosing a 1000m cap instead of 1128m, it's impossible to build a 1000m AGG pad without placing your foundation core at an exactly multiple of 128m (since you won't be able to place the top core if there is less than a 128m gap.) Even then, you can put nothing on your 1000m pad, no elements, no structure. And you have to either use smaller cores for your top layer (increasing server load) or build your base from the top core, down - which means tall temporary scaffold structures first to place top cores and work back down - while others complain about griefing the entire time. 
 
A large number of pre-launch bases had AGG pads at or slightly above 1000m. All these pre-launch base BPs are now bricked.
 
This misstep demonstrates a fundamental ignorance of their game's own mechanics by devs, and poor understandng of players. To make matters worse, the change wasn't even included in patch notes. The only place it was mentioned - just wks before launch - was in 'Ask Aphelia #12. Few players had any opportunity to fix their builds before launch. This mistake (1000m vs 1128m) would easily have been picked up if players had been warned.
 
In summary, not only did NQ reneg on prior commitments to honour our builds in their 'persistent' universe - the only compensation being retained blueprints - they went on to stealth nerf the BPs we kept. 
 
[EDIT: Because this rule is not yet being enforced, and it is still possible to place a core above 1000m, this will create even more pain for players uncertain or unaware of the rule - should NQ decide to delete structures after they are built. And for as long as the rule is unclear, it is impossible to safely place the foundations of a tall structure.]
 

 
Missing STUs for 'Contributors' (and Surface Natron):
By making Sanctuary the only place with surface natron near Alioth, Alpha contributors already had a significant advantage at launch - since natron is needed to make many popular elements: screens, lights etc.. NQ then messed up further, by jacking up the distribution of STUs meaning only some Contributors received them. ~10 days later, this still has not been fixed. This means a small number of players, purely by chance, have the only access to surface natron near Alioth.
 
HTML/SVG nerf and Indiscriminate LUA Changes: 
The disabling of HTML screens was long rumoured, but took so long to be done it appeared to have been abandoned. Waiting till launch to tell players all SVGs and HTML are also now bricked is also poor form and counter-productive. Because a large number of ship BPs from pre-launch contain screens using HTML, and virtually every factory monitoring set-up, any player flying these ships or running these factories, will now simply go to settings and re-enable HTML, to be able to play the game - undermining the point of the exercise to phase out HTML, and prolonging the inevitable pain and frustration when it is finally done. This pain is now unavoidable given the original misstep of building a new API with zero compatibility with HTML/SVG. (The new API should always have been implemented in a way to minimise the effort of reworking existing content for players - rather than forcing ground up rebuilds of all screens. Better still, existing content should ideally have been ported on behalf of players.)
 
Combine this with the frivolous renaming of a number of LUA cmds, additional rework has also been created for players to reimplement scripts written before launch - for no apparent reason. 
 
STILL No Static BP Placement Snapping!: 
We asked for this in the Alpha Trello 3 yrs ago. It was poorly implemented on day one - snapping new cores only. Hundreds of players have asked for it to be fixed for static BPs over the years. It never made sense that new cores snap into place, but static BPs work of a bizarre raycast that doesn't even align with the player camera and - annoyingly - nudges by 2 voxels instead of 1. This feature was already long overdue, but now made more critical since it is essential to redeploying any mult-core construct after the wipe. Finally... finally, it was coming! In the launch livestream it was promised for launch here, at timecode 35:38:
 
Instead, we now learn this was skipped, rendering all multi-core static construct blueprints useless. 
 
Summary:
 
- Forcing players to constantly rework their builds is not gameplay.
- Reworking existing content is a poor proxy for new gameplay loops.
- Player input is invaluable. 
- Last minute, uncommunicated changes rarely if ever have a positive outcome.  
 
The culture at NQ of disregarding the time and effort of players, and lack of consideration of impacts on our gameplay, is worrisome. More worrisome, is the tendency to continuously rework existing content - mechanics, terrain, boolean noise - rather than develop significant new features, many of these features requested years ago. NQ are still missing the winning strategy of successful 'player generated content' franchises like Minecraft, where the focus of the first several years was on adding new gameplay loops - as opposed to continuously reworking existing ones. Reworking existing content decays player satisfaction by forcing the constant rework of our own builds. And making changes by stealth only magnifies the problem.
 
Until this is understood, the future of this franchise is fraught.