Minecraft Wiki:Admin noticeboard/Archive 31

Missing CSS
I seem to be missing a few CSS classes, and nothing I try – except going incognito – will fix this. This is what Special:RecentChanges looks like to me:. Please help. – Nixinova  03:25, 9 June 2018 (UTC) Also the "Preview", "edit", and "changes" buttons don't appear when editing. – Nixinova  05:37, 9 June 2018 (UTC)


 * Try clearing your cookies of this page. It may work. skylord_wars (talk) 06:09, 9 June 2018 (UTC)
 * Yes! Thank you. – Nixinova Grid_Book_and_Quill.png Grid_Diamond_Pickaxe.png 08:03, 9 June 2018 (UTC)

Editing page errors
All JavaScript won't work when I'm editing a page. Does not happen when viewing source of page or adding new section. Errors in console: Exception in module-execute in module ext.visualEditor.targetLoader: ReferenceError: locat1on is not defined ReferenceError: locat1on is not defined at eval (eval at (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=hydra&version=1rkfg73:4), :567:477) at eval (eval at (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=hydra&version=1rkfg73:4), :564:6402) at new Uri (eval at (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=hydra&version=1rkfg73:4), :564:6588) at eval (eval at (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=hydra&version=1rkfg73:4), :589:2644) at mw.loader.implement.visualeditor-loaderror-message (eval at (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=hydra&version=1rkfg73:4), :593:622) at Object. (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=hydra&version=1rkfg73:161) at fire (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=hydra&version=1rkfg73:45) at Object.add [as done] (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=hydra&version=1rkfg73:45) at Object.always (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=hydra&version=1rkfg73:46) at runScript (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=hydra&version=1rkfg73:160) Exception in module-execute in module ext.echo.init: ReferenceError: locat1on is not defined ReferenceError: locat1on is not defined at eval (eval at (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=hydra&version=1rkfg73:4), :567:477) at eval (eval at (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=hydra&version=1rkfg73:4), :564:6402) at new Uri (eval at (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=hydra&version=1rkfg73:4), :564:6588) at load.php?debug=false&lang=en&modules=ext.MsUpload|ext.echo.init|oojs-ui-core%2Coojs-ui-widgets|oojs-ui.styles.icons-editing-advanced&skin=hydra&version=05rfiks:126 at load.php?debug=false&lang=en&modules=ext.MsUpload|ext.echo.init|oojs-ui-core%2Coojs-ui-widgets|oojs-ui.styles.icons-editing-advanced&skin=hydra&version=05rfiks:129 at Object. (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=hydra&version=1rkfg73:161) at fire (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=hydra&version=1rkfg73:45) at Object.add [as done] (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=hydra&version=1rkfg73:45) at Object.always (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=hydra&version=1rkfg73:46) at runScript (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=hydra&version=1rkfg73:160) Exception in module-execute in module ext.visualEditor.desktopArticleTarget.init: ReferenceError: locat1on is not defined ReferenceError: locat1on is not defined at eval (eval at (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=hydra&version=1rkfg73:4), :567:477) at eval (eval at (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=hydra&version=1rkfg73:4), :564:6402) at new Uri (eval at (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=hydra&version=1rkfg73:4), :564:6588) at eval (eval at (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=hydra&version=1rkfg73:4), :574:794) at mw.loader.implement.css (eval at (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=hydra&version=1rkfg73:4), :589:220) at Object. (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=hydra&version=1rkfg73:161) at fire (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=hydra&version=1rkfg73:45) at Object.add [as done] (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=hydra&version=1rkfg73:45) at Object.always (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=hydra&version=1rkfg73:46) at runScript (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=hydra&version=1rkfg73:160) Uncaught ReferenceError: locat1on is not defined at Object.getParamValue (eval at (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=hydra&version=1rkfg73:4), :24:58) at HTMLDocument.eval (eval at (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=hydra&version=1rkfg73:4), :499:564) at fire (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=hydra&version=1rkfg73:45) at Object.fireWith [as resolveWith] (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=hydra&version=1rkfg73:46) at Function.ready (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=hydra&version=1rkfg73:49) at HTMLDocument.completed (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=hydra&version=1rkfg73:49)


 * Nevermind, just by clearing cookies fixed it – ITechieGamertce 07:34, 17 June 2018 (UTC)

