BREAKING NEWS: GNOSIS STRANDED, GALNET NEWS!

Status
Thread Closed: Not open for further replies.
Like space honking?

Well, I went out and investigated the non-human signal sources, scooped some thargoid bits I was unable to sell at Gnosis, went out again and scanned bodies in several systems to find places to search for geological activity and do some mining, landed a few times and picked up some rare elements, took some neat photos on said landings, spent an hour searching for geysers on a good candidate planet with awesome landscapes and and vistas, and rescued 8 Occupied Escape Pods. I made two round trips from Gnosis in Open and experienced no difficulties regarding either hostilities or getting a pad to land on.
I
 

Deleted member 110222

D
I might buy the SRV camo' pack today, in celebration of Canonn not getting their own way.
 
I can safely say I would have done it better. It is in fact a huge part of my job, change management and software rollouts. I am not at the gnosis today because I had to train a bunch of senior managers how to use some new software we just rolled out.

The content is excellent. As many have said, this is what we wanted, to see what it's like to be under proper attack by Thargoids. Then came the detention center thing. How can I say I would have done better? Because I have NEVER in my 30 year career, EVER rolled out a piece of software or update to a live environment, without testing the CRAP out of it first in a stage environment. If I were testing this scenario, I would have engaged the thargoids in the no fire zone, I would have been killed, and I would have immediately realised and turned off the no fire zone (or if that were not possible, considered another workaround, such as the already suggested adding a detention center to the gnosis).

I agree, there are some outrageous things being said, but the fact is yes, I would have done better. I remember reading some time ago that FD don't have a test environment on the same version as production. I took it with a pinch of salt, but now I wonder.
.
So what would you have actually done? I mean, FD till the end tried to convince Cannon not to jump. But Cannon stuck to the plan and the schedule. That means that just delaying the content was no option here. They had to deliver something, no matter how quickly developed and how badly tested it was.
.
So based on the combination of such a fixed timeline and the fact that the software is "not critical"* releasing it would be the way to go. But what can I say, I'm just small ISTQB certified test analyst.
.
.
* Not critical means that no harm, be it physical or financial, will come from bugs. It's still a game, where the balance between quality and schedule often is in favour of the second. And while I also regularily find that FD favours the second too much and should put more emphasis on quality, in the given case rolling out badly tested content was the only reasonable option they had.
.
 
Exactly.

If the Gnosis had made the jump and then anything from nothing to the destruction of the Gnosis had happened I don't think anybody would have had cause to complain.

As it is, what we got was a "prank" from FDev, resulting in the usual hackneyed CGs and repairs.

Big whup.

Haha, I can't be helped, but feel a bit sorry for FDev, as they have really tried to do this with best intentions, providing something unexpected for the community. It seems they really need someone with experience how to handle such events.
 
Exactly.

If the Gnosis had made the jump and then anything from nothing to the destruction of the Gnosis had happened I don't think anybody would have had cause to complain.

As it is, what we got was a "prank" from FDev, resulting in the usual hackneyed CGs and repairs.

Big whup.

Nail on the head there Stealthie, Nail on the head!

+ Rep
 
And about "FD doesn't care, that is the worst thing evaaaaaa! The game is dooooooooomend". Oh my, because i don't like this tiny thing here?

But this isn’t a tiny thing. Not anymore. Anyone looking at the forums regularly could’ve seen the huge buildup this event has caused over the last weeks. Hundreds, thousands of CMDRs suddenly voicing interest in a thing at a time where the CG contributions are at an all time low. People coming back to the game because they’re hopeful something worthwhile might happen, maybe this time it will, oh please. Frontier could’ve seen this and put resources aside to make it a special occasion, something to remember, to show people they still care after months of postponed promises. But all they manage to deliver is a badly executed script they recycled from the bin that obviously wasn’t even tested properly. That’s the sad thing about this. The disappointment that even after this golden player-driven opportunity has been placed in their lap, FDev didn’t manage to jump over their own shadow.

Edit: At least that’s how it looks as of now. I’m still open to be positively surprised though, please prove me wrong Frontier!
 
Last edited:
Things are getting messy.

First of all, there will be no jump to the cone sector next week, the next jump for the gnosis will be back to its normal schedule, there was never going to be a jump to the cone sector, fdev just confused it all and didn't deal with it.

Second, if none of the build up had happened, no talk of cone sectors, and instead there was an unexpected attack on it by thargoids wherever it happened to be sitting, then this might have been a decent (though kind of overdone) event.

The big problem here is lack of foresight. Surely fdev know how excited people would be at the chance to visit a permit locked area? They are at fault for giving the impression it was possible.
To then fall back to the old "oh it didn't make it, but look, yet more thargoids, and another station to repair" routine, was just cheap and boring. They didn't even bother with a damage model.

It just sucks, so often we get excited about something that might happen in game due to a galnet article or other clue, yet so often they drop the ball.

It really didn't need a lot to make this into an awesome event, just exploring the unknown would have been enough, something different, a few little hand placed things to find, everyone would have been happy.

As it is, you have a massively unhappy canonn group, disappointed explorers and casual players, and if your lucky, a few combat guys enjoying the hydra fights, but the whole thing was just allowed to collapse in a pile of excrement.

I'm sorely disappointed, especially after last week's non announcement. And I'm a previous white knight type, faith has ran out guys, sorry.
 
Exactly.

If the Gnosis had made the jump and then anything from nothing to the destruction of the Gnosis had happened I don't think anybody would have had cause to complain.

As it is, what we got was a "prank" from FDev, resulting in the usual hackneyed CGs and repairs.

Big whup.

