These forums have been archived and are now read-only.

The new forums are live and can be found at

Assembly Hall

  • Topic is locked indefinitely.

Ship manufacture date

Jason Edwards
Internet Tough Guy
#1 - 2011-12-13 20:24:53 UTC
Couldnt tell you what they keep in their database but they have to be tracking every item as it is for anti-cheating purposes. The database cost should be negligible as the data can just be cached forever. It would be quite interesting to be able to see when you 'commissioned' the ships.
Breaking Ambitions
#2 - 2011-12-13 21:12:14 UTC
I have no idea what you are going on about. Or if you were tripping balls while making this thread.

I honestly think PoCo based sov is a good idea

Trin Xi
#3 - 2011-12-13 22:23:56 UTC
It might also be interesting to see a commissioned date in the KM. That way you can tell if you've deprived your target of ship or pod they've managed to hang on to for a long while.

Post with someone else's main™.

Psychotic Tendencies.
#4 - 2011-12-14 14:26:28 UTC
The best you would be able to store is the date the ship was actually assembled - i.e., not the date it was built, but the date someone right clicked on the item stack and said "Assemble ship". That date would be lost at any point someone repackaged the ship.

The problem is that, in order to conserve database rows, an item doesn't get it's own row if it's part of a stack. The stack gets a row with a quantity indicator that shows how many of that item are in the stack. When the ship gets assembled, it gets it's own row that you can store the name, etc, in, but if the ship gets repackaged, that data is destroyed.

De'Veldrin's Corollary (to Malcanis' Law): Any idea that seeks to limit the ability of a large nullsec bloc to do something in the name of allowing more small groups into sov null will inevitably make it that much harder for small groups to enter sov null.