Original Post — Direct link

Lets assume that i have a 1000 BPC for a destroyer.

Those are all 20 run ME 10 TE 20 similar copies important part is that those are the same BPC with same ME/TE

Currently the only way i can store this is inside a small freight can, as it can quickly overflow the maximum number of items in hangar and make it unusable.

At the same time it is 1000 rows in database for you.

If one of the BPC was used and is missing single run - i cannot find in other way than looking at each BPC so this kind of storage is highly ineffective.

The idea is simple will save a lot of work from players and quite probably will have huge impact on your database

it was proposed also many times

Can you allow us to merge and split BPC using some mechanic?

Why not allow us to merge 1000 same BPC (in terms of ME/TE) into a single one ?

Asset management is much easier - and from 1000 rows in your database is being reduced to a single row.

In order to prevent abuses - splitting an merging BPC can be behind a ISK sink
So let say merging multiple BPC cost you 500,000 ISK same for splitting it to specific number of smaller copies.

Just to give you idea how big effect on database this can have :
I have multiple cans for each type : frigats, destroyer, cruiser, capital parts , capital modules etc.

This could also address issue that for example max run BPC for Capital Gun is 5 runs, while dread have 3 guns.

Just an idea not new one tbh

External link →
over 5 years ago - /u/ccp_habakuk - Direct link

Originally posted by EposproductionZ

Legacy Code?

Pretty much. But yeah, I personally would totally love to change BPCs and allow merging them (or some similar mechanic). There are different ways on how this could be done (potentially even moving blueprints out of the inventory system), but it would require quite a bit of code refactoring, so it would take an extensive amount of programmer time - and programmer time is needed for many different projects. While it would probably improve server performance (and especially DB performance) in the long run, we would also need to be careful about the performance impact of the process of merging 1000 BPCs into one BPC.