Feed The Beast Wiki:Administrators' noticeboard/Archive

Setup stage

 * Set up CAPTCHA on the wiki.
 * Set up an IRC channel for the wiki.
 * Clean up the Community portal
 * Protect important pages.
 * Require email confirmation.
 * Configure ConfirmEdit CAPTCHA trigger settings.
 * Setup group permissions.
 * Add the Nuke and Renameuser extensions.
 * Remove unused accounts.
 * Inform team members about their new responsibilities.

Testing stage

 * Test user rights.
 * Test account creation.
 * Test email confirmation.
 * Test CAPTCHA triggers.

Finalization stage

 * Grant group ' ':.
 * Grant group ' ' (all):.
 * Rebuild statistics.

Post-finalization stage

 * Announce on forums.
 * Start recruiting new team members.

Vandalism and Spam

 * New page spam/vandalism response time (delete):  N/A   N/A   N/A
 * Spam/Vandalism response time (revert):  N/A   N/A   N/A
 * Consecutive spam/vandalism response time (rollback):  N/A   N/A   N/A
 * Excessive spam/vandalism response time (protect):  N/A   N/A   N/A
 * User spam/vandalism response time (notify).
 * User spam/vandalism response time (warn).
 * User spam/vandalism response time (block) (>5 counts):
 * Excessive user spam/vandalism response time (nuke):  N/A   N/A   N/A

Quality assessment

 * Tag bad articles with template (community):  N/A   N/A   N/A
 * Tag bad articles with template (staff)
 * Fix/Resolve (community):  N/A   N/A   N/A
 * Fix/Resolve (staff):  N/A   N/A   N/A

Maintenance

 * RFD (normal):  N/A   N/A   N/A
 * RFC (deletion):  N/A   N/A   N/A
 * Patrol (revision)
 * Patrol (new page)

Requests and Help

 * Help desk (community):  N/A   N/A   N/A
 * Help desk (staff/sysop):  N/A   N/A   N/A
 * IRC help (community):  N/A   N/A   N/A
 * IRC help (staff/sysop):  N/A   N/A   N/A
 * Admin noticeboard:  N/A   N/A   N/A
 * Staff noticeboard:  N/A   N/A   N/A
 * Translator noticeboard:  N/A   N/A   N/A
 * Bot operator noticeboard:  N/A   N/A   N/A
 * Issues:  N/A   N/A   N/A
 * RFC:  N/A   N/A   N/A
 * Skin bugs:  N/A   N/A   N/A
 * AFC submissions (accept):  N/A   N/A   N/A
 * AFC submissions (review):  N/A   N/A   N/A
 * AFC submissions (merge):  N/A   N/A   N/A

New extensions proposals

 * mw:Extension:TitleBlacklist
 * mw:Extension:AbuseFilter
 * mw:Extension:FlaggedRevs
 * Discussion
 * I like this extension because staff can review and assess the quality of the article at the same time, administrators can also stabilize the quality of pages with a tool included. -- Jinbobo SysOp &middot;&#32;BotOp &middot;&#32;talk &middot;&#32;contribs 11:29, 4 July 2013 (UTC)
 * Poll
 * This poll will end in 1 day.
 * Support: Please add done and a comment if you want this extension to be installed.
 * Against: Please add done and a comment if you want this extension to not be installed.
 * Conditional support: Please add partlydone and a comment if you want this extension to be installed only under some circumstances.
 * I think this is a good idea. -- auris331
 * This should be good, provided we can quickly learn the new system. -- AgentTadpole Staff &middot; talk &middot; contribs 12:24, 4 July 2013 (UTC)

Blacklisting new account names
We have figured out a few username patterns that spambots like to use, we will be blocking these usernames that match these regex patterns in the near-future, use Jinbobo's Blocked username list to test the following regex, by default, patterns are case insensitive:
 * Usernames with 4 or more consecutive consonants (Easy fix for real users is to add a space between words?)
 * Pattern:
 * Usernames with 3 or more consecutive capital letters (Case sensitive)
 * Pattern:
 * Usernames with 2 or more consecutive capital letters at the end (Case sensitive)
 * Pattern:
 * Usernames with 2 or more consecutive numbers
 * Pattern:
 * Usernames containing the following words: car, limo, home, house, service, move, moving, guide, clean.
 * Pattern:
 * Usernames with 20+ letters.
 * Pattern:

