Why is https://warframe.fandom.com/wiki/Module:DropTables/data locked from editing? I created an account just so I can help you catch up with Xaku Prime Access relics and can't even edit the droptables.

Missing Sevagoth Prime, Sevagoth Prime's Shadow, and Shadow Claws prime stats, and labelling of "Asep prime" instead of Sevagoth prime. Also missing acquisition and crafting information.

Two of the status damage formulas on the blast damage page are cut off because they are too long!

If its possible, the required Voca from each rank to level up to Rank 5 should be added to the wiki page for ease of understanding how much Voca of each type you should save and trade for standing.

Ideally this is in the form of a dropdown list that changes the result with the selection, you should be able to select your rank and then be given a list of all the Voca, and maybe any additional required resources to fully rank up to rank 5 (Lanthorns, Stela, Credits, etc.)

If there is some wiki-tech-wizard willing to implement this that would be great or if there is an example of something like this in practice in another wiki, I'd love to take a look and take a shot at it myself.

EXAMPLE:

Your current rank is: [Rank 2]

You need:

Echo Voca: 11

Bellow Voca: 12

Shrill Voca: 8

Requirements to Rank Up from Each Rank:

From Rank 0 to Rank 5:

Echo Voca: 11

Bellow Voca: 12

Shrill Voca: 16

From Rank 1 to Rank 5:

Echo Voca: 11

Bellow Voca: 12

Shrill Voca: 13

From Rank 2 to Rank 5:

Echo Voca: 11

Bellow Voca: 12

Shrill Voca: 8

From Rank 3 to Rank 5:

Echo Voca: 11

Bellow Voca: 10

From Rank 4 to Rank 5:

Echo Voca: 10

Idk how to edit it so here you go: infobox for incarnon forms with aoe has the typo "from" instead of "form" in

"Incarnon From AoE"

PLEASE change the theme back!! I can't read anything on the new theme. It all blurs togeter and hurts my eyes. I"m sure this is an April Fool's joke but in the mean time I can't use the wiki at all.

Hey everyone! I'm here to share some general news on what's going on at Fandom as of the middle of March 2024, including technical updates and some other announcements.

Technical Updates

• A known issue with section editing by using the Visual Editor source mode (2017 source editor) is known - the entire page gets loaded instead of only the section being clicked on. The team is currently looking into a fix.

• Issues with usage of <bloglist> tags causing faulty rendering of code for the "Create blog post" button have been solved, with the corresponding button now displaying correctly. Other issues with button interaction continue to be looked into, though!

• An upgrade for CodeMirror (the syntax highlighting extension for the editors) will be tested by a few communities prior to being released to all wikis. There were many reported issues during our first update attempt last month, but local testing will help prevent more of those. (WARFRAME Wiki is not part of that early test. Only specific wikis that agreed to it beforehand are included.)

For more known issues, fixes and other details, feel free to visit the March 8 Technical Update (or also the previous one, from February 23).

Experiments and feature tests

• Visual Editor performance: Following a successful experiment, we increased the loading speed of VE in a recent update.

• Interactive Maps: Some experimenting has begun for Maps, with an option for visitors to mark in-game progress via checkboxes for collected items/visited locations. (For the wikis that are part of this, I have reached out to admin(s) already to give some details.)

• Welcome messages: A beloved feature from years ago could be making a comeback soon, as testing is happening to figure out if this makes sense. Experimenting on this will be very limited to begin with, but we'll see what happens!

Other announcements

• We have unleashed a new Community Culture blog series - a monthly post highlighting diverse people, programming, and entertainment topics. The February Community Culture post was the first post.

• Also published was our first Transparency Report, which shows data relating to Trust & Safety actions in 2023. This includes things like the number of rejected JS edits, closed duplicate/spam wikis, and more. (See announcement and the 2023 report.)

That's all for now, hope y'all are having a wonderful month!

I noticed After a Long time Of Reading this wiki that for some reason None of the Default Controller Buttons are Listed Beside what they would do (For Example, 3rd Abilities Only have the PC Keybind "3" and not Xbox's RB + B or Playstations RB + Circle Etc.) Instances of Controller Keybinds are Already on the Wiki in both The Key Bindings Page and the Abilities Page. But other than that I don't think the Controller/Non-PC Keybinds are Shown Anywhere Else.

This could be useful for New players who are learning and Dont know what the Specific Keybind is for a Certain Action, This Feature can also be useful for People Learning a New Control Scheme (like Controller -> Mouse & Keyboard or Vice Versa)

Is there a Reason For this? is it possible to make it so that there is an Option on pages that show Default Keybind to Pick Which Platform/Control Scheme is Shown?

I think the energy orb icon shouldn't be piss colored in text blocks (see e.g. Nourish description) in the white theme.

a filter is wrongly applied to the icon

Hey everyone!

This week, Fandom released an update to the VisualEditor, targeting the interface of both the Visual Mode and the VE - Source Mode (also known as the '2017 editor'). The goal is to improve the editing experience there to make it more intuitive than it use to be.

You can check the announcement blog from staff for more details and a bit of history behind these changes, and also the updated help page.

To summarize, some of the changes the team worked on are these:

• Some of the tools have been renamed (e.g. "paragraph" is now "normal text")

• Icons were shuffled around (e.g. the back and forward arrow buttons are now located on the far left rather than the middle)

• Some less-essential tools were hidden from view to make the initial editor view a little less overwhelming (but the tools are still accessible in dropdown menus)

• For the 2017 source mode: removal of the options available from the menu icon (the three stacked horizontal bars) -- To get those back, anyone can customize the toolbar to access them from there)

