Board Thread:Wiki Discussion/@comment-6003396-20140313011700/@comment-6003396-20140408075944

I'm still not sure why the infusions aren't working, but I did notice a possible other problem. During certain instances where columns are suppressed, the template will still look for the values that would have been there otherwise. For example, let's say that one column is suppressed out of a total of 14 and that the template input was still in this formation: The main template would still think that #14 was part of the first row. There would still need to be an input as if the column were still there, and the particular cells under that column would be suppressed, yet still present in the code. If we look at the weapon upgrade code for the Caestus, for example, the reduction values are still entered, although only with a hyphen, and are then all suppressed with the variable "SuppRed".
 * 1 | 2 |  3 |  4 |  5 |  6 |  7 |  8 |  9 | 10 | 11 | 12 | 13
 * 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26

I think it might be easier to work off of this model and suppress the unnecessary columns, rather than naming which ones will be included, and also still input all of the values in the code for a weapon even if they do not apply. This would also function well for the WeaponDB.