| |
[FUT ".dev"]
> > 0 MiniBot SW Battle Droid (complete)
> > 0 Name: 30375cs0.dat
>
> This file should be 30375c01.dat.
Uh, why? Part # 30375 isn't unique the the "Star Wars" theme,
it's used in the "Life on Mars" theme as well, so I thougt that
the theme should be part of the filename (as with pattern numbers).
Since there are three patterns for this torso (so far),
one for each of the three "special" battle droids,
I made the filenames correspond with the pattern numbers:
parts/30375cs0.dat
MiniBot SW Battle Droid (complete)
vs.
parts/30375.dat (no pattern number)
MiniBot Torso
parts/30375cs1.dat
MiniBot SW Battle Droid Commander (complete)
vs.
parts/30375ps1.dat
MiniBot Torso with SW Battle Droid Commander Pattern
parts/30375cs2.dat
MiniBot SW Battle Droid Security (complete)
vs.
parts/30375ps2.dat
MiniBot Torso with SW Battle Droid Security Pattern
parts/30375cs3.dat
MiniBot SW Battle Droid Pilot (complete)
vs.
parts/30375ps3.dat
MiniBot Torso with SW Battle Droid Pilot Pattern
Thus, all four "complete" files will be adjacent to one another
in the parts list, as they should be.
Thanks,
Franklin
|
|
Message has 1 Reply:
 | | Re: 30375cs0.dat, "MiniBot SW Battle Droid (complete)"
|
| (...) Because it's an assembled item, based on unpatterned/decorated parts. Actually, since this file does *not* represent a part as delivered by TLC[1], the title should be flagged (Shortcut), not (Complete) (or (complete), as you put it). (...) In (...) (22 years ago, 11-Jun-02, to lugnet.cad.dev)
|
Message is in Reply To:
8 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