Upgrading mediawiki software to 1.22.2
This checklist can be viewed at after the database has been locked.

Pre-upgrade checklist

 * Backup database.
 * Backup files.
 * Download & extract mw 1.22.2 tarball.
 * Configure staging site.
 * Lock database.
 * Backup database again.
 * Backup files again.

Upgrade checklist

 * Copy & paste LocalSettings.php
 * Upgrade extensions:
 * mw:Extension:CheckUser
 * mw:Extension:Echo
 * mw:Extension:FlaggedRevs
 * mw:Extension:Nuke
 * mw:Extension:RenameUser
 * MLEB
 * mw:Extension:DynamicPageList (third-party)
 * mw:Extension:MsUpload
 * mw:Extension:ParserFunction
 * mw:Extension:SyntaxHighlight GeSHi
 * mw:Extension:Variables
 * mw:Extension:AbuseFilter
 * mw:Extension:ConfirmEdit
 * mw:Extension:SimpleAntiSpam
 * mw:Extension:Title Blacklist
 * mw:Extension:TorBlock
 * mw:Extension:CodeEditor
 * mw:Extension:WikiEditor
 * Execute maintenance/upgrade.php

Post-upgrade checklist

 * Install extensions:
 * mw:Extension:CategoryTree
 * mw:Extension:GettingStarted
 * mw:Extension:PageTriage
 * mw:Extension:InputBox
 * mw:Extension:VisualEditor
 * mw:Extension:TemplateData
 * mw:Extension:AntiBot
 * mw:Extension:ApiSandbox
 * mw:Extension:BetaFeatures
 * mw:Extension:DismissableSiteNotice
 * mw:Extension:Gadgets
 * mw:Extension:GuidedTour
 * mw:Extension:SecurePoll
 * mw:Extension:Thanks
 * mw:Extension:WikiLove

Deployment checklist

 * Unlock database.
 * Deploy.

Allowing image uploads for "normal" people
Is there any reason why image uploads are disabled for "normal" people? It is quite annoying to have to post an image URL and wait for a sysop to upload it for you (like for Writing Desk and Talk:Writing Desk). It's not a big vandalism problem - I've been on a rather frequented wiki with image uploads active for anonymous, and have only seen a single case of upload vandalism in a few months. --dgelessus (talk &middot; contribs) 20:59, 11 October 2013 (BST)
 * In order to upload images, you simply have to be auto-confirmed, which means a few edits patrolled by the wiki team, and then you'll be able to upload images without any issues Retep998 (talk) 00:46, 12 October 2013 (BST)
 * actually you have to get 50 edits and your account must be 1 week old to get autoconfirmed. The reason you see no vandal on other wikis is because there are more active admins there. --  Jin bo  bo  04:34, 12 October 2013 (BST)
 * Let's say I've been actively watching the recent changes/logs, so I would've noticed anyway. Also, is "patrolled" the same as "checked" on this wiki, or is that separate? And will the annoying captchas be gone once I am autoconfirmed? --dgelessus (talk &middot; contribs) 10:37, 12 October 2013 (BST)
 * yes being autoconfirmed will allow you to skip CAPTCHA tests. Checking is limited to pages in the main and template namespace. --  Jin  bo  bo  16:17, 12 October 2013 (BST)

Server not responding after template edits
okay, you probably already noticed this - every time a template is edited the server stops responding for some time afterwards. Probably because it's updating all the pages, but normally the job queue should do that over time. --dgelessus (talk &middot; contribs) 15:09, 12 October 2013 (BST)
 * can you tell me what you were editing that caused this? --  Jin bo  bo  16:17, 12 October 2013 (BST)
 * Template:P and Template:Infobox. Not sure if Template:Navbox RedPower 2 did it as well... It only lasted a few minutes though. The server problems I posted about on the forums a few weeks ago were probably the same thing. --dgelessus (talk &middot; contribs) 18:03, 12 October 2013 (BST)
 * I'll try work with the web team to figure out this problem, but no promises, we've tried some stuff already but none seems to work. --  Jin bo  bo  19:27, 12 October 2013 (BST)
 * Okay, I'm no expert on this, but have you already tried setting the job queue's rate lower? AFAIK that's what updates the templates transcluded onto pages. --dgelessus (talk &middot; contribs) 19:36, 12 October 2013 (BST)
 * ok, will take a look when I have the time. --  Jin bo  bo  21:21, 12 October 2013 (BST)

