Potential of structure hacking is woefully underutilized beyond just relegating it to displaying reinforcement timers. Here are five additions that could be included in the report after a successful structure hack. This info would only remain available for viewing as long a player is uncloaked and in range of structure.
Last 5 players (25 with max skills) to have docked with structure in prior 3 days
When players docked/undocked
Prior station(s) players visited before docking with target structure
Structure saves info on last ship docked/undocked with as a ship fitting. Max 25 players tracked. One fitting saved each.
List of upwell cargo delivers Estimated value of all items in the structure.
Breaching this intel dossier triggers suspect status in empire space.
Addendum: Players may pay CONCORD cyber security division a monthly fee to raise structures hacking difficulty by 1 or 3 levels depending on the payment package.
Structure hacking difficulty is also automatically raised by 1 level for any defending corporation under war declaration.
Also possibly crash the client depending on the volume of the request. If CCP could find a balance to provide granular intel on transit activity without setting server on fire it would greatly expand counter intelligence gameplay opportunities.
They already have. Thatâs why you get what you currently get. Because itâs also information that does not change second to second and needs to be tracked and remembered. You want permanent TIDI in perimeter or something? â â â â no.
First because of the data that would have to be tracked for 10 million useless structures and second the data is not even structure related it is player tracking. Major -1 on player tracking.
If it was something like industry jobs that could be different.
Players dock with structures. Scotty the docking manager keeps records of who docked, when they docked, and what they docked with. That makes it structure related in my eyes.
If you donât want to dock and leave an immediate record of your presence use the upwell structure deposit.
Itâs a rolling list of 5 to 25 names with 2 to 3 data points each. Nothing too extreme. Data is only saved on a structure for 3 days. If a structure is unused it frees up space.
The change of going suspect when hacking structures in empire space moderately mitigates this server call load. Sure some groups may try to group blitz for data hacks, however CCP could limit that by capping the number of people hacking structures to one at a time.
âMan up?â Iâll have you know that i identify as a female pleasure bot.
No, this expands leg work opportunities to feel out possible ship fits of solo or gang targets, however this info doesnât guarantee anything as the targets can refit in space.
Itâs not going to be the request to get the info thatâs going to cause the performance issues. Itâs going to be the storage of the information required. Take Jita 4-4 as an example. If the game had to ârememberâ who the last 25 people undocking from that station were, and only that, itâs going to cause a performance impact because that many people are undocking from the station at any given second. Enough systems and structures on a node, youâre going to start seeing levels of data processing on par with blob vs blob fleet combat. Thus TIDI.
Thereâs a reason many things only update/change at downtime.
To be honest, Iâd be shocked if the logs didnât already reflect dock and undock times. Itâs just one row in a table, every time someone docks or undocks⌠even in Jita thatâs not going to spike more than 10 inserts every second 95% of the time. But remember that Jita 4-4 isnât a citadel either. Perimeter, different story but still really not an onerous query to run on the server (select top 25 from dockinglog).
When we have 1000 in a citadel and we mass-undock to get on the titans, thatâs still not going to be a huge problem because it can easily be run asymmetrically⌠you donât need to wait for the log to write to proceed.
As for saved fits⌠those are player things, not citadel things. But even if you did, which of the ~200 fits that I have saved are you going to base your choice on?
The assets thing⌠that I actually do like and want. Evicting people from space is â â â â â â â annoying. Knowing which citadels their stuff is in offers more opportunity to attack the right structures. This in turn forces them to evac the structure (or show up and defend it, rather than just ignore the loss of an empty structure).
Fair point. It doesnât necessarily need to be an immediate check for the system to still convey relevant data. Server could poll in 5 minute delayed checks, grab player names on the tail end of those blocks.
What I meant by saved fitting is a copy of the ship a player docks or undocks with, essentially a comprehensive ship module scan. The system would only save one entry at a time per player.
E.g. group A of wormhole hunters want to get approximations on group Bâs forces. When they docked/undocked and possible fleet size (capped at viewing 25) and composition.
Of course, this info is also particularly handy for hunting miners and epithals, unless those resource gatherers forgo docking and instead use upwell cargo deposit to conceal docking times.
I was initially thinking more last 100 items placed in upwell deposit box, however your interpretation has more utility. How about instead of a list of items held in the structure it would display the estimated value of all items in the structure?
If it was a reliable estimate, sure. What is CCPâs estimate of an Imp, though? Iâve yet to see much of anything with a reliable estimate.
Just a giant dump of the items, so the player could copy and paste into evepraisal would be enough for my tastes. It would likely be computationally easier as well, because while theyâd still be pulling the information they would not need to perform the summation of value once they pull the items.
Iâd probably add to that itâd be worthwhile to see contracts as well. Knowing that theyâve failed to restock a doctrine would be incredibly valuable knowledge, when you can bring something that they would have used that doctrine to counter.
ok, thred tldr, so iâll mix what i read with what you got here and state what looks good and what doesnât.
looking alright i guess
not sure if feasible but looking to know patterns with the particular structure seems like an allowable action
no. even if a player spent all day jumping from upwell to upwell, i donât see, since you like to take to the in-lore side, why this information would be logged in one station. if you wanted to create a play by play on every movement a capsuleer made, you would just have to track them down the old fashioned way.
recieving a ship fitting with each of the 25 is a little sketchy of a proposal, from server workload to whether or not this seems to be TMI to reasonabl allow access to, if used against a lowsec pvper you could effectively know how to counter him and that allone sounds like a way to kill off solo pvp, which i thought LS was supposed to be âThe placeâ for that.
in short, i say allow access to what ship their flying, but nothing more.
thatâs quite alright depending on asset safety rules in their area.
suspect flag is applied the second you make the first node click in the window, but only in Highsec.
If we take tracking for docking times and ships flown off the table, would you see wealth tracking of combined assets value in a structure placing the same kind of load on the server? The tech is already there with player net worth stats on the character sheet (updated every 12 hours).
Estimated value would be pretty pointless because not everything in that amount would be a potential loot object. Youâd have so much stuff getting trimmed out that the only thing of value you would get in the end is a value estimate of the structureâs fit itself, not itâs contents.
