Template talk:Blueprint

There something wrong with the existing one?

There something wrong with the existing one? -Shine () 02:55, 10 August 2010 (UTC)

Yes, it's overly complicated. Compare:

{{recipe|
number=3|
ingredient1img=Backpack Batter's Helmet|
ingredient1name=Batter's helmet|
ingredient2img=Backpack_bonk|
ingredient2name=Bonk! Atomic Punch|
ingredient3img=Backpack_bonk|
ingredient3name=Bonk! Atomic Punch|
resultimg=Backpack Bonk Helm|
resultname=Bonk helm|
}}

to

{{Crafting recipe
| ingredient-1 = Batter's Helmet
| ingredient-2 = Bonk! Atomic Punch
| ingredient-3 = Bonk! Atomic Punch
| result = Bonk Helm
}}

If I could only figure out why I can only only get it to be consistent with two ingredients OR 3+ ingredients, and not both. -- Pilk _(talk) 03:02, 10 August 2010 (UTC)

Well, I can make the existing one only need

{{recipe
| number=3
| ingredient1=Batter's helmet
| ingredient2=Bonk! Atomic Punch
| ingredient3=Bonk! Atomic Punch
result=Bonk Helm
}}

Would that work? -Shine () 03:06, 10 August 2010 (UTC)

Well, so could I. The point is it shouldn't even need that. -- Pilk _(talk) 03:10, 10 August 2010 (UTC)

Is this going to work on language pages, where the links need descriptions?--Piemanmoo 08:18, 13 August 2010 (UTC)

Alternative results

How'd be have more parameters for results, separated by a "OR"? To show something like Melee Token + Medic Token + Scrap Metal = Ubersaw OR Vita-Saw.--Kid Of The Century 08:17, 30 October 2010 (UTC)

I agree with this. It would look cleaner and take up less space. On the set hats articles for example. Moussekateer 17:50, 8 November 2010 (UTC)

Background color for specific blueprints

Could be useful having a light-colored background for recipes that have a single result?--Kid Of The Century 08:19, 30 October 2010 (UTC)

Todo

• Make ingredient 2 optional (for recipes like Scrap Metal x3 = Reclaimed)
• Add result-amount

— Wind 20:25, 14 October 2010 (UTC)

Notes

Would it be possible to implement the notes of the chance of getting a certain weapon? Such as:

Note: The blueprint simply makes a <class name> <weapon type>; there is still a chance of getting the <result 1>, <result 2>, <result ect>, or <result 6> instead. There will be approximately a <percent> chance of crafting this item. — The preceding unsigned comment was added by GeminiViRiS (talk) • (contribs)

Specifically on the token crafting ones, he means. Fendermcbender 23:08, 11 March 2011 (UTC)

Spy watch blueprints incorrect

The Spy watch blueprints use the PDA2 slot token. This is infact the only PDA token available to craft, via 3 watches. Please amend the auto blueprints. – Smashman _(talk) 03:10, 18 March 2011 (UTC)

Correct naming for tokens?

I also notice that we have incorrect naming for tokens too. A 'Scout Token' here, actually appears as 'Class Token - Scout' in-game with 'Melee Token' appearing as 'Slot Token - Melee'. I think these should be used to keep to the names used in-game. – Smashman _(talk) 03:20, 18 March 2011 (UTC)

Why is this separate from Template:Blueprint/core?

I've been trying to fix a widespread error across different templates. Long story short, this kind of stuff causes an error/warning:

 |{{#if:{{{rankson|}}}|rankson|void}}={{{rankson|}}}
 |{{#if:{{{rankson2|}}}|rankson2|void}}={{{rankson2|}}}

because it passes the nonexistent parameter void to another template multiple times. This template has that kind of error. I couldn't find a fix for it for some reason because black magic, but I noticed that this template literally does nothing but pass parameters to {{Blueprint/core}} and adds an autoresult function:

{{#if: {{{autoresult|}}}|{{dictionary/blueprints/{{lc:{{{autoresult|}}}}}}}| . . . }}

Why not just copy-and-paste the entire Blueprint/core page onto this page, add that autoresult snippet, and redirect Blueprint/core to this page? It wouldn't cause any sort of problems (outside of perhaps surver burden), and it would save me the trouble of having to understand the black magic behind why |{{#if:{{{ingredient-1|}}}| ingredient-1 = {{{ingredient-1|}}}}} and
{{#if:{{{ingredient-1|}}}|{{!}} ingredient-1 = {{{ingredient-1|}}}}} somehow produce different results than |{{#if:{{{ingredient-1|}}}| ingredient-1 | null}} = {{{ingredient-1|}}} if given an input. Lemondoge (talk) 21:07, 15 August 2020 (UTC)

Hi, Lemondoge. Thanks for inquiring. I offer one opinion as one who is mostly a wiki writer, rather than a wiki architect.

Could you explain the wide-spread error more. I don't know if we have been experiencing an error.

The giants who set up the systems of templates we have are no longer active, but what they set up years before moving on has been stable; Blueprint since 2011 and Blueprint/core since 2912.

But, if Blueprint and Blueprint/core have been so stable, why are they broken now?

The Blueprints are something I have never worked with.

I am very wary of the argument of "I don't understand it so I will replace it." If the change is import enough to do, it is important enough to actually know what you are changing. My method is to figure out the template and add comments and documentation without changing any function without complete understanding. "Magic" is just technology one doesn't understand.

M I K A D O 282 ⊙⊙⊙⊙⊙⊙ ⊙⊙ ⊙⊙ (talk) (Help Wanted!) 21:44, 15 August 2020 (UTC) 00:02, 16 August 2020 (UTC)

This kind of error/warning is shown when you preview an edit on most pages:

I'm not entirely sure, but it seems like this error increases load time when trying to preview a page. Blueprint in particular calls Blueprint/core with more than one value for the "null" parameter. Lemondoge (talk) 18:19, 16 August 2020 (UTC)