Abuse filter for Java Edition hardware performance/entries
So many entries added by IPs are completely empty (see history). Maybe a filter could be set up to prevent it? --AttemptToCallNil (report bug, view backtrace) 16:45, 12 May 2018 (UTC)
 * Personally I consider this extremely excessive vandalism instead, I'd vote for semi-protection. – [ Jack McKalling ] [ Grid Book.png Grid Book and Quill.png Grid Diamond Pickaxe.png ] 07:49, 13 May 2018 (UTC)
 * More likely to be testing than vandalism, I think. --AttemptToCallNil (report bug, view backtrace) 07:50, 13 May 2018 (UTC)
 * But still, I think that page should only be edited by trusted editors instead of everyone (because of this excess of malformed edits). There is a warning message on the page with instructions below it. Even in the edit form there are custom instructions. It's just no excuse IMHO to keep doing this like they have. I feel like if these IP editors cannot behave as requested, the page should get protected from them. – [ Jack McKalling ] [ Grid Book.png Grid Book and Quill.png Grid Diamond Pickaxe.png ] 10:08, 13 May 2018 (UTC)
 * ...Why do we even have that page in the first place? --AttemptToCallNil (report bug, view backtrace) 10:11, 13 May 2018 (UTC)
 * I don't know, I'm just defending the case of the page. It's been going on for more than half a year. – [ Jack McKalling ] [ Grid Book.png Grid Book and Quill.png Grid Diamond Pickaxe.png ] 10:13, 13 May 2018 (UTC)
 * Putting aside the fact whether the page should be kept at all, I've drafted an abuse filter which when testing against the recent changes to that page, prevents all of the blank entries from being added and does not have any false positives so far. There are a few cons to using the current abuse filter, and I'm sure there are multiple ways it could be improved by somebody who's more advanced with AF coding than me:


 * It currently only works for users with less than 10 edits, meaning that if somebody made more than 10 edits and then added a blank entry it would succeed
 * This one's probably the worst of all - if a user made less then 10 edits, they can't revert an edit adding a blank entry, because abuse filters apparently cannot detect the number of bytes added in an edit - only the number of bytes changed, which is... very annoying. With my last revision, this is no longer the case. The abuse filter will now allow an edit to be made that has a change size of 188 bytes IF it removes the text "{{HardwareEntry", meaning that users who made less than 10 edits should be able to revert blank entries now just fine.
 * If anybody adds or removes even 1 character, the edit would succeed, due to the abuse filter only disallowing the edit if it adds exactly 188 bytes.


 * I'm currently going to be changing a lot of stuff with the draft to see how it works, so some of these problems may be fixed.-- Madminecrafter12 {{sup|Orange Glazed Terracotta.png to meLight Blue Glazed Terracotta.png}} 20:56, 29 June 2018 (UTC)


 * I just went ahead and added the AF - when I tested it it disallowed all of the edits that added blank entries, and didn't hit any false positives. We may eventually just delete the page, but I do think the abuse filter will be very helpful in the meantime or if we don't end up deleted it.-- Madminecrafter12 {{sup|Orange Glazed Terracotta.png to meLight Blue Glazed Terracotta.png}} 13:09, 3 July 2018 (UTC)

Why do we even keep Java Edition HW performance data?
What's the purpose of users submitting their JE performance data?

Pro:

Contra:
 * There are external benchmarking software programs, some of them with more maintained and comprehensive result databases, which may also include submission verification.
 * There are official system requirements, and a free demonstration version to determine whether/how your computer runs MC.
 * A substantial portion of users are likely to use unofficial content which impacts performance (such as modifications or higher/lower resolution texture packs), making vanilla measurements not very useful.
 * Users are submitting bogus entries almost all the time. We have to revert it.
 * There are just too many factors affecting PC performance in general, far more than on mobile devices.

I propose we delete Java Edition hardware performance and all related pages. --AttemptToCallNil (report bug, view backtrace) 10:28, 13 May 2018 (UTC)


 * Bedrock Edition hardware performance isn't at all scientific either, so also isn't useful. –Majr ᐸ Talk Contribs 11:06, 13 May 2018 (UTC)
 * Shouldn't it be archived and protected instead like with the old issues pages? - MinecraftPhotos4U (talk) 11:26, 13 May 2018 (UTC)
 * Aren't issues pages just as pointless now? Oh, and there's recently been a proposal to unprotect issues pages.
 * The problem is maintenance. Unless it's deleted, we have to maintain it. --AttemptToCallNil (report bug, view backtrace) 11:29, 13 May 2018 (UTC)


 * Issue pages document historical bugs. If we knew all that data was documented elsewhere (maybe even including who reported it?), such as the issue tracker, then they could be deleted. The hardware performance pages don't contain any reliable information to begin with, so there's no reason to archive them. –Majr ᐸ Talk Contribs 11:42, 13 May 2018 (UTC)
 * Letting users to submitting their performance data is complete useless. People only see the minimum requirements and recommended requirements. This page should only show the requirements, not the performance. The page Server/Requirements is long not updated. Server software from Mojang is completely free, so there is no need to worry. List of request for deletion page:
 * Java Edition hardware performance
 * Java Edition hardware performance/entries
 * These pages should instead be redirected to Java Edition hardware requirements. Skylord wars (talk) 11:53, 13 May 2018 (UTC)


 * Pinging as he is the main maintainer of the Java Edition HW page. – KnightMiner  · (t) 23:53, 14 May 2018 (UTC)
 * Didn't receive a notification for this, thanks Internet!
 * Anyway, I have to agree that even with all the effort that we put into this to keep the benchmarks semi-reliable for the benefit of others .. it's definitely not the best way to go about benchmarking and sharing data seeing as the way we ask users - with full trust not to manipulate or poison the end results - to get that data is based on opinion of what may work best. It's sad to think that to hours of work I put into it are a bit of a waste but yet that seemed rather inevitable when I started. I can't see this data being useful for future use as most modern machines will run this software just fine anyway. I can see it being good for only archival use going forward. -- RhythmicDaze (Edits)

