Topic on User talk:Harakoni

You're not bothering me. Always feel free to ask.

As for the table, you mean this table, Body part weapons#Comparison table?

If so I can see why you're confused. That table uses #ask to find anything that matches its parameters and then it feeds the matches' information (each of the properties with a ? In front of it) into a template to generate each row. This lets it automatically update when the pages are changed and also lets us avoid making all the tables manually.

The template it feeds into is Template: Body Part Weapon Table Row . That template is pretty simplistic - all it does is format the properties the ask feeds in. It doesn't even call True Melee DPS Calculator.

These properties are set by the infobox main template on the respective pages. That template is where you would add the new cell (and then on the page itself, add a new cell to the headings as well)

Atm there is a property for what body part a thing goes into/replaces Property: Body Part (which seems underused) but there isn't one for whether it's an implant or a replacement. This leaves you with a few options -

1. you can create a list of implants and then check if the name is on the list in the template, this is the easiest but obviously needs to be updates manually and doesn't let us use the implant/replacement info elsewhere
2. you can add the property to Template: infobox main and then add the call to the pages of each, then add the ? Property to the #ask then add a cell to the template. This lets us use the property elsewhere and it mostly is just copying what's already there and changing the names, but it's the most complicated and most work. You might want to hit up User: Ickputzdirwech, another Moderator here. They were doing work on the DPS Calculator and might have input on how to implement the property as it'll be useful for that too.
3. tag it with {{Recode|section=1|reason=Add "implant or replacement" column to table}} and let someone else handle it.

I know it's a bit overwhelming and not new editor friendly but the templatisation saves so much time and effort long term. I can help you with any of the options you wish to take, and you're perfectly justified to just go "nah someone else fix it".