Minecraft Wiki talk:Admin noticeboard

Halfway towards actually making admin pages. Nice.  A CLECTASIS   05:55, 7 February 2011 (UTC)

Delete Revision
All administrators now have the ability to delete individual revision in a page's history. You will see the changes on the page history view. This function should be used only in cases where a revision poses some threat to the community at large, such as the malicious link that was recently placed on the Programs and Editors page. If you have any questions regarding the use of this function, please ask. Thanks! -- Wynthyst  talk  20:06, 7 February 2011 (UTC)

Template useless due to restrictions

 * discussion moved from noticeboard
 * Look at the following examples (which i made quickly from existing small ASCII diagrams)
 * Tutorials/Nomadic Experience
 * Tutorials/Safe Home
 * Tutorials/Airlock
 * Tutorials/List of things to do to your shelter
 * Two that don’t work:
 * Talk:Tutorials/Branch Mining
 * Talk:Tutorials/Tree farming
 * You can see how much easier to use it is by the fact that nobody did what you suggested. This is because using is both tiresome and confusing. Also it would produce padding around the tiles. I can’t see any reason not to use a simple template instead of having to do a huge amount of work to get the same done in another way or producing ugly ASCII art which takes only ~10 keystrokes less than my template (For the name and the curly braces). – Flying sheep 13:10, 12 April 2011 (UTC)
 * PS: you say on your user page that you like working with templates. Why the harsh critique, then? Don’t you see the clear advantages, if you were the one to create most of the cool templates we use for similar tasks? I try to help the wiki with it, i’m not some sort of “competitor” in templatemaking who does it to “outshine” your work or something.


 * That looks neat and all, but the reason I'm opposed to it is the fact it needs limits upped, which makes it seem like it'd be inefficient. Thus making it better to just use the already existing ones.
 * However, I'd love to see you prove me wrong on that, I don't have any knowledge of how taxing the loops would be, but I'd assume Curse has that set to 100 for a good reason.
 * Also, you should be using the standard doc template. – ultradude25 ( T at 13:35, 12 April 2011 (UTC)


 * OK, i’ll gladly explain it to you: It needs to loop over every character which has to be transcoded to an image once. Then it retrieves the named parameter with the character name and inserts the BlockSprite for it. This is is one Hashmap lookup more than manually inserting templates. Hashmap lookups have approximately O(1) for small maps. That is the fastest possible execution duration.
 * The limit of 100 is default, so most likely Curse just hasn’t done anything with it.
 * Another solution needs to be more efficient than mine or more easy to use while giving comparably pretty output. Everything else I can think of has worse performance, is ugly, hard to write, or any combination of that. That includes the following solutions:
 * you suggested manually inserting Sprites. That’s a little bit more efficient, but uglier (padding around images), much harder to write, and near impossible to read (Giant blocks of template transclusions)
 * Already used is ASCII-Art, which is more efficient, but much uglier and equally easy to write. You can manually convert this into my template very quickly (rewrite the legend to use proper sprite names, and add a pipe character in front of every line).
 * My alternative template (one parameter per sprite) is again a litte bit more efficient and equally pretty, but harder to write and read (rows · cols more pipe characters to type. That matters.)
 * I’ll use the doc template. I won’t on small templates like Template:FakeImage or Template:Inline, though :) (edit: i see that you have already done this, thanks!)
 * Thanks for not becoming set on your initial opinion, Flying sheep 14:37, 12 April 2011 (UTC)
 * Thanks for not becoming set on your initial opinion, Flying sheep 14:37, 12 April 2011 (UTC)


 * Slight aside: from looking at the loop extension documentation and your code, where is the limit being hit? Like, is there a limit of 100 iterations per page that has #loop? Is there a limit of 100 for each call of #loop or what? 'Cause based on a glance at the documentation and your code, it seems like the limit for your template is 100 blocks wide. --JonTheMon 15:16, 12 April 2011 (UTC)


 * No, the limit is per-Page, not per Loop-invocation. See below. Every time a for- or while-loop is gone through, a counter is increased. When it hits the limit, the all further loops just yield an error text and stop. (You can loop over the arguments for free, which could be exploited to circumvent the limit. It would be difficult and less performant, though.) – Flying sheep 15:35, 12 April 2011 (UTC)
 * Test (2 90-Loops. If the limit is hit in the second run, it is per page, if it isn’t hit at all, the Limit is per transclusion):