Gamepedia Help Wiki

This page is an archive of Talk:Requesting extensions. Please add sections directly to the live page, not here.


  • Extension: FixedHeaderTable
  • User: Game widow
  • Witcher wiki, Skyrim wiki, probably many others
  • I think this would be useful on many wikis that have long tables. Scrolling down long, complex tables, it becomes difficult to figure out what information is in which column.

Discord Notifications

  • Extension: Discord or DiscordNotifications
  • User: Darkpsy3934
  • Wiki to be used on: Oxygen Not Included and possibly others might be interested
  • Use case: This extension will send the wiki's recent changes to a specific Discord server and channel. Although it requires configuration, perhaps the dev team can come up with a way to allow wiki admins to change the settings from a Special Page.


  • Extension: PortableInfobox
  • User: TwoTailedFox
  • Wiki to be used on: Codex Gamicus
  • Use case: We still have old Infoboxes from our move that used the PortableInfobox code. I'd like to see how viable it is to keep those Infoboxes in that syntax, and see how it interacts with the Hydra mobile skin.

Threaded discussion

  • Threaded discussions offer many advantages over the current wiki model as explained here, so maybe install on all wikis except where consensus and/or the proprietor are opposed to the change.--Xanthipos (talk)
This is under review, but the extension has been essentially abandoned and many people do not like it, so no, it will never be *default*. --Pcj (T·C) 15:39, 20 February 2019 (UTC)
But they don't object to the discussion system on user profiles, this being almost the same.--Xanthipos (talk) 10:20, 22 February 2019 (UTC)
They do, but even then that's only on profiles. Not replacing every talk page. --Pcj (T·C) 01:52, 23 February 2019 (UTC)

I don't understand why so many people don't like it. So many web users are already used to such discussion systems, namely on forums and comments sections on blogs. Furthermore, there are many advantages to threaded discussion systems, such as automatic signing comments, these also having automatic timestamps, these can be relative. Older comments can be archived automatically. Furthermore, it is possible to have a technical restriction on which users can edit other users comments.

Actually, installing this extension on an existing wiki does not affect all talkpages, only talk pages created after installation of the extension. --Xanthipos (talk) 15:29, 1 March 2019 (UTC)


  • Extension: UrlGetParameters
  • Wiki to be used on: Terraria Wiki
  • This extension will enable to use and/or display the "GET" parameters of the URL, i.e. the query string, on the wiki page.

ReedemtheD3ad! (talk) 19:57, 13 March 2019 (UTC)

Denied because "caching for the page you use this extension on should be disabled" and caching will not be disabled for use of an extension. – ReedemtheD3ad! (talk) 20:00, 13 March 2019 (UTC)


  • Extension: Preloader
  • Wiki to be used on: Terraria Mods Wiki
  • This extension will enable the creation of boilerplate text which will be inserted into the edit form when creating new pages.

ReedemtheD3ad! (talk) 20:08, 13 March 2019 (UTC)

How is this different from Extension:BoilerRoom? --Alianin TC 20:27, 18 June 2019 (UTC)
Preloader would automatically add the text when editing a page, BoilerRoom required user input, unless I misunderstood. In any case, a workaround was found and the extension is no longer required. ReedemtheD3ad (talk) 16:51, 19 June 2019 (UTC)
Preloading is possible without an extension: --Alianin TC 17:34, 19 June 2019 (UTC)


  • Extension: Numbertext
  • Wiki to be used on: Terraria Wiki
  • The Numbertext extension allows to transform numbers into words. It based on the service and supports more than thirty languages.

ReedemtheD3ad! (talk) 15:41, 22 March 2019 (UTC)

  • What is the actual use case for this? --Alianin TC 20:27, 18 June 2019 (UTC)


  • Extension: CustomLogs
  • Wiki to be used on: All esports wikis, mostly LoL/COD
  • This lets me define & use arbitrary log types entirely via the MediaWiki namespace so backend access isn't required after installation of just this extension to add more logs/log types. I need this for use with a bunch of my gadgets, especially Refresh Overview & Refresh Teamnames, which require manual "recaches" but don't make any edits so I can track usage.

--RheingoldRiver (talk) 19:54, 9 April 2019 (UTC)


  • Extension: TemplateStyles
  • Wiki:
  • Desc: Allows creating sanitised stylesheet pages for templates, rather than having to write all the styles inline, or use an admin only and globally loaded file like common.css, making styling much more flexible, maintainable, and faster. Basically a more secure version of Extension:CSS (which is already approved), but without inline stylesheets, external files, or unsafe styling, and used and maintained by Wikimedia. Would make a lot of sense as a default extension to promote better styling practises and improve security and performance (less styling loaded per page, and less editors needing admin in order to use common.css for template styling).

06:11, 27 April 2019 (UTC)


  • Extension: GlobalCssJs
  • Wiki to be used on: Across all network
  • Great extension for cross-wiki editors, which allows them to use their global CSS and JS without any browser add-ons. Highly recommended for wikifarms.

Rail (talk) 08:22, 5 May 2019 (UTC)


  • Extension: Quiz
  • Wiki to be used on: Across all network / I'd like PUBG Wiki to be the test subject.
  • I think it would be pretty useful to have to engage and attract users to a Wiki more often to test users knowledge of Easter Eggs, locations, weapons, etc.

-- Azgoodaz (talk) 18:25, 6 May 2019 (UTC)

Header Footer

  • Extension: Header Footer
  • Wiki to be used on: LoL, cod-esports, smite-esports, any other of my wikis that I add top schedule to
  • I'm not sure 100% if this will do what I want, but it might be a way to stop loading the TopSchedule with JS and instead have it be part of normal page load.

--RheingoldRiver (talk) 19:12, 19 May 2019 (UTC)