 |
VOOZH | about |
|
VOOZH | about |
Minecraft Wiki Pending tasks
You can create a new task by using {{task}}.
Move hatnotes (about, main, for, disambig etc), message boxes, and infoboxes into that order according to the style guide where needed
Some of these may either require admin permissions or page unprotection.
<code>{ ... { ...}}</code> ↛ {{code|<nowiki>{ ... { ...}}</nowiki>}}[[#...]] with proper {{slink||...}} section links. (List of pages that still use the #links)We're missing all 1.15 transparency changes (block items no longer allow it, neither do paintings, shulker heads, etc.), these should all be added to the history sections.
to give Helpful Answers and response to various thing that can happen in chat
Responses Make a Official Suggestion in chat Response Make a Official Duplicate Topic Response Make a Official Non-Affiliation Response
Requests Make a Official Technical Page Editing Request Message Make a Official Page Deletion Request Message
1. Move all outdated forms and texture update files to JEN BEN.
2. Move the non-revision version of the objects to revision files and leave a redirect.
3. Update all usages of the files to refer to JEN BEN, EXCEPT when it has to show the latest revision (eg history VS infobox).
4. Make all revisions of an object inherit a table from the first revision that contains links to all revisions and the versions they existed in.
5. If a new revision is added, add it to the list, and make the non-revision redirect to that.
Project page: MCW:Projects/Texture Update Cleanup.
These images are horribly outdated and no longer used on this wiki. They're in Category:Awaiting deletion and mostly all grid images.
These pages require a lot of information aggregation from existing release pages, collecting all of the added and changed content, and related useful (but compact) information about it. See the existing guides on the main page for how it should look.
Hey folks! We are rapidly outgrowing the "addons" page for Bedrock as the scripting stuff doesn't really fit under that anymore since those are part of the modding API and not add-ons specifically. As we expand the scripting engine and MoLang, we have more documentation for it but I thought maybe we'd want to reorganize things before we put in more.
Half this page is misinformation (i.e. conflates RTX as RenderDragon, when RenderDragon is just the graphics layer that made RTX support possible), and most of it is based off tertiary sources that aren't really accurate at all. A more accurate source for the RTX stuff specifically would be:
Additional first-hand sources are:
NBT data does exist in bedrock edition, but (basically) all documentation for it is missing.
The parity issue list is supposed to list all differences between bedrock and java, which means all their edition specific information, thus going through these categories and adding everything should be done. (also make them link to the parity issue list)
These guides are made by Jjlrjjlr. They summarize all additions and changes of all minor releases of a major update in a simplified, visual way. They would do very well with a nav box similar to {{version nav}}, such as "Template:Guide nav", so you can navigate between them while you're on one. I'm thinking it should for instance contain:
{{Guide nav}}. – Nixinova 👁 ImageThe documentation for InvSprites (and potentially, large mod sprites on non-English wikis) otherwise exceeds performance limits and stops working, even though the template itself is functional (i. e. sprites can still be used in pages).
Thoughts on implementation: a module calling loadData on the sprite data module, encoding the data to JSON. A JS function that makes an API request to action=parse with an #invoke of this module and scrapes the returned HTML for the JSON. (May need to have the module place the JSON text in pre tags and escape all less-than signs with \u003c - for JSON, they are only valid when within strings.)
Many templates (such as {{Sound table}} as of the time of writing) and modules are not categorized, making it hard to find them. This is not limited to templates shown on Special:UncategorizedTemplates, since some templates are automatically put into giant categories such as this, but no others.
A template where it is used on pages that are in the progress of splitting. This will make people copy from the other page.
This may not be necessary but I think it's a little better than putting regular "Work in progress" template. This can also be a parameter for the existing one.
