If you are looking for Information about PSU Clementine, Go check their Wiki
Difference between revisions of "Template talk:Weapon synth board (Kubara)"
From The re-PSUPedia
m (New page: == Complexity == Okay boy you might consider not doing it the same way for Kubara as you did for other weapons. Right now you have 11 parameters to your template. You can do it with a muc...) |
(→Complexity) |
||
Line 2: | Line 2: | ||
Okay boy you might consider not doing it the same way for Kubara as you did for other weapons. Right now you have 11 parameters to your template. You can do it with a much simpler template using 12 parameters (see below). It's OK like this but I fear you'll get more exceptions because Kubara doesn't have a lot of logic put into it. If it can work, fine by me, but if you have to add another parameter or keep finding exceptions you'll want to make a template that uses the following parameters: Rarity, Photon, Ore, Ore qty., Gemstone, Gem. qty., Wood, Wood qty., Biomaterial, Bio. qty., Uses, Board. [[User:Essen|Essen]] 10:16, 17 April 2008 (CDT) | Okay boy you might consider not doing it the same way for Kubara as you did for other weapons. Right now you have 11 parameters to your template. You can do it with a much simpler template using 12 parameters (see below). It's OK like this but I fear you'll get more exceptions because Kubara doesn't have a lot of logic put into it. If it can work, fine by me, but if you have to add another parameter or keep finding exceptions you'll want to make a template that uses the following parameters: Rarity, Photon, Ore, Ore qty., Gemstone, Gem. qty., Wood, Wood qty., Biomaterial, Bio. qty., Uses, Board. [[User:Essen|Essen]] 10:16, 17 April 2008 (CDT) | ||
+ | * Excellent point. It seems that Kubara copies all follow a single pattern (based on weapon type and rarity), so if it comes to it, those can be kept in a single template that will allow for maximum auto-population of data cells. Like you said, it's the exceptions presented by the special weapons that's causing all of the problems. (And the Crea Wand+ really threw a wrench into the works by not following the copy or special patterns.) Worst case scenario, if we go with this template for all Kubara and then six months later SonicTeam decides that they want to give us a completely random ingredient pattern, a few adjustments can be made to the template that will allow a user to input unique values for ingredients of non-knockoff weapons. That way we could keep a single template, and then go back to articles using it that would be affected by the changes, add a few necessary parameters and values to make the corrections and be good to go. I think. XD - [[User:EspioKaos|EspioKaos]] 10:47, 17 April 2008 (CDT) |
Revision as of 15:47, 17 April 2008
Complexity
Okay boy you might consider not doing it the same way for Kubara as you did for other weapons. Right now you have 11 parameters to your template. You can do it with a much simpler template using 12 parameters (see below). It's OK like this but I fear you'll get more exceptions because Kubara doesn't have a lot of logic put into it. If it can work, fine by me, but if you have to add another parameter or keep finding exceptions you'll want to make a template that uses the following parameters: Rarity, Photon, Ore, Ore qty., Gemstone, Gem. qty., Wood, Wood qty., Biomaterial, Bio. qty., Uses, Board. Essen 10:16, 17 April 2008 (CDT)
- Excellent point. It seems that Kubara copies all follow a single pattern (based on weapon type and rarity), so if it comes to it, those can be kept in a single template that will allow for maximum auto-population of data cells. Like you said, it's the exceptions presented by the special weapons that's causing all of the problems. (And the Crea Wand+ really threw a wrench into the works by not following the copy or special patterns.) Worst case scenario, if we go with this template for all Kubara and then six months later SonicTeam decides that they want to give us a completely random ingredient pattern, a few adjustments can be made to the template that will allow a user to input unique values for ingredients of non-knockoff weapons. That way we could keep a single template, and then go back to articles using it that would be affected by the changes, add a few necessary parameters and values to make the corrections and be good to go. I think. XD - EspioKaos 10:47, 17 April 2008 (CDT)