Difference between revisions of "Template talk:Blueprint"
(→Correct naming for tokens?) |
GeminiViRiS (talk | contribs) (Bah, I can't believe I forgot to put my sig there...) |
||
| Line 55: | Line 55: | ||
Would it be possible to implement the notes of the chance of getting a certain weapon? Such as: | 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.'' | + | '''''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.'' {{unsigned|GeminiViRiS}} |
: Specifically on the token crafting ones, he means. [[Image:TF2_crosshair.png|20px]] [[User:Fendermcbender|Fendermcbender]] 23:08, 11 March 2011 (UTC) | : Specifically on the token crafting ones, he means. [[Image:TF2_crosshair.png|20px]] [[User:Fendermcbender|Fendermcbender]] 23:08, 11 March 2011 (UTC) | ||
Revision as of 07:09, 19 March 2011
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)
Contents
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. {{subst:void|This template should always be substituted. Please change {{Unsigned}} to {{subst:Unsigned}}}}— The preceding unsigned comment was added by GeminiViRiS (talk) • (contribs) 2024-12-24, 09:21 UTC
- Specifically on the token crafting ones, he means.
Fendermcbender 23:08, 11 March 2011 (UTC)
As we have agreed to implement the generic blueprints into pages, each general blueprint is now manually added in each page; as such, every time there is an update adding new weapons that can be crafted via the generic blueprints, every page containing that generic blueprint will need to be updated. My modification to the template solves this: I've implemented an "autoresult", generated via adding autoresult=yes to the blueprint attributes; which automatically generates the results based upon the inputted items.
The autoresult is generated by interpreting ingredient-1 as a class token, ingredient-2 as a slot token and ingredient-3 as whatever additional item (currently it's only got support for the token blueprints (classtoken + slottoken + scrap metal).
Currently, the only thing preventing me from implementing this is that the /core file (containing the crafting combinations) is incomplete - it only supports primary, secondary and melee slots.
I welcome you all to review my modifications, and suggest any changes that should take place before it's implementation. I also welcome you all to contribute in populating the /core file with all of the token-related craft recipes and outcomes - it's written in a simple format, should be easy to get to grips with.
-
11:49, 13 March 2011 (UTC)
- I added the missing ones that I could remember; you were just missing the Rift items, and the Spy PDA recipe (though honestly that recipe is kinda moot given that you would need three PDA weapons to craft it and there are only two PDA weapons as of right now). I'll see if I can comb through it again to see if I missed anything. --LordKelvin 16:45, 13 March 2011 (UTC)
Notice Now implemented into Template:Blueprint- 19:36, 17 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)
