Okay, so the stuff will be useless (cannot be enginnered) and will be more dificult to unlock.
><
><
News Guardian Blueprint Bug
- Status
game is broken, totally unplayable.
This is the logic of "fun"made in frontier.
CQC failed : lack of support.
Multicrew failed : lack of range within the promised activities, poor matchmaking.
Thargoid weapons where nerfed because they estimated it was too easy and fun to kill them.
And now Guardians will fail because stuff related to them is nerfed even before it is available.
Moreover FD spends time to enhance engineers, but make AX stuff (thargoids) and guardians stuff (new to the game) incompatible with them.
What a strange choice of direction. Really.
Last edited:
Good afternoon,
I am literally just back from Dav's hope in the last 10 minutes. sometimes the data scan gives one and sometimes three. lots of nice chemical manipulators though.
Regards
Pug
May I indulge in a slight rant? OK, if a bug is found, the right thing to do is fix it. But with modern coding practices bugs like this one should be completely impossible. There should be a class called something like GuardianObelisk which has a private field ScanResultList and a public method ScanResult which makes a selection from the list and returns it. A new scan result then only becomes possible if it is purposefully added to ScanResultList.
(Similarly, in another thread here, there should be a class GuardianPowerPlant which has a field CanBeEngineered set to "false"...)
Since the bug has happened it's obvious that the ED code isn't structured as I've suggested. I have a horrible fear that it's a load of spaghetti code instead. I've seen this happen to other games: making changes gets more and more difficult as the code becomes opaque and people who know it leave, and every attempted change introduces bugs which have to be rolled back.
Please don't let that happen to ED! Pause and put some proper structure in place instead of heading further into the spaghetti.
(Similarly, in another thread here, there should be a class GuardianPowerPlant which has a field CanBeEngineered set to "false"...)
Since the bug has happened it's obvious that the ED code isn't structured as I've suggested. I have a horrible fear that it's a load of spaghetti code instead. I've seen this happen to other games: making changes gets more and more difficult as the code becomes opaque and people who know it leave, and every attempted change introduces bugs which have to be rolled back.
Please don't let that happen to ED! Pause and put some proper structure in place instead of heading further into the spaghetti.
What about a generic class Module that gets parametrised during the construct/init? I see you know programming, but you lack of modular programming skills if you think there should be a specific class for every module. Anyway, I wont judge you, neither FD, I'm sure it is a complex piece to discuss without any knowledge.
Really? Which member of the anti fun police reported this?
How is it that these sort of things get patched so quickly but other more important things, don't get touched you know bug's that people have reported months ago that are still not fixed, like mentioned in the "Skimmer Nerf" thread.
I did the whole powering up of the "Data Terminal" and got 17 or 18 of the scan's done on it, whilst doing that I only ever got the "Weapon Blueprint Segment" I never got any of the other ones that I managed to obtain by scanning the Obelisk's.
I get that Frontier might not want people to get the stuff "Quickly" but you need to give more than 1 each time of completing the scan and at least have a chance of getting more than just the "Weapon Blueprint Segment".
What's next on the nerf/fix list, removing solo/private group because you can avoid unwanted pvp combat that way?
How is it that these sort of things get patched so quickly but other more important things, don't get touched you know bug's that people have reported months ago that are still not fixed, like mentioned in the "Skimmer Nerf" thread.
I did the whole powering up of the "Data Terminal" and got 17 or 18 of the scan's done on it, whilst doing that I only ever got the "Weapon Blueprint Segment" I never got any of the other ones that I managed to obtain by scanning the Obelisk's.
I get that Frontier might not want people to get the stuff "Quickly" but you need to give more than 1 each time of completing the scan and at least have a chance of getting more than just the "Weapon Blueprint Segment".
What's next on the nerf/fix list, removing solo/private group because you can avoid unwanted pvp combat that way?
So... The bug is, you can get what you need without having to repeat it as many times as FD decided you should have to...
I'm really quite miffed about that.
Would this not have been a lot better if you had a site for each tech broker item, which you just run once?
Is it really designed to make you repeat the exact same thing many many times, in a place your not going to go to regularly?
Because that sounds really really bad.
I'm really quite miffed about that.
Would this not have been a lot better if you had a site for each tech broker item, which you just run once?
Is it really designed to make you repeat the exact same thing many many times, in a place your not going to go to regularly?
Because that sounds really really bad.
That is exactly how it's designed by the sounds of it, but with a metric ton of RNG as to whether you get the data type you actually need.
17 or 18 times I did it, the way it seems it is supposed to be done and only got 1 of the data types I wanted, then I scanned the obelisk's to find the "Pattern Data" and found I got all the Data types I wanted so did that.
If it still work's after this update drop's this morning, I am going to stock up on the Data from the obelisk's because I really don't want to sit on a planet for hours on end scanning an object only to get 1 of 1 data type, when I am looking for 2 data types.
Will Flanagan
W
This issue has now been corrected in Update 3.0.2. Details can be found here: https://forums.frontier.co.uk/showthread.php/412245-Update-3-0-2
Locking up this thread now.
Locking up this thread now.
- Status