It looks like there is consensus that these pages should not be kept. Given these pages were rather prominent, it is likely they should be redirected instead of deleting, possibly with notices at redirect target pages.

A proposed list of redirections follows:
 * 1) To Java Edition hardware requirements:
 * 2) Java Edition hardware performance, with all subpages deleted instead of redirecting.
 * 3) To Bedrock Edition:
 * 4) Bedrock Edition hardware performance,
 * 5) Bedrock Edition hardware performance (Android),
 * 6) Bedrock Edition hardware performance (iOS)

Other notes:
 * Hardware performance currently redirects to the JE page, but could be turned into a disambiguation page. Same with Hardware requirements.

Requesting comments. --AttemptToCallNil (report bug, view backtrace) 09:51, 13 June 2018 (UTC)


 * Looks good – Jack McKalling [ Grid Book and Quill.png Grid Diamond Pickaxe.png ] 09:59, 13 June 2018 (UTC)


 * Sounds decent, though I would redirect one of Hardware performance to Hardware requirements rather than keeping separate disambig articles, especially since the performance pages already will redirect to requirements. – KnightMiner  · (t) 15:06, 13 June 2018 (UTC)


 * Should I perform the proposed actions with KnightMiner's amendment? I will assume the answer is "yes" unless someone objects and explains the objection. --AttemptToCallNil (report bug, view backtrace) 18:02, 29 June 2018 (UTC)


 * Acting on it now. --AttemptToCallNil (report bug, view backtrace) 09:59, 13 July 2018 (UTC)
 * Cleanup task is completed. No double or broken redirects remain. Links to deleted pages in userspace have not been addressed. --AttemptToCallNil (report bug, view backtrace) 10:11, 13 July 2018 (UTC)

Simple edit - unable to submit
Trying to submit the new design for a clock circuit:

Dropper-Dropper clock
Simple design that does not require iron or pistons of any kind: https://www.youtube.com/watch?v=KJLxY6q7GxA

I understand the wiki has a rule that prevents new users from posting link. Please review the above edit and add to the "Clock circuit" page. –Preceding unsigned comment was added by 103.10.197.194 (talk) at 12:33, 27 April 2018‎ (UTC). Please sign your posts with


 * . MarcelTheHippie (talk • contribs • logs&#32;• block log) 🐷🥕☮️ 02:35, 28 July 2018 (UTC)

despawning mechanics edit
I was adding a little part to the page spawn in the section about +128 blocks away despawning, but a filter prevented me to make the edit, and I can't even write my text here. what am I supposed to do now? --Mortealre (talk) 22:41, 23 June 2018 (UTC)


 * - thanks for reporting. I went ahead and added that to the Spawn page (and given you the credit =)), modifying a few grammatical/spelling errors and slightly rewording a sentence or two. I've been looking at the abuse filter rule 6 (the rule that your edit was caught in), and I'm not sure what word you added that triggered it. Somebody who's more advanced with abuse filter coding probably knows though, and this may be worth investigating. Anyways, once you've made 10 edits to this wiki you shouldn't be affected by that filter as well as most other filters.-- Madminecrafter12 Orange Glazed Terracotta.png to meLight Blue Glazed Terracotta.png 23:39, 23 June 2018 (UTC)


 * "Happen is" was the phrase setting off the filter; its processing ignores whitespace. I think that's been an issue before as well, though it doesn't come up much. -- Orthotopetalk 00:07, 24 June 2018 (UTC)


 * That one is hard to filter properly, because we cannot tell in prior, if they deliberately inserted spaces to write the filtered word, or just happen to put these two legitimate words together in a sentence. You can't filter out all the false positives from a filter, it'd be an endless fight to pluck all possible loopholes. But excluding this word combination from the filter could work until someone else finds another false positive... – Jack McKalling [ Grid Book and Quill.png Grid Diamond Pickaxe.png ] 11:00, 24 June 2018 (UTC)
 * thank you, I didn't think you could see my edit. --Mortealre (talk) 11:17, 24 June 2018 (UTC)
 * Normal users aren't able to see edits that were caught in the abuse filter, but administrators can. And as for the filter itself, there are two sections that words can be put into: a section where it disallows the words regardless of whitespace and special characters, and a section where it only disallows the word if there is no whitespace or special characters. We might should try moving the word to the second section, as "happen is" does seem like it would occur quite commonly.-- Madminecrafter12 Orange Glazed Terracotta.png to meLight Blue Glazed Terracotta.png 12:26, 24 June 2018 (UTC)
 * the trigger word to the second section mentioned, see below.-- Madminecrafter12 Orange Glazed Terracotta.png to meLight Blue Glazed Terracotta.png 22:07, 1 August 2018 (UTC)