Verification questions for signup page error on some correct answers
May want to change these so that people can more reliably sign up to help improve the wiki: I wasn't able to sign up successfully until the question of who created Redpower 2 came up. (I was signed up last summer, but it looks like the mediawiki upgrade dropped my account or something NBD.) TheAtomicOption(talk &middot; contribs) 14:26 03 May 2014 (PST)
 * "Notch" was not accepted for the question who was the original developer of minecraft?
 * "Jeb" was not accepted for the question what is the nickname for one of the current minecraft developers
 * The answer to who founded the FTB pack was not readily available via search. Most sources just say "FTB is a group of people".
 * The current captcha software is broken. The Notch and Jeb answers should've worked. The answer to the Founder question are various forms of "slowpoke101". This is a problem we are looking into. --  Satanic Santa Admin • Editor  22:49, 3 June 2014 (BST)
 * Yeah, I fought so hard to implement the new CAPTCHA system cause I thought it'd work. Guess I've been shown up, huh. -- AgentTadpole &middot; Former Staff talk contribs 11:23, 4 June 2014 (BST)

new mw release
Contains significant new features and critical fixes. Plz update. 1.23.0 release notes --  Jin bo  bo  10:22, 5 June 2014 (BST)

Wiki issues
I really would like to contribute to the wiki, but I am finding it too slow to load pages, especially for tasks such as edit previews. Difficult to reproduce reliably, but I have noticed that page loads slow down considerably every 10 minutes or so, for roughly 5 to 10 minutes. By slow I mean it can take from 10 to 30 seconds for the browser to go from "Waiting" to loading content. Things checked/relevant:


 * I am connecting from the UK with no proxy settings (unsure if ISP does connection tampering or caching)
 * During testing, I had no other connectivity/page load issues at the time (tested with Google, github.com, etc.)
 * Tested over a period of three days
 * Previewing pages seems to worsen the problem twofold
 * No issues when browsing http://feed-the-beast.com
 * Tracert results seem to be normal
 * Tested on both Chrome and Firefox; former with Adblock, latter without
 * As the admins are already aware, there was a 504 (Gateway Timeout) issue preventing the wiki from loading at all on the night I signed up (9th November)

Is it just me affected by this problem? Is there anything I could do to fix it?

A more minor issue I have also found is that the results of the "Preview" tab are inaccurate compared to using MediaWiki's preview button. I would prefer to use the Preview tab but this isn't a big deal compared to the speed issue.

Other than that, I feel I must say I like how very well organized this wiki is, from the Manual Of Style to the category hierarchy to templates. Nice work! -- VanDerProtofsky (talk) 10:15, 11 November 2014 (GMT)


 * The problems with slow page loading are well known and occur to everyone. Once we transition over to Gamepedia, we'll be able to get any remaining slowdowns investigated properly and fixed. The issues with the preview tab are also well known and will be investigated soon. In the mean time just bear with us.  R e t e p 9 9 8 Bunny Overlord•talk•contribs 10:33, 11 November 2014 (GMT)


 * Understood; thank you for the prompt response -- VanDerProtofsky (talk) 10:44, 11 November 2014 (GMT)

Problem with account settings (I hope this is the right place !?)
When I go into the settings of my account, I get the following error message: Interner Fehler

[28503122] /Special:Preferences Exception from line 341 of /home/hydra/public_html/includes/htmlform/HTMLForm.php: Descriptor with no class for disablemail: Array ( [section] => echo/emailsettings )

Backtrace:

Does anyone know what is wrong? --LuminousLizard de-native / "en-B2" (talk) 13:53, 5 December 2014 (UTC)
 * 1) 0 /home/hydra/public_html/includes/htmlform/HTMLForm.php(356): HTMLForm::getClassFromDescriptor(string, array)
 * 2) 1 /home/hydra/public_html/includes/Preferences.php(117): HTMLForm::loadInputFromParameters(string, array)
 * 3) 2 /home/hydra/public_html/includes/Preferences.php(1232): Preferences::getPreferences(User, RequestContext)
 * 4) 3 /home/hydra/public_html/includes/specials/SpecialPreferences.php(58): Preferences::getFormObject(User, RequestContext)
 * 5) 4 /home/hydra/public_html/includes/specialpage/SpecialPage.php(379): SpecialPreferences->execute(NULL)
 * 6) 5 /home/hydra/public_html/includes/specialpage/SpecialPageFactory.php(506): SpecialPage->run(NULL)
 * 7) 6 /home/hydra/public_html/includes/Wiki.php(285): SpecialPageFactory::executePath(Title, RequestContext)
 * 8) 7 /home/hydra/public_html/includes/Wiki.php(588): MediaWiki->performRequest
 * 9) 8 /home/hydra/public_html/includes/Wiki.php(447): MediaWiki->main
 * 10) 9 /home/hydra/public_html/index.php(46): MediaWiki->run
 * 11) 10 {main}


 * I'll make sure our dev team takes a look. CrsBenjamin (talk) 16:38, 5 December 2014 (UTC)


 * Now it works. Thanks :) ! --LuminousLizard de-native / "en-B2" (talk) 20:41, 11 December 2014 (UTC)

Common.js
I noticed an unused function called "ModifySidebar" in the common.js, apparently unused anywhere and wondered if it was worth keeping? Cblair91 (talk) 13:03, 26 January 2015 (UTC)
 * Resolved in my JS cleanup Cblair91 (talk) 09:11, 27 May 2015 (UTC)

Problems accessing wiki pages like /dev/null
The problem arises from how the wiki does its links: it doesn't check for restricted characters, leading it to try to send anyone trying to get to the /dev/null page to the literal web address "/dev/null" because it tries to link to //dev/null. To actually access the /dev/null page you have to directly access the url "http://ftb.gamepedia.com/%2Fdev%2Fnull", which has the '/'s replaced with the URL encoding for '/': %2F.
 * We are well aware of this issue. This problem is something that can't be avoided as it a limitation of the website itself; however there was a quick fix made to circumvent this issue when the article was made which gives a fully operating link in the Navbox for the OpenBlocks mod. For quick reference the link in the Navbox targets /dev/null rather than the conventional location. -- Wolfman_123_ ·&#32;✉ F T B  Wiki Staff  01:31, 13 March 2015 (UTC)
 * Still suggest you create a page like dev/null for users using the search box. --  Jin bo  bo  16:27, 26 May 2015 (UTC)
 * Damn that's a mind screw. dev/null created. PaladinAHOne  Staff (talk) 08:12, 27 May 2015 (UTC)

Ftb.css
Just checking through your CSS and stuff, I notice you have a FTB.css, yet it's never directly imported/called/used? Cblair91 (talk) 07:49, 26 January 2015 (UTC)
 * That is the old theme from before we moved to Gamepedia. 🐇 R e t e p 9 9 8 🐇🐰 Bunny Overlord 🐰 07:53, 26 January 2015 (UTC)
 * So it's technically safe to remove? :) Cblair91 (talk) 13:03, 26 January 2015 (UTC)
 * Should be --  Satanic Santa F T B Wiki Admin 14:56, 26 January 2015 (UTC)
 * Needs deleting then :P Cblair91 (talk) 09:13, 27 May 2015 (UTC)

PLZ PATCH
Patch from commit df529ac. It's so annoying.

If you don't mind breaking the slide up and fade out animation, just add this to MediaWiki:Common.css:

Now the scrollbars in those syntax highlighting boxes are bothering me lol. --  Jin bo  bo  16:15, 26 May 2015 (UTC)

Yeah. --  Jin bo  bo  16:23, 26 May 2015 (UTC)

Fix for rainbow text and two flavors of repeating rainbow text. Patched just for User:Retep998. --  Jin bo  bo  06:53, 27 May 2015 (UTC)