• For the 2017 source mode: the menu icon was used to replace the gear icon

You can also see an outline of these in the design mocks below:

VisualEditor - Visual Mode

VisualEditor - Source Mode (a.k.a. 2017 source mode editor)

Separate from this, some functionality changes have also happened to the older source editor (a.k.a. "2010 editor"). Those are unrelated to the VE changes, and some have been filed as bug tickets (for instance, a cursor not being visible on wikis using a dark skin).

If you have any questions or feedback to share, you're more than welcome to either reply here, or message me directly. Cheers, and have a nice Friday/weekend!

Hey everyone. I thought I'd summarize a bit of what's been going on in the past couple of months at Fandom in terms of features and other updates.

The Thanks extension is now optionally available for all wikis

• This feature allows you to thank other editors for specific contributions they made. After much testing, it has been included as an option for wiki admins via the Admin Dashboard.

• It can be toggled on/off at any point by admins, which is great for those wikis that are unsure and just wanting to test for a bit to see how it works.

• You can find more information about the feature itself in the help page written for it, as well as some history behind it in the announcement post published by staff.

Gamepedia wikis now display less ads for logged-in users

• Wikis that originally came from Gamepedia lacked the "don't show all ads" option Fandom wikis have. Happy to report this is no longer the case, and the ad display for logged-in users is limited to the main page, not regular content pages.

• (This isn't 100% relevant to this wiki, as it isn't a GP wiki - but given that this has been a controversial topic for a long time, it's important enough to be shared. Obviously a small step, but hopefully one that begins to address community concerns.)

Notifications for message reports were released back in November

• In response to user feedback about lack of visibility for reports, admins and Discussion moderators can now receive a new set of notifications for reported posts/messages in a wiki's social areas (Discussions, walls, comments).

• These are enabled by default for any admins/mods at their wikis and can be disabled at each wiki where you have one of these roles via the "notifications" tab in user preferences in case you prefer not to have the notifications for certain wiki(s).

• You can find more information about these in the announcement post made by Fandom staff.

The Quick Answers Dashboard is actively being tested by a set of wikis

• Quick Answers is a feature that adds a set of AI-sourced questions/answers to character pages. There was a disastrous release of these back in August, with many inaccuracies, and the feature had to be removed at the time. The current goal is to bring it back by providing much more admin control over the content.

• To that end, Fandom has been working on testing a new QA Dashboard with a few wikis. The dashboard allows inaccurate content to be reported, provides admins with the ability to alter answers, and also the option to reduce the amount of answers available. (You can find more info, as well as images of the dashboard itself, in the Quick Answers help page).

• There are no plans to expand the number of wikis trying it at the moment, and this wiki isn't part of the testing. (If that changes at any point, I'd expect admins to be consulted prior to the wiki taking part in testing, since it's optional.)

More news / technical updates

• A number of new experiments have been taking place and are either still running, concluding, or being planned for upcoming testing. You can find more information on these by checking Fandom's Technical Update posts, as well as more detailed posts on some of the experiments in the Fandom Stars Wiki.

• For details on current bugs recently fixed or being looked into, as well as other feature news, you can also check technical updates and other recent posts via the Fandom Staff Blog in Community Central.

There's precedent for groups of mods to have their own pages. Just to give a couple offhand examples:

https://warframe.fandom.com/wiki/Set_Mods

https://warframe.fandom.com/wiki/Category:Galvanized_Mods

Should we set up a page for Bond mods, so wiki goers can have a one stop shop for 'em? There's certainly enough of them to make such a page substantial (there's 14 of 'em at time of writing).

Greetings English wiki users - the official wiki for the game. Since you have more or less direct access to the creators of our favourite game, could the admins please ask the developers to provide the missing icons on the mod pages? Why would it be for me or anyone else? The answer is simple - to fill the wiki in other languages. The Ukrainian wiki, for example, uses the structure of different elements of the modifier image, where the icon is overlaid with frames and effects, creating an identical to in-game look. So we really miss square .png images for some modifications, like Rubedo-Lined Barrel and Prime version of it.

I have noticed that in some entries, for example the mod Jolt, that the current, relevant acquisition method is sometimes listed last, after all prior acquisition methods.

I posit that the method of acquisition in a historical sense is largely not of particular value to the average user visiting this wiki, and only serves to bloat the article and make it more difficult than necessary to glean the information people are actually searching for, especially when the most current acquisition method is listed last.

That is all to say, I hereby suggest that prior acquisition methods be moved into a 'Prior Acquisition' or 'Historical Acquisition' section around or sub-sectioned to 'Trivia', near the bottom of the article.

Thoughts?

I need an updated wiki discord link. I need to discuss matters with the AbilityU10.3 template.