Talk:Blueprints
From Seed
Entry Template
====BPNAME==== {| border=1 cellspacing=0 cellpadding=5 |- |colspan=5 style="font-style:italic" width=100 | DESCRIPTION |- align=center |'''Base Value''' | '''Production Time''' |'''Factory Functions''' | '''Abilities''' | ''' Components''' |- |align=center | BASEVALUE |align=center | PRODUCTIONTIME | [[List_of_Factory_Functions#FUNC1|FUNC1]] <br>[[List_of_Factory_Functions#FUNC2|FUNC2]] <br>[[List_of_Factory_Functions#FUNC3|FUNC3]] <br>[[List_of_Factory_Functions#FUNC4|FUNC4]] | SKILL1 SKILL1LEVEL <br>SKILL2 SKILL2LEVEL | COMP1NUM x [[Components#COMP1|COMP1]] <br>COMP2NUM x [[Components#COMP2|COMP2]] <br>COMP3NUM x [[Components#COMP3|COMP3]] <br>COMP4NUM x [[Components#COMP4|COMP4]] |} [[Components#BPNAME|Component View]] [[List of Tools#BPNAME|Tool View]] <br>
- Zhiroc 17:46, 11 March 2006 (CET)
Link to component/tool/etc.
Supermagle
I think each blueprint should contain a link to the component/tool/etc. that is produced.
Saile
I think the links to components required for a bluprint should link to bluprint view, not component view - that way it would be easier to track a chain of requirements.
Zhiroc
I thought of that, but I'm not sure what real production will look like. Actually producing everything from scratch is a huge pain. I'd say it's more likely that components will be bought, or used from stockpiles. But who knows? Currently, it takes only two clicks to do a BP view: first go to the Component, then use the BP link.
Page too large?
I've found that you can no longer get a diff between two versions, presumably because this page has grown too large. Should we consider breaking it up? And if so, how? Some wiki advice would be appreciated.
- Zhiroc 16:58, 24 March 2006 (CET)