 | | Re: please identify a tire?
|
|
Yes! Thank you very much. :) (20 years ago, 29-Feb-04, to lugnet.db.brictionary)
|
| |
| | Re: please identify a tire?
|
|
(...) You may also find this page (URL) useful when identifying wheels/tyres. ROSCO (20 years ago, 29-Feb-04, to lugnet.db.brictionary)
|
| |
| | Re: please identify a tire?
|
|
(...) Is it: (URL) Wedge Belt Wheel Tyre' (70162) BL uses the same number for it. Julie (20 years ago, 29-Feb-04, to lugnet.db.brictionary)
|
| |
| | please identify a tire?
|
|
I was wondering whether someone could identify this tire/tyre. A BrickLink or Peeron code would be appreciated, or the number of a set with this tire. I've looked through the BrickLink database with no luck, which I assume is about the same as the (...) (20 years ago, 29-Feb-04, to lugnet.db.brictionary)
|
| |
| | Re: Minifig Helmets
|
|
(...) Thanks for doing the research. As a result, I think "Chin Guard" is preferable. Chris (20 years ago, 18-Feb-04, to lugnet.cad.dat.parts, lugnet.db.brictionary)
|
| |
| | Re: Minifig Helmets
|
|
<all the stuff I agree with snipped, leaving only the trivial> (...) I agree with the idea, but is "Chin-Guard" a standard word? It's not in either dictionary.com or m-w.com (I really need to get my books out of storage. . .) and a Google search on (...) (20 years ago, 18-Feb-04, to lugnet.cad.dat.parts, lugnet.db.brictionary)
|
| |
| | Re: Minifig Helmets
|
|
(...) I can go along with that! ;) (Good catch, by the way! ;) (20 years ago, 18-Feb-04, to lugnet.cad.dat.parts, lugnet.db.brictionary)
|
| |
| | Re: Minifig Helmets
|
|
(...) I agree and prefer Chin-guard too. (...) Doh - no, of course not. I meant 193a : Minifig Helmet Classic with Thin Chin-guard 193b : Minifig Helmet Classic with Thick Chin-guard (...) Chris (20 years ago, 17-Feb-04, to lugnet.cad.dat.parts, lugnet.db.brictionary)
|
| |
| | Re: Minifig Helmets
|
|
(...) So, by your own logic, the classic helmets should be: (...) (I personally think the above makes more sense, incidentally. None of the helmets have chin straps, because that would have to go under the chin.) On a side note, are those supposed (...) (20 years ago, 17-Feb-04, to lugnet.cad.dat.parts, lugnet.db.brictionary)
|
| |
| | Re: Minifig Helmets
|
|
(...) I'm partial to Chin-Guard. A chinstrap is a miniature belt that braces itself against your chin to hold your helmet onto your head. A chin-*GUARD* on the other hand protects your chin. (...) I like the inclusion of Castle. But we should (...) (20 years ago, 17-Feb-04, to lugnet.cad.dat.parts, lugnet.db.brictionary)
|
| |
| | Re: Minifig Helmets
|
|
(...) And they lived happily ever after... :-)))) (...) Chin-Guard or Chinstrap? (...) suggestion: x527 - Minifig Helmet Castle with Chinstrap and Wide Brim (...) w. (20 years ago, 17-Feb-04, to lugnet.cad.dat.parts, lugnet.db.brictionary)
|
| |
| | Re: Minifig Helmets
|
|
(...) I'd like to reach closure on this in preparation for the next parts update. I have re-thought my decsion about 193+593 vs. 193a+193b, mainly in the light of the Classic Window discussion, where we are allowing suffices on 3DNs. And I also take (...) (20 years ago, 17-Feb-04, to lugnet.cad.dat.parts, lugnet.db.brictionary)
|
| |
| | Re: Minifig Helmets
|
|
(...) I still prefer: Minifig Town Castle ClassicSpace OldStyle Modern Crash With_and_without_vis...and_pivots Helmet with Skinny(Obese) Chinstrap any objections? how about the word order? ROFL w. (20 years ago, 22-Dec-03, to lugnet.cad.dat.parts, lugnet.db.brictionary)
|
| |
| | Re: Minifig Helmets
|
|
Why not call the current helment Minifig Helmet (which is what it is now) and call the classic helment Minifig Helmet Old with Thin/Thick Chinstrap (21 years ago, 12-Dec-03, to lugnet.cad.dat.parts, lugnet.db.brictionary)
|
| |
| | Re: Minifig Helmets
|
|
(...) Well, unless for some reason you've got a database that can recognize that two parts may be related when they have the same base number. I'm sure I know of a database like that somewhere. :) (...) For whatever reason, the visor was only made (...) (21 years ago, 11-Dec-03, to lugnet.cad.dat.parts, lugnet.db.brictionary)
|
| |
| | Re: Minifig Helmets
|
|
(...) put the blame on me ;-) I named them type 1, 2 because 3839A.dat and 3839B.dat are named: Plate 1 x 2 with Handles Type 1 - 3839A.dat Plate 1 x 2 with Handles Type 2 - 3839B.dat the only difference is in the height of the handles. the (...) (21 years ago, 11-Dec-03, to lugnet.cad.dat.parts, lugnet.db.brictionary)
|
| |
| | Re: Minifig Helmets
|
|
(...) Personally, I've thought of the "crash helmet" as the helmet that can accept a visor. You could also use the word "modern" as a descriptor. Thus, my two suggestions for 2446 are Minifig Helmet, Modern Style & Minifig Helmet with Visor Pivots I (...) (21 years ago, 11-Dec-03, to lugnet.cad.dat.parts, lugnet.db.brictionary)
|
| |
| | Re: Minifig Helmets
|
|
(...) The single-character suffixes are used, not because parts have multiple versions, but because different parts sometimes have the same number. If a new version of a part comes out with a different number, we'd use the new number when modeling (...) (21 years ago, 11-Dec-03, to lugnet.cad.dat.parts, lugnet.db.brictionary)
|
| |
| | Minifig Helmets
|
|
Noticed a few odd things about the Minifig Helmets on the Parts Tracker a few weeks ago (URL) first thing I noticed is that the newer version of the original helmet (the thick chinstrap version) has been assigned the new 3DN 593. I thought that was (...) (21 years ago, 11-Dec-03, to lugnet.cad.dat.parts, lugnet.db.brictionary)
|
| |
| | Re: Slope Brick Round
|
|
(...) It looks like another CATEGORY is about to be introduced. Steve has added ROUND as a CATEGORY; see (URL) may make sense to start moving all of the round bricks to this category, if that's what this category is intended for. John (21 years ago, 19-Nov-03, to lugnet.cad.dat.parts, lugnet.db.brictionary)
|
| |
| | Slope Brick Round
|
|
Following up on a comment by Chris Dee on part 33243 on the Tracker. . . There's this part 500 from the last parts update Slope Brick Round 1 x 6 Inverted The first mysterious thing about this name is that it starts with "slope", but then proceeds (...) (21 years ago, 19-Nov-03, to lugnet.cad.dat.parts, lugnet.db.brictionary)
|
| |
| | Re: Fwd from a builder: Colors don't match, among other things!
|
|
(...) This article is a quite interesting read. What jumped out at me was the mention that different colors of ABS have different specific gravities (within a small overall range). I wonder if the saline solution would have a detrimental effect on (...) (21 years ago, 16-Nov-03, to lugnet.general, lugnet.db.brictionary, lugnet.cad, lugnet.market.theory)
|
| |
| | Re: Proposal: New Part *NAMING* System.
|
|
Just to through my 2 cents in (even though I'm two weeks behind the rest of this thread ;-) )...I'm definitely interested in being a part of this project. (Being a data-organization junkie may have something to do with it.) Let me know what I need (...) (21 years ago, 13-Oct-03, to lugnet.db.brictionary)
|
| |
| | Re: 8429 re-release of 8812 not found
|
|
(...) Probably because no one posted about it to lugnet.admin.database. What's with this set? I've never heard of it not that that indicates much), and it's not on shop.lego.com. XFUT lugnet.admin.database (21 years ago, 6-Oct-03, to lugnet.db.brictionary, lugnet.admin.database)
|
| |
| | 8429 re-release of 8812 not found
|
|
Hello all, I have without any result tried to find the 8429 set ((URL)) - a re-release of the 8812 set ((URL)) - in the Lugnet database. Why is it not listed? Best regards, Peter (URL) (21 years ago, 5-Oct-03, to lugnet.db.brictionary)
|
| |
| | Re: Proposal: New Part *NAMING* System.
|
|
(...) Ray - this sounds like a very ambitious (and cool!) project :-) See some questions inline. (...) Why not block some numbers off for natural groupings of parts? Would say, a 1x2 brick with click hinge (2 prongs) and the same with 1 prong (that (...) (21 years ago, 29-Sep-03, to lugnet.db.brictionary)
|
| |
| | Re: Proposal: New Part *NAMING* System.
|
|
(...) This is a working draft of what I have in mind - Ray ===...=== Conceptural Outline for a Public Parts Catalog A) The results of the effort will be held under a public content license (such as Open Content or Creative Commons). The results will (...) (21 years ago, 28-Sep-03, to lugnet.db.brictionary)
|
| |
| | Re: Proposal: New Part *NAMING* System.
|
|
(...) We're very interested in having a public system set up, and would love working with one. It's something that we've been planning to do (with LDraw) for quite some time now - we even posted back in the day, to try and get some momentum going, (...) (21 years ago, 23-Sep-03, to lugnet.db.brictionary)
|
| |
| | Re: Proposal: New Part *NAMING* System.
|
|
(...) I like the ideas proposed here. They are almost identical to something I've been tossing around for a while with some other folks. Anyone out there interested in being involved in creating a public catalog ? Ray (21 years ago, 23-Sep-03, to lugnet.db.brictionary)
|
| |
| | Official LEGO Color Chart
|
|
Thanks to Jake and TLC, we just posted an official LEGO color chart, with RGB, CMYK, and Pantone colors, and a danglish name! Take a look: (URL) will be working in the next few weeks with LDraw to associate each of these colors with our current (...) (21 years ago, 30-Aug-03, to lugnet.announce, lugnet.cad, lugnet.db.brictionary, lugnet.cad.dev, lugnet.cad.ray) !!
|
| |
| | Re: Part 4318
|
|
I'm guessing the centered tab under the two fingers was counted as the third finger. IIRC, it functions not as most hinge "fingers" do, but stops the attached part from moving lower than horizontal. (...) (21 years ago, 28-Apr-03, to lugnet.db.brictionary)
|
| |
| | Re: Proposal: New Part *NAMING* System.
|
|
(...) I've been also busy cataloging my LEGO collection. I use the master part list downloaded from Peeron as a start. Eventually I found out that especially the decorated bricks and decorated minifigs are missing as a unique part number in the (...) (21 years ago, 11-Apr-03, to lugnet.db.brictionary)
|
| |
| | Re: Part 4180
|
|
(...) I thought I remembered a more recent discussion about this, but I can't find it. What I'm seeing is that really instead of the current part 4180 there should be three composite parts: 4180c01--Brick 2 x 4 with Permanent Black Train Wheels (...) (21 years ago, 20-Mar-03, to lugnet.db.brictionary, lugnet.cad.dat.parts)
|
| |
| | Part names: describe shape, not what models they come in
|
|
There are a number of parts that are named according to their use in a particular set. Trouble is, LEGO would then come out with another set that uses that part in a totally different way. Consider "Loudhailer." That one took me forever to find in (...) (21 years ago, 12-Mar-03, to lugnet.db.brictionary)
|
| |
| | Re: Proposal: New Part *NAMING* System.
|
|
(...) Thanks! Now how can we get it implemented, is the big question? So now we just need to get all the various parties to the same virtual table as it were. I don't think the MLCAD and BrickLink folks read this forum, do they? --Bill. (21 years ago, 12-Mar-03, to lugnet.db.brictionary)
|
| |
| | Part 4318
|
|
This part (URL) called Hinge Boat Mast with 3 Fingers On Both Sides despite seeming to have two fingers on each side, like (URL) it misnamed, or am I missing something? TIA, -- TWS Garrison (URL) capital letters in address for direct reply. (21 years ago, 8-Mar-03, to lugnet.db.brictionary)
|
| |
| | Re: Proposal: New Part *NAMING* System.
|
|
(...) Yep, and programs could still use that if no custom file was available. ROSCO (21 years ago, 7-Mar-03, to lugnet.db.brictionary)
|
| |
| | Re: Proposal: New Part *NAMING* System.
|
|
(...) Excellent idea. --Todd (21 years ago, 7-Mar-03, to lugnet.db.brictionary)
|
| |
| | Re: Proposal: New Part *NAMING* System.
|
|
In lugnet.cad.dev, William R. Ward writes: <snip> This is a really great idea! In addition, it wouldn't be all that hard to implement into existing software. We'd still have to keep the names in the part files though, to keep backward compatability. (...) (21 years ago, 1-Mar-03, to lugnet.db.brictionary)
|
| |
| | Proposal: New Part *NAMING* System.
|
|
Once the numbering system is in place, we then can deal with the next sticky issue: part names. Since everyone will want their names to be the final name chosen, I would like to sidestep that issue - there should not be a final name chosen. But (...) (21 years ago, 28-Feb-03, to lugnet.cad.dev, lugnet.db.inv, lugnet.db.brictionary)
|
