User:ultradude25
| Main | Talk | User | User talk | Minecraft Wiki | Minecraft Wiki talk | File | File talk | MediaWiki | MediaWiki talk | Template | Template talk | Help | Help talk | Category | Category talk | Total |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 3,246 | 1,020 | 1,928 | 1,130 | 299 | 270 | 2,826 | 81 | 393 | 1 | 2,412 | 100 | 11 | 4 | 72 | 1 | 18,722 |
Hey there! I am an administrator on the English Minecraft Wiki (this one!). I prefer to do maintenance tasks over actual article editing; I also enjoy writing templates, doing image related things and long walks on the beach.
If you have a repetitive task you don't feel like doing, I have a bot called Overwatch AI – which uses the AutoWikiBrowser software – which I might be able to use to complete the task for you.
For interwiki linking, R2-D2 (run by Scaler) will take care of that eventually.
[edit] Contact
If you want to contact me, the more reliable way is to just leave a message on my talk page or e-mail me at mcwiki@matt-russell.com. If it's urgent, you might be able to find me on the #minecraftwiki IRC channel.
[edit] F.A.Q.
Q: How do you make those sexy block renders?
- A: Blender. It's a free program, but has a bit of a high learning curve, mainly due to its odd controls.
Q: I want to use one of your renders for a free/commercial (paid) purpose, can I?
- A: I don't have any problem with the renders being used for free purposes, although I do prefer it when people ask and have a crediting link back to the image on the wiki, my userpage (here) or my website, but this is mainly so anyone wanting to use the image can find the original, or knows who to ask if they want to use it or need a custom version made. It's also partially just out of interest to see what sort of things they're used for.
- For commercial purposes, it is best to ask me over e-mail (link in contact section). If used commercially without asking, then it is a breach of copyright.
[edit] To-do list
| Incomplete tasks | |
|---|---|
| Task | Status |
| Find a more IE < 9 compatible method of displaying minecraft skin's searchbar background, while also not making Opera misalign the search button. | |
| Write documentation for any templates that have bad documentation or are missing it that I understand. | |
| Completed tasks | |
|---|---|
| Task | Notes |
| Re-write Grid sub-page templates (e.g. {{Grid/Crafting Table}}) to be only layout pages, and move all base-code to {{Grid}}. Also improve grid's code in general (less images). | |
| Look into problem with the minecraft skin, where .suggestions is used for both the search bar at the tabs, and the search bar on the search page. | |
| Look into better methods to fix IE's issues with the navbox wrapping, otherwise at least try to fix IE 7 and below so they don't wrap every single line. | |
| File:PoweredRail.gif is too large to animate in the infobox. | Completed by CrazyBliep. |
| Make {{dec-hex}} less of a nightmare to look at. | |
| Create a new version linking template, and implement it into infobox templates and {{v}}. | |
| Delete all old Furnace grid/Crafting grid images. | |
| Make renders for all wool block colours and put them in an animated gif. | |
| Clean up archive pages. | |
| Make a render for wet farmland and put dry and wet farmland in an animated gif. | |
| Try to make a simple template for including standalone grid images into pages. | |
| Make image and invimage automatic by modifying Template:Block, Template:Item, Template:Food, Template:Mob and Template:Person to use #ifexist: {{BASEPAGENAME}} and use Grid images. | |
| Change any templates using File:No image.png to use File:No image.svg. | |
| Write documentation for templates I've created that are missing it. | |
| AWB all pages using Template:Crafting grid and Template:Furnace grid to use Template:Grid/Crafting Table and Template:Grid/Furnace. | |
Add |OA= <number> to all pages that transclude Template:Crafting grid and use a numbered output image. |
|
| Re-upload all numbered grid output images to have no number. | |
| Upload images for every possible input/output/fuel for Template:Furnace grid. | |
| Change grid templates to use the same images. | |
| Modify Template:Crafting grid and Template:Furnace grid to use transparent background versions of the input images for input and output. | |
| Replace all 64 grid numbers with a sprite. | |
| Make the main page more editor friendly. | |
| Re-render and re-upload all block images with correct lighting. | |
| Change all pages transcluding Table choice templates to use {{tc}} and add any missing ones. | |
| Create a template similar to this. | Completed by Gnu32. |
[edit] Scripts
[edit] Documentation tabs
Makes documentation pages act like their own namespace, adding "doc" and "doc talk" tabs to template pages.
// [[User:Ultradude25/docTabs.js]]
if ( mw.config.get( 'wgNamespaceNumber' ) === 10 || mw.config.get( 'wgNamespaceNumber' ) === 11 ) {
importScript( 'User:Ultradude25/docTabs.js' );
}
[edit] Editable rollback summary
Adds a button ([rollback
]) to rollback links, which will bring up an input box with the default rollback summary, so you can edit and expand on it.
// [[User:Ultradude25/editableRollback.js]] importScript( 'User:Ultradude25/editableRollback.js' );
[edit] Reference tooltips
Brings up a tooltip containing the related reference's text when hovered hover. This makes references much quicker and easier to use, instead of having to jump all over the page. Based on the reference tooltips recently added to wikipedia, however they are buggy and use a bad mix of jQuery and vanilla JS (making it was difficult to read, for me at least), so this is written from scratch.
I plan to add this script to the wiki by default at some point (want to test for a while, and add some settings), so only use this if you want it now.
// [[User:Ultradude25/refTooltip.js]] importScript( 'User:Ultradude25/refTooltip.js' );
[edit] Issue link summary
Currently broken until JIRA has CORS
Adds a title to issue tracker links created by {{bug}} with the issue's current status and its summary.
// [[User:Ultradude25/bugSummary.js]] importScript( 'User:Ultradude25/bugSummary.js' );
[edit] Code block links
Makes external links and wikilinks (including interwiki) clickable in code blocks (anything with a class of mw-code).
By default this applies to anything that looks like a link, however this can be limited to only comments by adding window.mcw.onlyLinkComment = true; before the importScript line. This requires a syntax highlighting script to mark comments with a "comment" class; Prism.js works out of the box, other highlighters may require the link script to be edited to look for a different class.
// [[User:Ultradude25/codeLinks.js]] importScript( 'User:Ultradude25/codeLinks.js' );
Adding the following styling to your usercss will allow the links to retain their colouring (from syntax highlighters), and also add an underline to them so it's still obvious they're clickable.
.mw-code a:not(:hover) {
color: inherit;
text-decoration: underline;
}