Pages: [1] :: one page |
|
Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Ishkur
|
Posted - 2004.01.31 01:01:00 -
[1]
Edited by: Ishkur on 31/01/2004 01:03:32 Can I be a noob and ask for a feature or two that may have been asked before?
I'd really like to see a blueprint copy indicator on BPCs. That is, a BPC and a BPO should NOT look the same. Perhaps a "folded down corner" or something? Or perhaps make it yellow not blue? Something. Or even change the name? Or allow us to change the name? Something? Anything? I find this annoying.
To be clear about why: Here I am, making a BPC. Now suddenly I have BPCs and BPOs laying all over the place. Which is which? I don't really know. I can look at the Show Info, but see below, I am too obsessive-compulsive about messing up to do that effectively.
I'd really like to see some kind of indicia on Expired Blueprints. A red circle and line across them, or a big red ZERO or something. Again, if I have 3 BPCs and 2 are expired, I am stressed like you wouldn't believe throwing the expired one out. Stressed as in, I can't really do it, so I put them in a cargo hold of a shuttle. I know, that's dumb, but I am obessive-compulsive like that.
I think that's all that is really troubling me at the moment. Has this been suggested before? Surely I am not the first to be troubled by such things...
|
Bellac
|
Posted - 2004.01.31 11:29:00 -
[2]
I Must agree with you on this one. Indicators for the various types of print would help me out too.
|
Hafthor
|
Posted - 2004.01.31 16:57:00 -
[3]
I prefer to use small cargo containers to organize the hangar.. put all except one copy in a cc and you don't have to scroll through them all when starting projects. This is for when you have multiple copies of the same type or similar.
To return to the topic... MAKE IT SO!! LISTEN TO THIS VOICE OF REASON AMIDST THE MADNESS(me)
|
Trinity Prime
|
Posted - 2004.02.04 00:18:00 -
[4]
I whole heartedly agree. A copy indicator is long over do. Also, we should be able to stack like BPC's.
|
Ruffles
|
Posted - 2004.02.04 11:11:00 -
[5]
Bit hard to stack like blueprints if they each have different mineral and productivity levels.
Yes I agree the background sr something can at least be another colour, as could expired run copies.
Blue - Original Blueprint Green - Blueprint Copy Red - Zero run Blueprint Copy
Great idea though sir
|
Baldour Ngarr
|
Posted - 2004.02.05 12:45:00 -
[6]
Quote: Can I be a noob and ask for a feature or two that may have been asked before?
Many, many, many times....
Not that I'm annoyed at you for bringing the subject up YET AGAIN. I'm annoyed that it hasn't occurred to anyone that actually implementing this might prevent the subject from coming up YET AGAIN.
_______ "Soon" is an ancient Icelandic word meaning "some time before the next Ice Age." |
Verbal Kint
|
Posted - 2004.02.05 13:13:00 -
[7]
Aye I will throw my voice into the choir and cry out for this. It's a very small thing, but a thing that would help our 'work' immensely. In my experience you will not see copies and originals look alike out there in the real world either, thats why they made that red rubber stamp so you can stamp COPY on them. So you don't get confused. Wich is also my suggestion to mark them different. Two lines in red with Copy stencilled in between, across the blueprint picture. On the other hand i don't think you should mark used up copies any different. Some worl we have to do manually.
Verbal Kint. "By blood or word, whatever it takes."
Verbal Kint - Grumpy ol' c0ot. |
Eltigre
|
Posted - 2004.02.05 23:52:00 -
[8]
Quote: Edited by: Ishkur on 31/01/2004 01:03:32 Can I be a noob and ask for a feature or two that may have been asked before?
I'd really like to see a blueprint copy indicator on BPCs. That is, a BPC and a BPO should NOT look the same. Perhaps a "folded down corner" or something? Or perhaps make it yellow not blue? Something. Or even change the name? Or allow us to change the name? Something? Anything? I find this annoying.
To be clear about why: Here I am, making a BPC. Now suddenly I have BPCs and BPOs laying all over the place. Which is which? I don't really know. I can look at the Show Info, but see below, I am too obsessive-compulsive about messing up to do that effectively.
I'd really like to see some kind of indicia on Expired Blueprints. A red circle and line across them, or a big red ZERO or something. Again, if I have 3 BPCs and 2 are expired, I am stressed like you wouldn't believe throwing the expired one out. Stressed as in, I can't really do it, so I put them in a cargo hold of a shuttle. I know, that's dumb, but I am obessive-compulsive like that.
I think that's all that is really troubling me at the moment. Has this been suggested before? Surely I am not the first to be troubled by such things...
What you lack is organizational skills - I keep my BPO's and BPC's separate so I never get myself confused but alas this is my own way of making sense of the universe - hehe.
SWEET routinely sells BPC's in Sing Laison and Essence Regions. |
Brisi
|
Posted - 2004.02.06 10:19:00 -
[9]
stacking BP(C)s isn't the big deal for a dev ... they already do this for items!
problem can be the need of pre-sent data: * BP or BPC (0..1, 1 bit) * mineral efficiency* (0..256, 1 byte) * production efficiency* (0..256, 1 byte) * production runs left (0..32768, 2 bytes)
there's no need to pre-sent following data: * minerals amount ... of same kind of BP(C) and at same me-level the mineral amount are always the same date for YOU amount and BEST amount * overall prod runs at copy time (as infinite can be used 32768, no BPC will ever have 32768 prod runs anyway)
so - there's no problem to stack them ... different mineral amount can be grouped by MineralEfficiency the major work of the grouping/stacking can be done by the client or in the serverside query so the extra serverload or bandwith shouldn't be a problem ... i am sure devs can decide if the major part should be done by the server or client ... we just have 100-200 different kind of BPCs and much more different items ... after some time we will have multiple of the current numbers anyway
* me and pe levels are having a maximum because above a given level it makes "no" difference - noone is building patches with more than 1.000.000.000.000.000 runs *ROTFL*
wasted minerals * lvl 0 = 0,5 lvl 1 = 0,25 lvl 10 = 0,0009765625 lvl 20 = 0,00000095367431640625 lvl 50 = 0,000000000000000888178419700125 lvl 256 = 0,00000000000000000000000000000000000000000000000000000000000000000000000000000863616855509444
|
Baldour Ngarr
|
Posted - 2004.02.06 12:16:00 -
[10]
Quote: What you lack is organizational skills - I keep my BPO's and BPC's separate so I never get myself confused..
So do I - a corporate factory manager can do this, given the use of two divisions of the corp hangar. But a freelancer cannot.
_______ "Soon" is an ancient Icelandic word meaning "some time before the next Ice Age." |
|
Cindy Goodwill
|
Posted - 2004.02.06 18:02:00 -
[11]
if we make it another color than blue, it would lose it doesnt really qualify as a BLUEprint now does it :P perhaps different shades of blue, or as sugested a folded corner ----------------------------------------------- Watch my leet everchanging dynamic signature \o/ http://www.games-on.nl/~cu2moro/evesigphp/icon.php?blaat=.GIF |
Baldour Ngarr
|
Posted - 2004.02.06 19:26:00 -
[12]
Quote: if we make it another color than blue, it would lose it doesnt really qualify as a BLUEprint now does it :P perhaps different shades of blue, or as sugested a folded corner
Original "blueprints" are black on white - or at least, used to be: my technical knowledge is considerably out of date.It was the copying process used in duplicating highly-important material, that caused the copies to be white on blue.
Nowadays, given CAD and other such things, there probably aren't blueprints in any physical sense, until the plans are printed from the computer, which wouldn't be likely to be on blue paper.
Yet another "EVERYBODY-knows-that!" that isn't actually true. There's a lot of em
_______ "Soon" is an ancient Icelandic word meaning "some time before the next Ice Age." |
|
|
|
Pages: [1] :: one page |
First page | Previous page | Next page | Last page |