You gotta be joking. I hope you are joking. Do you think that Canonn would have prefered to have their megaship destroyed and all the commander on the ship. You think that would be better then what happened.

My god, I have read it all today.
 
Updates from Frontier ...

Greetings Commanders.

We are aware of several issues affecting Commanders located at the Gnosis. The team are actively investigating and addressing these issues, so if you encounter any related to the Gnosis and the Thargoid attack, please report them here.

Currently:

  • The Interceptors that were causing shutdowns and destruction have been moved further away from the Gnosis, addressing player complaints of being destroyed before leaving docking pads.
  • The Gnosis' controlling faction is no longer issuing fines for fighting within its No Fire zone. Commanders are urged to defend against the imminent alien threat. Be warned, shooting at at the Gnosis will result in fines.
  • For those Commanders who have found themselves detained further away, please contact our support team who will be happy to move you back to the Gnosis, should you wish to be…
Thank you for your understanding!

Greetings Commanders,

As you and others may have noticed in the early hours of the morning, a GalNet article on our community site revealed the future fate of the Gnosis’ jump toward the Cone Sector . However, the intended jump was to take place at the normal time of the server tick, however this was not the case and has caused a disparity between the news Commanders were able to read and the actions that took place in game.

We are aware that this has caused a number of Commanders to express their discontent that the news that was announced and the fate of the Gnosis’ epic charter.

After seeing this morning’s feedback, we want to take the opportunity to explain a little more about the event as a whole, and how these actions are playing out right now in the game world, the galaxy.

Before the launch…

Canonn high command reached out to us to plan the next jumps for the Gnosis. The destination? The Cone Sector... Cone Sector FN-J B9-0, to be precise.

Without revealing too much about this area of space, the Cone Sector both in content and in game lore was always meant to be locked off; and the fact that certain systems within the sector weren’t permit-locked was an oversight from a time before it was possible for Megaships to make such jumps, like the Gnosis.

Based on feedback we've received in the past, and in an aim to involve player agency in Elite Dangerous’ narrative, rather than simply making a universal change, or flicking a switch to ‘permit lock’ the systems in question (known in some corners of the community as “God modding”), we decided to incorporate the actions of a great Elite Dangerous player group, and a huge number of Commanders, into the wider lore of the game. Supporting the event as best we could with our own channels while reacting to an emergent piece of content from the community.

Working with Canonns’ event in mind, we decided to weave the event into the large game narrative, and the arrival of a threatening new Thargoid variant – the terrifying Hydra that some commanders woefully encountered recently.

So, what’s happened so far?

The Canonn called for Commanders to join them on the expedition to the Cone Sector to make history in the name of both exploration and science!

Meanwhile, across other areas of the galaxy, some Commanders reported sightings of what they believed to be a new Thargoid variant, later confirmed and classified by AEGIS and the Pilot’s Federation as the Hydra.

With this growing uncertainty, the Pilots’ Federation reported that the jump to the Cone Sector was not safe, not advised and urged Commanders to steer clear of any journeys there, permit-locking the systems.
Despite these warnings, Canonn would still make the jump into the unknown. And, with them, approximately 11,000 Commanders, from all walks of life, allegiances and states, pledged to this legendary expedition. Whether driven by a pursuit of knowledge, fearlessness or even perhaps… madness, they pledged their ship and soul to the future of the Gnosis.

This morning

As the GalNet article explained, moments into its ground-breaking jump toward the Cone Sector FN-J B9-0 system, the Gnosis has been left stranded following a massive Thargoid attack in the Outotz ST-I d9-6 system.

Now, we are aware that the premature release of the GalNet article (‘Gnosis Stranded’) caused speculation and concern from the community. It spoke of events that had not yet had any consequence or implication in-game, and as this occurred in the early hours of the morning, had no explanation from the team. We have investigated why that article went live at the wrong time and corrected the community site’s GalNet news feed so that it won’t break embargo in the future.

We are also aware that there are a few issues causing problems for Commanders at the current location of the Gnosis. The team are actively investigating and correcting those issues. Some of those issues are already fixed, while others are being addressed and a fix is in progress currently. Please visit the following thread for the current status update on these issues.

We would like to thank all of the Commanders who have provided their feedback – and pledged to aid the Gnosis in its defence against the alien threat and the terrifying new Thargoid variant. We would also like to take this opportunity to apologise for the confusion and bugs within this event but we are hugely grateful to the many thousands of Commanders who came together to make the event possible and become a part of history.

For those Commanders who have found themselves detained further away, please contact our support team who will be happy to move you back to the Gnosis, should you wish to be…
 
So we now KNOW, as objective, indisputable FACT, that Fdev are not testing/QA'ing new content. Not at all. Not even making an effort.

The degree to which they no longer care is finally out in the open, plain to see.

Quite the contrary. If I wouldn't care I would just put the galnet article that the far cult has snuck onto the gnosis and sabotaged the FSD megadrive. Problem solved, no work needed. Or even more bleak solution - let the gnosis jump into that sector, where there is NOTHING there (I would lock anything worthwhile of a secret under permit-lock only devs can overcome), get them to tag some pristine planets and get bored to death in a month. Instead they did this. I love it :) It required a change of plans probably, and was cobbled together using the resources available, after it went through management path, probably... These things take time.

What people (perhaps not familiar with IT) are not taking from this is that it was perhaps a live test. It might as well be that it was a live test that required a large number of players in an instance, and not all things can be simulated in a testing environment. Even if we shackle the rest of the 100 person team to the game and have them play for 8h in a row. But the QA could be skipped on this, or perhaps QA account have crimes off for convenience or something. It was an error. Those things happen. Get over it :)
 
Status
Thread Closed: Not open for further replies.
Top Bottom