Thargoids destroyed FDev servers as well.
Heck, even my PC is malfunctioning since yesterday even though I wasn't even close to Gnosis.
Heck, even my PC is malfunctioning since yesterday even though I wasn't even close to Gnosis.
Yes. Now think about why these particular sectors might be reserved based on what we've already seen. I'm sure it's all just a coincidence.Firstly, there are a bunch of permit locked sectors all over the galaxy, that are locked by fdev as reserved space, so it's not lore based as the reason but practical.
I didn't say it was an AX-only fleet, just that the Gnosis had an AX fleet on board. Sure, there are lots of non-combat ships ready to take over and exploit the sector once the AX ships have killed the natives.Two, there is a mix of AX, MINING, EXPLORATION on the gnosis because the thought was the AX cmdrs would look for and hunt hydras, while explorers and miners did their own thing
So no it isn't just an AX only fleet at all. The description never mentioned thargoid homeworld or that this was some first strike, or that this was any kind of military campaign. At all.
Obviously the Canonn people plotting the route were originally planning an exploration trip, because they hadn't figured out why it was blocked out in the first place.Again this was phrased as some kind d of exploration mission.
Unless you think there is a military reason that the gnosis next stop was the formadine rift?
Hi there folks,
We should have an update on the Gnosis soon.
In the meantime, we'd like to thank you for the reports regarding being destroyed before launch, fire zone transgressions (and Thargoid proximity) and Solo/Open players being mixed together. The team are presently investigating and we hope to have more information for you soon.
You're right, it's not a combat vessel, but it's preventing the AX pilots from doing their job. However, no reasonable person onboard the Gnosis would hand out fines to Commanders, and would be training the guns it does have on the Thargoids.THis is not FDev problem, this is YOUR* problem 1) Do not engage within no - fire zone., This is the purpose of no-fire zone.2) Optionally report Tahrgoid breach of no-fire zone rulings to Gnosis commanders3) If fighter incurs fines, do not deploy fighters4) Solution alredy provided by time-paradox Galnet article some hours before the situation ensued - Use Meta Alloys to lure away Thargoids.5) Bear in mind, Gnosis is science resarch vessel, not intended combat dreadnought.*(Or other pilot attempting to place round peg in square hole)
Please, please, please tell me this problem can be fixed without taking the servers down.
Although I am fully expecting you to come back and say "we'll issue a fix for this next week"
Hi there folks,
We should have an update on the Gnosis soon.
In the meantime, we'd like to thank you for the reports regarding being destroyed before launch, fire zone transgressions (and Thargoid proximity) and Solo/Open players being mixed together. The team are presently investigating and we hope to have more information for you soon.
Hi there folks,
We should have an update on the Gnosis soon.
In the meantime, we'd like to thank you for the reports regarding being destroyed before launch, fire zone transgressions (and Thargoid proximity) and Solo/Open players being mixed together. The team are presently investigating and we hope to have more information for you soon.
WARNING
Do not die while having fines for firing in the no-fire zone of the Gnosis. If you die while protecting the ship from Thargoids, you'll get send 1178LY away to the California Sector Detention Facility.
I just found this out the hard way.
I would of thought that they would be server side fixes, so hopefully no downtime.
Behold, my new Gnosis/Human hybrid fighter, powered by pure forum outrage!
Choose options :
2. But we have 100 people working on this project.