EVE Search - BLUE PRINT ISSUES AND A REQUEST TO HELP US !!!

All Channels

EVE General Discussion

BLUE PRINT ISSUES AND A REQUEST TO HELP US !!!

» Click here to find additional results for this topic using Google

Monitor this thread via RSS [?]

Author	Thread Statistics \| Show CCP posts - 0 post(s)
Sarmaul	Posted - 2006.02.27 01:17:00 - [1] the reason is that BPCs and BPOs are exactly the same - the only difference is their number of runs (i.e. bpos set to infinate, bpcs aren't). This kind of information isn't stored in the regular item list, and as such a full database query would be needed for each blueprint to determine how many runs it has left. Now imagine players with hundreds of BPCs opening up their assets. LAAAAAAAAAAAAAAAAG Originally by: Zzazzt Originally by: thoth foc PA doesnt stand for anything.. Punchbag Alliance...
Sarmaul	Posted - 2006.02.27 01:17:00 - [2] the reason is that BPCs and BPOs are exactly the same - the only difference is their number of runs (i.e. bpos set to infinate, bpcs aren't). This kind of information isn't stored in the regular item list, and as such a full database query would be needed for each blueprint to determine how many runs it has left. Now imagine players with hundreds of BPCs opening up their assets. LAAAAAAAAAAAAAAAAG Originally by: Zzazzt Originally by: thoth foc PA doesnt stand for anything.. Punchbag Alliance...
Sarmaul	Posted - 2006.02.27 01:17:00 - [3] the reason is that BPCs and BPOs are exactly the same - the only difference is their number of runs (i.e. bpos set to infinate, bpcs aren't). This kind of information isn't stored in the regular item list, and as such a full database query would be needed for each blueprint to determine how many runs it has left. Now imagine players with hundreds of BPCs opening up their assets. LAAAAAAAAAAAAAAAAG Originally by: Zzazzt Originally by: thoth foc PA doesnt stand for anything.. Punchbag Alliance...
Sarmaul	Posted - 2006.02.27 01:17:00 - [4] the reason is that BPCs and BPOs are exactly the same - the only difference is their number of runs (i.e. bpos set to infinate, bpcs aren't). This kind of information isn't stored in the regular item list, and as such a full database query would be needed for each blueprint to determine how many runs it has left. Now imagine players with hundreds of BPCs opening up their assets. LAAAAAAAAAAAAAAAAG Originally by: Zzazzt Originally by: thoth foc PA doesnt stand for anything.. Punchbag Alliance...
Sarmaul	Posted - 2006.02.27 01:17:00 - [5] the reason is that BPCs and BPOs are exactly the same - the only difference is their number of runs (i.e. bpos set to infinate, bpcs aren't). This kind of information isn't stored in the regular item list, and as such a full database query would be needed for each blueprint to determine how many runs it has left. Now imagine players with hundreds of BPCs opening up their assets. LAAAAAAAAAAAAAAAAG Originally by: Zzazzt Originally by: thoth foc PA doesnt stand for anything.. Punchbag Alliance...
Sarmaul	Posted - 2006.02.27 01:17:00 - [6] the reason is that BPCs and BPOs are exactly the same - the only difference is their number of runs (i.e. bpos set to infinate, bpcs aren't). This kind of information isn't stored in the regular item list, and as such a full database query would be needed for each blueprint to determine how many runs it has left. Now imagine players with hundreds of BPCs opening up their assets. LAAAAAAAAAAAAAAAAG Originally by: Zzazzt Originally by: thoth foc PA doesnt stand for anything.. Punchbag Alliance...
Sarmaul	Posted - 2006.02.27 01:17:00 - [7] the reason is that BPCs and BPOs are exactly the same - the only difference is their number of runs (i.e. bpos set to infinate, bpcs aren't). This kind of information isn't stored in the regular item list, and as such a full database query would be needed for each blueprint to determine how many runs it has left. Now imagine players with hundreds of BPCs opening up their assets. LAAAAAAAAAAAAAAAAG Originally by: Zzazzt Originally by: thoth foc PA doesnt stand for anything.. Punchbag Alliance...
Sarmaul	Posted - 2006.02.27 01:17:00 - [8] the reason is that BPCs and BPOs are exactly the same - the only difference is their number of runs (i.e. bpos set to infinate, bpcs aren't). This kind of information isn't stored in the regular item list, and as such a full database query would be needed for each blueprint to determine how many runs it has left. Now imagine players with hundreds of BPCs opening up their assets. LAAAAAAAAAAAAAAAAG Originally by: Zzazzt Originally by: thoth foc PA doesnt stand for anything.. Punchbag Alliance...
Sarmaul	Posted - 2006.02.27 01:17:00 - [9] the reason is that BPCs and BPOs are exactly the same - the only difference is their number of runs (i.e. bpos set to infinate, bpcs aren't). This kind of information isn't stored in the regular item list, and as such a full database query would be needed for each blueprint to determine how many runs it has left. Now imagine players with hundreds of BPCs opening up their assets. LAAAAAAAAAAAAAAAAG Originally by: Zzazzt Originally by: thoth foc PA doesnt stand for anything.. Punchbag Alliance...
Sarmaul	Posted - 2006.02.27 01:17:00 - [10] the reason is that BPCs and BPOs are exactly the same - the only difference is their number of runs (i.e. bpos set to infinate, bpcs aren't). This kind of information isn't stored in the regular item list, and as such a full database query would be needed for each blueprint to determine how many runs it has left. Now imagine players with hundreds of BPCs opening up their assets. LAAAAAAAAAAAAAAAAG Originally by: Zzazzt Originally by: thoth foc PA doesnt stand for anything.. Punchbag Alliance...
Sarmaul	Posted - 2006.02.27 01:17:00 - [11] the reason is that BPCs and BPOs are exactly the same - the only difference is their number of runs (i.e. bpos set to infinate, bpcs aren't). This kind of information isn't stored in the regular item list, and as such a full database query would be needed for each blueprint to determine how many runs it has left. Now imagine players with hundreds of BPCs opening up their assets. LAAAAAAAAAAAAAAAAG Originally by: Zzazzt Originally by: thoth foc PA doesnt stand for anything.. Punchbag Alliance...
Sarmaul	Posted - 2006.02.27 01:17:00 - [12] the reason is that BPCs and BPOs are exactly the same - the only difference is their number of runs (i.e. bpos set to infinate, bpcs aren't). This kind of information isn't stored in the regular item list, and as such a full database query would be needed for each blueprint to determine how many runs it has left. Now imagine players with hundreds of BPCs opening up their assets. LAAAAAAAAAAAAAAAAG Originally by: Zzazzt Originally by: thoth foc PA doesnt stand for anything.. Punchbag Alliance...
Sarmaul	Posted - 2006.02.27 01:17:00 - [13] the reason is that BPCs and BPOs are exactly the same - the only difference is their number of runs (i.e. bpos set to infinate, bpcs aren't). This kind of information isn't stored in the regular item list, and as such a full database query would be needed for each blueprint to determine how many runs it has left. Now imagine players with hundreds of BPCs opening up their assets. LAAAAAAAAAAAAAAAAG Originally by: Zzazzt Originally by: thoth foc PA doesnt stand for anything.. Punchbag Alliance...
Sarmaul	Posted - 2006.02.27 01:17:00 - [14] the reason is that BPCs and BPOs are exactly the same - the only difference is their number of runs (i.e. bpos set to infinate, bpcs aren't). This kind of information isn't stored in the regular item list, and as such a full database query would be needed for each blueprint to determine how many runs it has left. Now imagine players with hundreds of BPCs opening up their assets. LAAAAAAAAAAAAAAAAG Originally by: Zzazzt Originally by: thoth foc PA doesnt stand for anything.. Punchbag Alliance...
Sarmaul	Posted - 2006.02.27 01:17:00 - [15] the reason is that BPCs and BPOs are exactly the same - the only difference is their number of runs (i.e. bpos set to infinate, bpcs aren't). This kind of information isn't stored in the regular item list, and as such a full database query would be needed for each blueprint to determine how many runs it has left. Now imagine players with hundreds of BPCs opening up their assets. LAAAAAAAAAAAAAAAAG Originally by: Zzazzt Originally by: thoth foc PA doesnt stand for anything.. Punchbag Alliance...
Sarmaul	Posted - 2006.02.27 01:17:00 - [16] the reason is that BPCs and BPOs are exactly the same - the only difference is their number of runs (i.e. bpos set to infinate, bpcs aren't). This kind of information isn't stored in the regular item list, and as such a full database query would be needed for each blueprint to determine how many runs it has left. Now imagine players with hundreds of BPCs opening up their assets. LAAAAAAAAAAAAAAAAG Originally by: Zzazzt Originally by: thoth foc PA doesnt stand for anything.. Punchbag Alliance...
Sarmaul	Posted - 2006.02.27 01:17:00 - [17] the reason is that BPCs and BPOs are exactly the same - the only difference is their number of runs (i.e. bpos set to infinate, bpcs aren't). This kind of information isn't stored in the regular item list, and as such a full database query would be needed for each blueprint to determine how many runs it has left. Now imagine players with hundreds of BPCs opening up their assets. LAAAAAAAAAAAAAAAAG Originally by: Zzazzt Originally by: thoth foc PA doesnt stand for anything.. Punchbag Alliance...
Sarmaul	Posted - 2006.02.27 01:17:00 - [18] the reason is that BPCs and BPOs are exactly the same - the only difference is their number of runs (i.e. bpos set to infinate, bpcs aren't). This kind of information isn't stored in the regular item list, and as such a full database query would be needed for each blueprint to determine how many runs it has left. Now imagine players with hundreds of BPCs opening up their assets. LAAAAAAAAAAAAAAAAG Originally by: Zzazzt Originally by: thoth foc PA doesnt stand for anything.. Punchbag Alliance...
Sarmaul	Posted - 2006.02.27 01:17:00 - [19] the reason is that BPCs and BPOs are exactly the same - the only difference is their number of runs (i.e. bpos set to infinate, bpcs aren't). This kind of information isn't stored in the regular item list, and as such a full database query would be needed for each blueprint to determine how many runs it has left. Now imagine players with hundreds of BPCs opening up their assets. LAAAAAAAAAAAAAAAAG Originally by: Zzazzt Originally by: thoth foc PA doesnt stand for anything.. Punchbag Alliance...
Sarmaul	Posted - 2006.02.27 01:17:00 - [20] the reason is that BPCs and BPOs are exactly the same - the only difference is their number of runs (i.e. bpos set to infinate, bpcs aren't). This kind of information isn't stored in the regular item list, and as such a full database query would be needed for each blueprint to determine how many runs it has left. Now imagine players with hundreds of BPCs opening up their assets. LAAAAAAAAAAAAAAAAG Originally by: Zzazzt Originally by: thoth foc PA doesnt stand for anything.. Punchbag Alliance...
Sarmaul	Posted - 2006.02.27 01:17:00 - [21] the reason is that BPCs and BPOs are exactly the same - the only difference is their number of runs (i.e. bpos set to infinate, bpcs aren't). This kind of information isn't stored in the regular item list, and as such a full database query would be needed for each blueprint to determine how many runs it has left. Now imagine players with hundreds of BPCs opening up their assets. LAAAAAAAAAAAAAAAAG Originally by: Zzazzt Originally by: thoth foc PA doesnt stand for anything.. Punchbag Alliance...
Sarmaul	Posted - 2006.02.27 01:17:00 - [22] the reason is that BPCs and BPOs are exactly the same - the only difference is their number of runs (i.e. bpos set to infinate, bpcs aren't). This kind of information isn't stored in the regular item list, and as such a full database query would be needed for each blueprint to determine how many runs it has left. Now imagine players with hundreds of BPCs opening up their assets. LAAAAAAAAAAAAAAAAG Originally by: Zzazzt Originally by: thoth foc PA doesnt stand for anything.. Punchbag Alliance...
Sarmaul	Posted - 2006.02.27 09:15:00 - [23] Originally by: Dark Shikari Originally by: Bawldeux IV seems easy. bpc has limited runs or another atribute that makes it different then a bpo, so just use that as a flag, and bpo gets original graphic, bpc gets a different graphic, simple, has only to use the exisiting db fields, and can be client side, simple huh... The claim was that in order to do that the client would have to request all the database entries for the BPO, not just the header. However, as stated before, this claim is BS as this exact thing has been done for ages in the factory system just fine. yes, but how often do you open the factory compared to opening a general container/cargohold? Well okay, asking you that might not be the best idea in the world, but you get the point Here's an idea: Make copies of some random bookmarks that equal the number of bpos/bpcs in your hangar at the moment. Drop them into your main station hangar and then relog. Now try and open your hangar. The lag you're getting is the result of having to do deep database searches on another table to get the name of each bookmark. The principle is exactly the same for getting the number of runs on a blueprint in order to display them differently. Originally by: Zzazzt Originally by: thoth foc PA doesnt stand for anything.. Punchbag Alliance...
Sarmaul	Posted - 2006.02.27 09:15:00 - [24] Originally by: Dark Shikari Originally by: Bawldeux IV seems easy. bpc has limited runs or another atribute that makes it different then a bpo, so just use that as a flag, and bpo gets original graphic, bpc gets a different graphic, simple, has only to use the exisiting db fields, and can be client side, simple huh... The claim was that in order to do that the client would have to request all the database entries for the BPO, not just the header. However, as stated before, this claim is BS as this exact thing has been done for ages in the factory system just fine. yes, but how often do you open the factory compared to opening a general container/cargohold? Well okay, asking you that might not be the best idea in the world, but you get the point Here's an idea: Make copies of some random bookmarks that equal the number of bpos/bpcs in your hangar at the moment. Drop them into your main station hangar and then relog. Now try and open your hangar. The lag you're getting is the result of having to do deep database searches on another table to get the name of each bookmark. The principle is exactly the same for getting the number of runs on a blueprint in order to display them differently. Originally by: Zzazzt Originally by: thoth foc PA doesnt stand for anything.. Punchbag Alliance...
Sarmaul	Posted - 2006.02.27 10:49:00 - [25] Originally by: Gariuys Originally by: Avon The solution, obviously, is to get rid of all BPC's. Easy. Would kill most small producers. Not your best idea IMHO. Although more limits on them would be fine, those 1000s of 3 run bpcs are annoying as hell. no, it would kill off the vast majority of 1-time undercutters. BPOs are dirt cheap to buy besides some of the bigger ships. Just think, battleships might actually be worth building again for general sale Originally by: Zzazzt Originally by: thoth foc PA doesnt stand for anything.. Punchbag Alliance...
Sarmaul	Posted - 2006.02.27 11:26:00 - [26] Originally by: Tar om Originally by: Sarmaul the reason is that BPCs and BPOs are exactly the same - the only difference is their number of runs (i.e. bpos set to infinate, bpcs aren't). This kind of information isn't stored in the regular item list, and as such a full database query would be needed for each blueprint to determine how many runs it has left. Now imagine players with hundreds of BPCs opening up their assets. LAAAAAAAAAAAAAAAAG What about the "Copy = NO/YES" field? Anyway, the "Full Database Query" can't be that hard- they already did it when they purged the 0 run copies a while back. like I said, BPOs and BPCs are stored in exactly the same way. ME? Same way. PE? Same way. Number of runs? Same way. And remember, the only difference between a BPO and a BPC is the number of runs. Originally by: Zzazzt Originally by: thoth foc PA doesnt stand for anything.. Punchbag Alliance...

COPYRIGHT NOTICE
EVE Online, the EVE logo, EVE and all associated logos and designs are the intellectual property of CCP hf. All artwork, screenshots, characters, vehicles, storylines, world facts or other recognizable features of the intellectual property relating to these trademarks are likewise the intellectual property of CCP hf. EVE Online and the EVE logo are the registered trademarks of CCP hf. All rights are reserved worldwide. All other trademarks are the property of their respective owners. CCP hf. has granted permission to EVE-Search.com to use EVE Online and all associated logos and designs for promotional and information purposes on its website but does not endorse, and is not in any way affiliated with, EVE-Search.com. CCP is in no way responsible for the content on or functioning of this website, nor can it be liable for any damage arising from the use of this website.