Template:ChickenTest

Void Drop Table 3.0
Greetings, a few months ago we did a major revamp to the drop tables in Orokin Void hoping to make updating and reading it easier. Some claimed the format was too cramped, too small, and more importantly, updating it still required a lot of labor. Starting today, we are implementing yet another update that will hopefully make everyone's life easier.

Now before you start complaining stop fixing stuff that's not broke, keep in mind this update is more a under-the-hood change geared towards editors. Any front-end/visual changes are optional and will be decided with the poll below.

Important links: Module:Void, Module:Void/data

New stuff
Currently, whenever a new prime comes along there are at least three pages we need to update: Orokin Void/Rewards, Orokin Void/Rewards/ByType, and then the BuildRequire template in all the prime articles. Doing so is error-prone, redundant and tedious.

This new update will address this with a new template/module: Module:Void, which will reference a meta table Module:Void/data. So unlike what we previously do, we just need to update the meta table one time, and all pages that call the module will auto reflect the change.

The module will generate information by mission or by rewards automatically, i.e.

New Format
Since the module can do both by mission or by rewards, .... we can pretty much ditch the all-in-one table. You have two choices: to switch to the previous tabber format, or retain the current all-in-one format. You may also post your suggestions in the comments below: Which drop table format would you prefer? Tabber All-in-one table Other. I posted a comment below.

Updating stuff
Updating the drop table is just a small part of the process. There are gazillions of prime articles around the wiki that need to be updated to utilize this new module, and we need your help to make this happen.

Updating the BuildRequire template in weapon/warframe articles
Currently every BuildRequire template displays drop locations like this: (taken from Soma Prime) ... Tower II Survival (Rotation B) }} Which is a bloody mess To make use of the new module and generate the drop locations automatically, we just need to change the drop location inputs to: ... }} Syntax:
 * blueprintmission = Tower II Defense (Rotation A) Tower II Survival (Rotation B)
 * build1mission = Tower IV Interception (Rotation C)
 * build2mission = Tower II Survival (Rotation C)
 * build3mission = Tower III Exterminate
 * blueprintmissionps4 =Tower II Defense (Rotation A)
 * build1missionps4 =Tower IV Interception (Rotation C)
 * build2missionps4 =Tower II Survival (Rotation C)
 * build3missionps4 =Tower III Exterminate
 * blueprintmissionxb1 =Tower II Defense (Rotation A) Tower II Survival (Rotation B)
 * build1missionxb1 =Tower IV Interception (Rotation C)
 * build2missionxb1 =Tower II Survival (Rotation C)
 * build3missionxb1 = Tower III Exterminate
 * blueprintmission =
 * build1mission =
 * build2mission =
 * build3mission =
 * blueprintmissionps4 =
 * build1missionps4 =
 * build2missionps4 =
 * build3missionps4 =
 * blueprintmissionxb1 =
 * build1missionxb1 =
 * build2missionxb1 =
 * build3missionxb1 =

The result output should remain more or less the same as before, save the "Defense Rotation A" being changed to "Defense A", but any changes in Module:Void/data will be reflected in all the outputs across the wiki.

Updating the data module
The Data module is available here: Module:Void/data and is opened to all registered members. To update it just follow the established format. I myself will be using the compare feature in a text editor.... Let's just pray DE will retain the current format in future updates.

Thanks for reading. If you come across any problems and/or want to make improvement to the code, please leave a comment below.