Add a "show background" class for the crafting grids
Can the line  from MediaWiki:Common.css be changed to  ? This would make cg cells with the class "gridShowBackground" show the background on G/Cell for the sake of covering things like default backgrounds, as most in game cases hide that image (eg, the armor slots). Otherwise I would have to upload an additional image for each empty slot and add extra code to make sure it will display when the parameter is unset. Existing grid templates will be unaffected, so it is basically an "opt in" type thing. –KnightMiner t/c 16:35, 3 November 2015 (UTC)
 * <- it does already have the grey background? In fact you have to explicitly say for it to not to have a background -  Chocohead  Nag • Edits • Staff 17:01, 3 November 2015 (UTC)
 * It appears .craftingGridNoBg is currently ignored. It used to be that Cg templates had to specify that for each cell to disable that behavior, but it appears it was made to always hide the background by default., do you think we should reinstate the requirement for .craftingGridNoBg to hide the background? 🐇 R e t e p 9 9 8 🐇🐰 Bunny Overlord 🐰 18:49, 3 November 2015 (UTC)
 * Not sure. How much would it break things and how quickly and easily could it be fixed? Does it actually cause a problem, because I haven't really noticed any? --  Satanic Santa F T B Wiki Admin 19:19, 3 November 2015 (UTC)
 * It just means that the background visible in a standalone Gc call would also be visible in any Cg that doesn't use .craftingGridNoBg. It would be pretty simple to fix any Cgs that don't use it but should. A lot of Cgs already use it anyway. 🐇 R e t e p 9 9 8 🐇🐰 Bunny Overlord 🐰 19:37, 3 November 2015 (UTC)
 * Most of the templates I've seen have used it, along with me personally using it in the new templates I make when relevant. The main problem is you can no longer tell it to show the background, which causes the default cell background issue I mentioned above. –KnightMiner t/c 21:02, 3 November 2015 (UTC)
 * So wait, the change will basically be having to define it in the Cg as a whole, and will effect every cell in the Cg, rather than having to define it in individual cells? --  Satanic Santa F T B Wiki Admin 00:09, 4 November 2015 (UTC)
 * Look at Cg/Distillery/GregTech. Notice the . That's all a Cg would have to do to hide the background from Gc. Whether that background should be hidden or not depends on the Cg. For example, with GregTech the Gc backgrounds should always be hidden since you can clearly see the images in the slots from Greg's GUI's even when there is an item in them. 🐇 R e t e p  9 9 8 🐇🐰 Bunny Overlord 🐰 00:23, 4 November 2015 (UTC)

MediaWiki:Sitenotice
MediaWiki:Sitenotice can be cleared to "-" to remove it. It's been over a year, so any accounts that were worth merging have been merged. Just in case, I put said information on the FAQ. -Xbony2 (talk) 14:12, 6 February 2016 (UTC)
 * Done. I replaced it with something regarding our extensions. --  Satanic Santa F T B Wiki Admin 23:03, 7 February 2016 (UTC)

Xbony2 for Administrator/Bureaucrat
The reason I'm applying for both is because my current group proposal has them combined.

I'm Xbony2. I've been on this wiki for a fairly long time- I registered on wiki.feed-the-beast.com on July 15th, 2014. This is my first edit (you can see my userpage has evolved much since then). I became mod maintainer and part of staff on October 28th, 2014. But I didn't really start editing seriously until January 2015; during that month, I made at least a couple edits every day, usually more. Wiki editing slowly became my "major hobby" over programming mods. I figured out how to markup pages and deal with translation, and became translation administrator after a vote that started on the 21st of April 2015 and ended on May 4th (a few days after my birthday. Cool, huh?) (Retep announced it on May 5th, but the user rights change on the 4th).

Since then, I've been wiking away. I've [arguable] become the most active editor ever on the Feed The Beast Wiki, and one of the top editors on Gamepedia in general (trivia: I own a Gamepedia shirt, Gamepedia mug, Hydra plushie and some other junk after Gamepedia gave free stuff to the top 100 editors based on wikipoints). I've created the Translation Restoration project, as well as overhauled how pages are marked up and marked up a very large amount of pages (likely the majority of them). I've documented a lot of mods, the newer ones including Immersive Engineering and Avaritia. I've done a lot of maintenance work too, G fixes, category restructures, cleaning up of articles, etc. I've welcomed and been generally friendly (in my somewhat humble opinion) to new users. I created the IP award.

I would like to have full administration/bureaucrat rights. If you don't know what this means or includes, look at Special:ListGroupRights. The bureaucrat group has the largest amount of responsibilities, excluding Curse. The mort important rights is that it allows me to modify groups, to block users, to change protections, to edit the interwiki, to edit all pages, to edit stuff in the MediaWiki namespace, to nuke and to modify many internal settings/filters. If given, I will not abuse these powers, as I believe I have not abused my current rights.

