Not entirely clear from the wording whether "Additionally, the top 75% of contributors will receive a fully engineered"... is contingent on "Should the initiative gain more data than Shadow President Winters's campaign" my assumption is that it is and that only one of the modules will be given based on which CG wins. But given its a separate paragraph it could be read as not dependent on one campaign doing better than the other
COMPLETED CG Support President Hudson to Increase Federal Surveillance (Data)
- Thread starter Kietrax
- Start date
- Status
Correct. This one is very clear in wording: Whoever gets more data is declared winner.
I seriously hope people are going for the KWS, because I want one.
The Hudson campaign is nearly at tier 3 already. This is gonna be all over by Sunday.
Relog makes this a joke.
And good luck to all of you trying to find a build with a 4.8 MW-draining KWS
35% after 18 hours ... we can look forward to many 'why do these finish so early!' posts on this one 
Don't worry, Frontier still can make adjustments on Friday35% after 18 hours ... we can look forward to many 'why do these finish so early!' posts on this one
Like the last time?
If they keep saying it they will be correct eventually. Might happen this week as there is a module to win, and it is going to finish very early.
I hope not “/ I have 58k already submitted and I don’t want to do this anymore lmao.
I don't think they'll adjust - because the CG is at 37% you're gonna upset people like ^^^ if you change now.
Edit: But - this is fdev, so
not always predictable
Edit: But - this is fdev, so
not always predictable 
Anyone else notice that this is the 2nd CG in a row that either requires constant relogging or is completely broken by it (depending on your view of relogging)?
Am I being paranoid thinking that FDev are using this to gather data before cracking down on it?
Am I being paranoid thinking that FDev are using this to gather data before cracking down on it?
I haven't done any relogging. Top 25% last time I looked. Maybe you're doing it wrongAnyone else notice that this is the 2nd CG in a row that either requires constant relogging or is completely broken by it (depending on your view of relogging)?
Am I being paranoid thinking that FDev are using this to gather data before cracking down on it?
All salvage CGs can use a relog to increase collection rate...Anyone else notice that this is the 2nd CG in a row that either requires constant relogging or is completely broken by it (depending on your view of relogging)?
Am I being paranoid thinking that FDev are using this to gather data before cracking down on it?
Thats because natural respawn is not applied.... and it is 2 salvage CGs in a row....
If escape pod CG, thargoid item CG or any "item" collection CG that is not based at a station is used respawn via relog will always be faster...
Instance regeneration via the normal space to super cruse to normal space loop takes longer but can still be done....
Last edited:
Interesting one. The time spent trading down g5 mats, 3 at a time, then going to the Research contact, handing in 200+ g1 mats, going back to mat trader to trade another 3 g5s... is painful. Some of the worst 'gameplay' in all gaming! I'll do it though for either interesting, dynamic narrative reasons, or just a sweet module.
As others have said though, even in fully G5 engineered combat / bounty hunting builds, I never use an A rated KWS because of the power consumption. It seems way out of whack with the B/C/D rated KWSs and more specifically, other modules like weapons and other scanners.
As others have said though, even in fully G5 engineered combat / bounty hunting builds, I never use an A rated KWS because of the power consumption. It seems way out of whack with the B/C/D rated KWSs and more specifically, other modules like weapons and other scanners.
Trade 3 AEC + 2 AEA, this will give you 297 UEF and make the overall process somewhat faster.
Top 10% in a little over an hour. I dont think i amI haven't done any relogging. Top 25% last time I looked. Maybe you're doing it wrong
- Status