Data & Relic Site Anti-Cherrypicking

EVE Technology and Research Center Player Features & Ideas
21

Working pretty well though.
In sleeper caches, once you hack the first can (not the one for opening the site, but one containing actually something), if there is nobody uncloacked in the site for 5 min, it despawns.
And the value is often more important that what you can get in usual relic/data sites.

There is a lot more, it’s more complex, and still people somehow find a way to NOT leave the site.
I mean, I made the mistake a few time, but that’s something you learn. You can’t cloak next to the explosive trap in the “sentry on duty” room in a ship fitted for survival.
However, you can stay visible in that room, hack the sentries to not get shot at, and target the trap. You’re visible on dscan, so at least the victim has a chance to not lose its shiny ship.

I can’t see a reason to not have this feature. But if you have a valid reason, please share.

22

I gave a reason when I told you my experience the last time I was in a relic site.

Me: no hacking modules on my Loki.
Relic site: one can hacked while I was probing it.
Explorer who did it: a wreck

Now if I wanted to refit to hacking modules to finish the site the Heron started, it would disappear as result of your suggestion. That’s no fun.

23

What if the ‘escalation’ was simply for an additional can to decloak ?

24

That could be nice, but is not the way sites work in EVE so that might require too much change from CCP.

I guess it could work if the exploration escalation always spawned in the same system.

2 Likes
25

Just because some specific cases would not be possible, is not a problem.
Of course any change has its pros and cons. Typically, preventing cherry picking from impacting other player may be perceived as a con, for those who consider cherry picking a positive thing.
It’s not “annoying”. It just removes some use cases.

And I mean, if you don’t go in a site ready to make that site, there is no reason for the site to wait for you. Other people could come and loot it too.
Get a depot. Don’t fight in shattered.

26

I dislike cherry picking and the exolorers who do it, but I think it’s a good part of the game that doesn’t need to be removed.

Cherry picking may annoy others and reduce your own profits by delaying also your own spawns, but it has it’s uses: you reduce the time you’re vulnerable in a site and behave less predictably through the site unless any campers already checked the contents of thr cans themselves.

Also if you dislike cherry pickers you can go out and stop them from doing so.

I think the gameplay options surrounding cherry picking are healthy and in no need of change.

I still do like the escalation idea as it reduces cherry picking but doesn’t stop people from cherry picking if they wanted to do so for strategic purposes.

1 Like
27

Of course, another addition could be, that once a player dies in a site, the site despawns :slight_smile:
This way, no more annoying “having to refit fast to do the site myself before it despawns” .

What I proposed (despawn) would not change that.
You can cherry pick. It just does not annoy others. Unless they come less than 5 min after you left.

That would not prevent cherry pick. Just make it less annoying for people who take the time to scan just to find out there is only a carbon remaining.

off topic edit :

FWIW the spawning of the anomalies is not completely random. I don’t know for relic and data, but sometimes the sites spawn in a very limited number of constellations.
The limited sleeper cache for example, can respawn in the same constellation, happened to me 3 times in a row in the same system (respawning like 1 min after I left the site)

I don’t know if that is abused regarding cherry picking in NS/WS but I know this can be used by people who have good knowledge of the game, to a point they can predict where(constellation wise) and when a given site will spawn (not ALL sites respawn instantly).

(And no, it was not an ice belt :stuck_out_tongue: )

edit 2 because I think it’s not clear : I’m not discarding your opinion, I’m saying it’s not generally annoying ( which would be enough to invalidate my proposal, as you know how much I hate tediousness by design ) . It’s annoying in specific cases, and it’s important to know which ones exist.
Indeed, if enough cases are rendered invalid by my proposal this could void it.

However, if it only punctually requires you to carry a mobile depot to do an activity that you did not intend to do in the first place, I don’t think that can be called “annoying”. It’s a specific case of potentially lost opportunistic activity, so I can’t see that as really an issue.

Of course, as any proposal, it should have its own important issues that simply put would void them and I expect you to actually provide an expert vision on those redhibitory defects rather than on a slight, potential, very specific opportunistic annoyance.

28

This. This a million times. (escalating hacking sites).

PS. I’m a cherry picker, and will stop doing that if sites can escalate.

2 Likes