Retep told me all staffs' vote counts, not just administrators. This is pretty reasonable; a two-person vote would be a bit lame. Since my vote for translation administrator was over a period of about 2 weeks, this vote will close on February 28th.

Update: After this application was created, SatanicSanta has given me banhammer rights. This makes a point or two invalid below. It is a bit disappointing to have to create a very wordy adminship application with much debate just to gain this right, even though I have requested it from the two administrators several times in the past, with them seemingly considering me eligible but not doing anything.

Update 2/Decision: Although some of the staff which haven't voted yet could vote support and I could become administrator/bureaucrat, I feel I couldn't accept it without a larger consensus (plus I don't imagine that would happen anyway). It is probable that I will re-apply for administrator (less probable for bureaucrat) at a future time, but I do feel like everyone got something out of this vote anyway; I've received the long merited banhammer (which is something I would argue that all staff should have, not just the crazy ones like me [though this can be discussed at a later debate]), and the current administrators have pledged to react faster to requests given to them. I'd like to thank everyone who voted, even the ones that voted against me (I'm still unfriending all of you on Facebook though).

Support

 * It took me more then an hour to right write this. -Xbony2 (talk) 12:01, 14 February 2016 (UTC)
 * Mhhhh .... it seems to be a great responsibility (where I know about it less than the admins). But he does already many tasks about the entire wiki and I think he will do that all right, and will support/relieve SatanicSanta and Retep998. But as always with higher responsibilities, he must think 1 times more about his actions. And he has a "Gamepedia Mug" .... that's the right equipment for a bureaucrat, then he only needs coffee.
 * To be honest, I don't like coffee and have never used the Gamepedia mug for that. I've used it for soda and orange juice though. -Xbony2 (talk) 12:42, 14 February 2016 (UTC)

