FANDOM

A Lone Tenno
  Loading editor
  • I think the migration broke something fundamental. There are broken scripts everywhere. Two examples are: https://warframe.fandom.com/wiki/Panthera https://warframe.fandom.com/wiki/Chroma

      Loading editor
  • The Pupacyst is categorised as a staff, where it is actually a polearm.

    I tried to correct this in the master template, but I don't have permissions to do so.

      Loading editor
    • A Lone Tenno
        Loading editor
  • In the "View Rewards List" table at http://warframe.wikia.com/wiki/Spy#Rewards , the "Second Vault" column for Tier 3 is currently duplicating Meso S8 relic 4x, and Neo K2 relic 4x. I'm guessing it should be 44.24% drop chance for Meso S8 and 10.04% for Neo K2. Not sure if this is an issue with your Lua script or DE's data, and it's not urgent, so whenever you get to it.

    p.s. your modules code scares me :p

      Loading editor
    • A Lone Tenno
        Loading editor
  • Hello there Falterfire, I have reverted your edit on two templates

    Module:Void and Module:Icon since both broke the Ducats Price list by ommiting the name of  the item whenever it is template'd



    Regards

      Loading editor
    • Thanks for letting me know. I was working on something else and missed something when trying to ensure it didn't break other pages. I've un-reverted and then fixed the bug. Let me know if you spot anything else broken.

        Loading editor
    • A Lone Tenno
        Loading editor
  • Hi, FalterFire, i added all information about researches in Tenno Lab on Module Research/data. Please, inform me if I have made any mistakes.

    Thanks.

      Loading editor
    • A Lone Tenno
        Loading editor
  • Hi FalterFire,

    I have been roaming around http://warframe.wikia.com/wiki/Module:Weapons and I thought that the way we get the big weapon comparison table (this one http://warframe.wikia.com/wiki/Weapon_Comparison ) it is not convenient to make other tables of the same kind...

    The reason is that the page calls a p. function that calls the subfunction that construct the header of the table then calls the subsubfunction that construct each rows. And the structure of the table (ie : what are the columns) is hardcoded in these 3 functions !

    So if you want to make another table similar to this one, but with one less column (for example), you have to copy these 3 functions, paste them with 3 new names, and edit the code in the 3 functions...

    That's where I thought that the structure of the table (ie : what are the columns) could be encoded only in the first p. function, and then passed to the subfunctions as a "Header" table... so to create two similar tables with different columns you only have to create two p. functions that calls the same subfunctions...

    I put my test in Module:Weapons at the end of the file... output tables examples can be seen on my testpage http://warframe.wikia.com/wiki/User:Croquemorttime/testpage

    It may make life easier if we want to create specific comparison tables on pages like this one : http://warframe.wikia.com/wiki/Projectile_Speed

    Let me know what you think

    Cheers !

      Loading editor
    • View all 21 replies
    • Right now the idea is that the properties in the uppermost attack apply to the lower ones unless overriden. So Dread's charge crit chance is unlisted, which means it's the same as the normal attack.

      The simulor is just a giant clusterfuck built out of exceptions and 'technically it works'.

        Loading editor
    • Indeed, I checked in older versions, the getAttackValue would first search in the default attack (eg charge) then in the normal attack if it didn't work...

      I reverted to that in getAttackValue and added a "global" weapon version in getValue (that is only used in tables for now...) and that is checking in order in charge, normal then secondary to fetch the values...we could even add other attack types to that eventually...

      I think it is safer that way, as the weapon infobox is supposed to give attack specific result, and the way I implemented it before it could give the wrong stats to a given attack... (like give the crit chance of the secondary attack into the normal attack for stradavar or tenora or whatever...)

      It is live and working as far as I can tell...

        Loading editor
    • A Lone Tenno
        Loading editor
  • Hi FalterFire,

    we have noticed that this table http://warframe.wikia.com/wiki/Plains_of_Eidolon/Rewards is a little confusing since the update that give a bounty reward at every stage : the rewards appear multiple times with different drop rates with no clasification. That is because there is no distinction between the stages in the drop table database

    I tried to force the distinction by multiplicating the bounty categories by 3, ie : there is now 3 bounty1 categrories ("5-15-1","5-15-2" and "5-15"3" corresponding to stages 1, stage2 and stage 3 rewards respectively)

    It is a little experimental for now so I only did it for bounty1 ... do you have a better idea of how to do it ?

    (feel free to revert any changes obviously)

    cheers !

      Loading editor
    • View all 6 replies
    • Okay, everything should now properly be on the new formatting version. Please let me know if you spot anything that isn't working right

        Loading editor
    • Cool !

      it seems to work fine as far as I can see

      However, I think it would be better to sort first by drop chance, since stage 2 basically adds rows of lower drop chance to stage 1 etc... (with some exceptions apparently...)

      I tried it in http://warframe.wikia.com/wiki/Module:DropTables to see what it does... Obviously it does affect other droptables like survival and defense... it is rather a matter of taste at this point :)

        Loading editor
    • A Lone Tenno
        Loading editor
  • Can you help me with the error script? I'm using the old module:WeaponInfoAutomatic (compared to the version of the wiki en). Vectis Prime

    43534534534534
      Loading editor
    • View all 5 replies
    • I fix the problem with this lines and added the new version the function "getValue"

         result = result..buildInfoboxRow("Aumento", getValue(Weapon, "Zoom", true, true))
         if(Weapon.Zoom ~= nil) then
             result = result..buildInfoboxRow("Niveles de Zoom", table.concat(Weapon.Zoom, "
      ")) end result = result..buildInfoboxRow("Reinicio del Combo de Disparo", Weapon.SniperComboReset) result = result..buildInfoboxRow("Combo de Disparo Mínimo",Weapon.SniperComboMin)
        Loading editor
    • I'm glad you found a fix. Let me know if you need any other help.

        Loading editor
    • A Lone Tenno
        Loading editor
  • I tested the recent update you made on "WeaponInfoboxAutomatic" (update the "weapons" and "weapons / data" modules, but there was an error like "", how can I solve it?

    pd: I'm from the Spanish wiki [link]

      Loading editor
  • I hope I haven't messed up your code with too many or too few commas. Nevertheless, all of the disposition information for the listed melee weapons has been put into http://warframe.wikia.com/wiki/Module:Weapons/data

    I will work on the rest later, however I have recently made a few hundred edits and must rest now haha.

    To note, you are missing several weapons. Some that I recall are Prisma Obex and Jat Kusar, but I believe there may be more.

      Loading editor
    • View all 9 replies
    • That variant thing has proven true for Primary and Secondary weapons, however, there are a few special cases in Melees. For example, Dragon Nikana has a 5/5, while Nikana and Nikana Prime both have 1/5. So be wary of that when editing them in.

        Loading editor
    • Dragon Nikana isn't a typical variant though. Prisma, Vandal, Prime, and Wraith all share the disposition. For example, a Latron riven will work on the Latron, Latron Wraith, and Latron Prime. A Nikana riven will not work on the Dragon Nikana. Don't worry, I'm familiar with the system haha.

        Loading editor
    • A Lone Tenno
        Loading editor
Give Kudos to this message
You've given this message Kudos!
See who gave Kudos to this message
Community content is available under CC-BY-SA unless otherwise noted.