Template talk:Weapon

This will be getting love once I'm done with other templates and SMW conversion work ahead of its position in my queue. - lycan.nick (talk) 22:20, 8 April 2013 (EDT)

For the class restriction, we either need a redirect page for every class or have it set up in the template so that it links properly. For example, 'Raptor' doesn't exist, so we need to either make a redirect page to 'Recon/Raptor' or somehow have the template automatically link to 'Recon/Raptor' when 'Raptor' is put in as a field. Weableandbob (talk) 00:28, 13 May 2013 (EDT)
 * Redirect pages are fine. I could build a parser to trim out the preceding "Recon/" for display, but that parser would just incur more processing time on the server with pretty much the same results as the much simpler redirects. If we eventually get pages that actually take up Raptor, etc. with articles that aren't related to battleframes, we can revisit this problem later. - lycan.nick (talk) 12:52, 13 May 2013 (EDT)

Also, shouldn't there be a clip/magazine size field? That's common to all weapons. Weableandbob (talk) 00:31, 13 May 2013 (EDT)
 * Yeah, I should probably do that. I'll get to it after I'm done with classes today. If you notice these things during the Planning phase, that would make the template-making easier, since the initial template making is automated and any further changes have to be done manually. - lycan.nick (talk) 12:52, 13 May 2013 (EDT)

When editing a weapon page with the form, Primary fire ammo usage has "" instead of a field. Weableandbob (talk) 19:03, 10 June 2013 (EDT)
 * Error in Form:Weapon fixed. It wasn't in this template. - lycan.nick (talk) 01:08, 11 June 2013 (EDT)

Add Stock/Level 1 Crafted/Level 2 Crafted values (or ranges)?
Would add a lot of extra information and probably one extra row (and I'll probably end up doing width:40% on the infobox to accommodate the extra data). I'd probably implement it as a table-in-a-table or with multiple colspan= tags (either way making it a bit harder to maintain). Either way, I can do it... so should I? I'll probably just go ahead and implement Tier 3 and Tier 4 fields while I'm at it... would need some maintenance later, though, when R5 releases the Tier 3/Tier 4 crafting nanoprints. - lycan.nick (talk) 02:02, 19 June 2013 (EDT)
 * That would certainly be useful. I say go for it. Weableandbob (talk) 02:29, 19 June 2013 (EDT)