Against

 * With banhammer rights (which I totally agree with you having BTW), I don't see the point in you having admin rights. With what you say you need, banning you've now got, update to rights it's clear Retep and Santa have got that covered with how infrequently it happens, and protected pages are protected for a reason. If they've been protected but shouldn't be, then they can just be lowered to Staff edit-only rather than Admin edit-only, or the protection removed completely. With pages like the main page or core templates that are admin edit-only, it's better than the edits to them are compacted down and offloaded to duplicate versions so that the wiki itself isn't effected until the changes are proved to be fine. There is, after all, no point in you having rights like edit filters and the interwiki table if you're never going to use them.  Chocohead Nag • Edits • Staff 22:17, 14 February 2016 (UTC)
 * --  Satanic Santa F T B Wiki Admin 22:24, 14 February 2016 (UTC)
 * I somewhat do too. However, I think that voting against me means that you and Retep will need to step up and cleanup some of the mess caused by you two's ignorant (as in ignoring the mess the wiki is) behavior. This includes cleaning groups, updating the Sidebar, and overhauling some of the MediaWiki namespace's messages to make it easier for contributors and new users to pointer to the wikis guides/guidelines/MOS, some of which are nonexistent or outdated. -Xbony2 (talk) 22:48, 14 February 2016 (UTC)
 * Fair enough. --  Satanic Santa F T B Wiki Admin 23:26, 14 February 2016 (UTC)
 * The main reason I ran for administrator was dissatisfaction with current administrational [lack of] actions. Ex. when requested to fix an issue on the Common.js which was easily fixable, asking Retep many multiple times just wasn't enough. It took over a week for it to be resolved, by you, who was at the time "in and out" of wiki editing and hard to reach. One week is seriously a bullshit response period. Things have generally improved since then, but I would have much hesitation before calling it perfect. -Xbony2 (talk) 23:36, 14 February 2016 (UTC)
 * , I don't feel good about giving power to someone who is asking for power. You are a competent editor but that doesn't necessarily translate to someone good at administrative things. I also do feel a minor pang of guilt for not having good response times to your requests for certain things to be done, so I'll try to improve on that which simply means not procrastinating and just doing things when asked. 🐇 R e t e p 9 9 8 🐇🐰 Bunny Overlord 🐰 12:50, 14 February 2016 (UTC)
 * If you don't ask, you don't receive, and little is done. I think my work as translation administrator/editor shows I would not be a terrible administrator. -Xbony2 (talk) 13:02, 14 February 2016 (UTC)
 * (I as well will work on doing shit when asked and not procrastinating as much anymore, so you won't be alone in this anti-procrastination journey) --  Satanic Santa F T B Wiki Admin 05:58, 15 February 2016 (UTC)

Neutral/Abstain

 * No comment. Cblair91 (talk) 12:07, 14 February 2016 (UTC)
 * , I feel rights should be given on a "will use the permissions given" status. As bony doesn't do, and has a lack of showing, that the permissions given from sysop/crat will be used in an advantaged manner, I vote against.Cblair91 (talk) 12:17, 14 February 2016 (UTC)
 * To prevent confusion, Cblair's vote is considered neutral/abstrain. See the CurseVoice conversation below.

(Addressing this comment in a minute) -Xbony2 (talk) 12:25, 14 February 2016 (UTC)
 * Cblair's point is that I do not need these rights. I disagree. I've had to request a large number of administrative/bureaucrative actions from Retep/Santa (usually the later), including edits to protected pages (especially Project:FTB Wiki Staff which took many requests to update, until thank god Santa removed the protection over that page), updates to user rights, and lastly (and most importantly) blocks. -Xbony2 (talk) 12:39, 14 February 2016 (UTC)
 * Blocking can be done without administrative rights through the banhammer usergroup. --  Satanic Santa F T B Wiki Admin 20:14, 14 February 2016 (UTC)
 * Supposable. I have requested this many times, and the general response has always been... "Should bony have banhammer? I dunno, do you know? I dunno". -Xbony2 (talk) 21:41, 14 February 2016 (UTC)


 * — I don’t have anything serious against appointing Xbony2 as an administrator, but why go for being a bureaucrat?! Xbony2, you are asking for that too soon. We already have two here, plus we have Curse staff. And you weren’t a fitting administrator yet to be applicable for a bureaucrat. — Agent NickTheRed37  ( Kirk to   Enterprise ) — Russian Translator and Minepedian 15:32, 14 February 2016 (UTC)
 * : I mentioned this already, but my current reformed group proposal has the group merged; unlike the MCW and wikipedia/wiktionary, this wiki isn't really big enough for there to really need to have a difference. Throughout the wiki history, there's only been one admin (AgentTadpole aka Nerixel) who didn't become a bureaucrat. My group proposal is just a proposal and isn't even finished yet (at the moment), but there hasn't been much stated disagreement with the idea. -Xbony2 (talk) 15:45, 14 February 2016 (UTC)
 * I don’t like having default rights merged. Some extensions might be confused by that, plus I just don’t like that (I don’t know why).
 * And, as a point of comparison, I would say that my own home wiki, the Russian Minecraft Wiki, is also “not big enough” so it could have the two groups merged, but what we have is apparently okay. We don’t need modifications to user rights. (We had a special “moderator” user group ages ago, and I even was a member of this group, but it was scrapped.) Alongside the only active bureaucrat user, we have a somewhat active regular admin, plus a nearly-inactive admin sometimes appears on the wiki.
 * And, Xbony2, just a personal thing: you’re too active. Don’t wear yourself down. — Agent NickTheRed37  ( Kirk to   Enterprise ) — Russian Translator and Minepedian 16:18, 14 February 2016 (UTC)
 * I'm opposed to merging admin and bureaucrat. While I am still somewhat neutral in your application to be administrator, I am opposed to you being a bureaucrat. There is simply no need for more bureaucrats as their power is needed very rarely to promote/demote staff which is never a thing that needs to be rushed. It is useful to have people that can be trusted to do technical things which is what sysop/admin should be, people who can muck about with the javascript and css and core templates without messing up the wiki. Bureaucrat is for a smaller group of people that only are needed when there is a staff promotion/demotion which is rare. Meanwhile the power to block is granted via banhammer which doesn't need admin. Having that separation is good. 🐇 R e t e p 9 9 8 🐇🐰 Bunny Overlord 🐰 21:15, 14 February 2016 (UTC)
 * Debate over group reform is something that should go on the Staff's Noticeboard at a later date. If you wish, you can vote " Xbony2 for administrator but Xbony2 for bureaucrat" or " Xbony2 for administrator but  Xbony2 for bureaucrat".
 * : don't worry too much about me. Wiki editing is more or less my passion, but it's not my only hobby; I'm healthy and happy, so I think I'm doing okay. -Xbony2 (talk) 21:54, 14 February 2016 (UTC)

Discussion
Looks like the goal is going to be “No”, isn’t it? — Agent NickTheRed37  ( Kirk to   Enterprise ) — Russian Translator and Minepedian 15:13, 18 February 2016 (UTC)
 * I closed it, remember? -Xbony2 (talk) 22:12, 18 February 2016 (UTC)

Fix for Template:T JavaScript
The recent MediaWiki update broke T, and from a quick test in my browser's console it can be fixed by changing the line in MediaWiki:Common.js from $( this ).children( '.tankLiquidImageContainer.minetip .tankLiquidImage' ).each( function { To $( this ).children( '.tankLiquidImageContainer.minetip' ).children( '.tankLiquidImage' ).each( function {

Can an admin please make the fix?

–KnightMiner t/c 02:57, 18 February 2016 (UTC)


 * Done 🐇 R e t e p 9 9 8 🐇🐰 Bunny Overlord 🐰 04:02, 18 February 2016 (UTC)

Common.js cleanup pt.1
Requesting for the deletion of the "insertUsername" section of the Common.js. This is a small script by Cblair91... it's ununused, and unfinished for that matter; USERNAME should be a created template, like here on her habbo wiki. Although it could be complete, and is generally a clever idea, it doesn't have much use other then as a cheap trick to impress/creep out the reader. -Xbony2 (talk) 11:23, 21 March 2016 (UTC)
 * Done --  Satanic Santa F T B Wiki Admin 17:14, 21 March 2016 (UTC)
 * Was it intentional that you deleted the  part of the code rather than the  ? In any case, the code from   does not seem to do anything. –KnightMiner t/c 19:06, 21 March 2016 (UTC)
 * Nope, I was half asleep when I did this :D --  Satanic Santa F T B Wiki Admin 19:08, 21 March 2016 (UTC)

Protection for safety
Most of the vandalistic attacks on this wiki have been arbitrary and aren't particularly offensive or effective. However, many of the templates and modules (as listed below) are unprotected, and any user can changed them. If someone with more serious motivates and higher technical skills was to to attack one of these (like a crazy competitor or evil ex-staff), it could break basically every page on the wiki, or at least a lot of them. Thus, I'm proposing these following pages be put into "editor"(+) protection. Although they could easily go for staff or even admin-only protection, there's a pretty small amount of non-staff editors (hint- it's pretty close to 0) and (in my opinion) they can all be trusted with very little risk. I'm a bit embarrassed these aren't already protected. Somebody add this to my list of why I want to be admin. May justice prevail (or something, I wanted to end this interestingly).
 * Navbar
 * Transclude
 * Gc (the redirect; G/Cell is already protected but the redirect everyone uses isn't...)
 * and
 * and
 * Cg
 * and
 * NI (the redirect again...)
 * Navbox subgroup
 * Navbox item/disambiguation and NID
 * Cg/Crafting Table
 * Clear
 * Tl
 * Navbox/Lazy
 * G/O and O
 * Navbox item/disambiguation and NID
 * Cg/Crafting Table
 * Clear
 * Tl
 * Navbox/Lazy
 * G/O and O

Also requesting for the unprotection of MediaWiki:Gadget-UTCLiveClock.js‎ and MediaWiki:Gadget-DotsSyntaxHighlighter.js‎, apparently Santa doesn't know pages in that namespace are automatically protected per default >.> -Xbony2 (talk) 13:14, 29 March 2016 (UTC)
 * Protection cannot be set to editor. It can be set to everyone, autoconfirmed, staff and admin, admin, or bureaucrats only. 🐇 R e t e p 9 9 8 🐇🐰 Bunny Overlord 🐰 13:55, 29 March 2016 (UTC)
 * Well, that's stupid. I guess staff would better. -Xbony2 (talk) 14:18, 29 March 2016 (UTC)

Done. I also protected Cg/Furnace. The /en pages cannot be protected because they cannot be updated manually. --  Satanic Santa F T B Wiki Admin 16:11, 29 March 2016 (UTC)