Currently 3 per cannister at Dav's Hope.
So they reverted from the postponed nerf in 3.0.3, good
A total Goldmine. Whether one per drop or three. You do a circuit, scan the datapoint and pick up some scan data - re log and go again. It’s my exploit. I don’t tend to follow whatever may give me 30MCr per hour but whizzing around a tiny base and picking up stuff that would otherwise take systems hops and flying about in hope is just too good to pass up.
Do it until you’d rather do something else and then move on. Sometimes I’d rather hang around outside Jameson Memorial in Open and get my scans from a busy station, other times I’d like to race other Cmdrs to the free stuff and share a friendly wave before logging in to solo before seeing them again in open.
It’s a weird game but I’m definitely smitten.
It's my understanding that the datapoint doesn't reset upon relogging, for what, like 2 hours or so?
It was always 3 per material drop. The bug was only with data drops from datapoints (and it was fixed in 3.0.4).
Good to know thanks.Currently 3 per cannister at Dav's Hope.
Well, they wanted to change it but apparently did not. You were supposed to only get one msterisl instead of three. This was stated as an intentional change.
Seriously, did you forget all the salt posts about this a few weeks ago?
I don't underdtand why they did not do this but lets not wake up sleeping dogs.
Good way for a few spare mats.
Well, they wanted to change it but apparently did not. You were supposed to only get one msterisl instead of three. This was stated as an intentional change.
Seriously, did you forget all the salt posts about this a few weeks ago?
I don't underdtand why they did not do this but lets not wake up sleeping dogs.
Good way for a few spare mats.
.............
- Good spread of materials including very rare's.
Did anyone ever tried to go to Dav's Hope after 3.0???
Material drop was never nerfed, or bugged, or whatever. It was, is, and presumably always will 3 per drop. Data drop (which is NOT the same as material drop!!!!) was bugged, and was subsequently fixed.