User talk:AdiosToreador

Hey, just wondering, on the beacon block page, you took off a couple of trivia points, one being mine about it melting ice. I thought this was valid trivia for this block, what rule did I break, so I know in the future. Didn't want to just undo arbitrarily. Thanks. ...Dweller Benthos 18:58, 17 August 2012 (UTC)
 * Oh, I just removed it because all light sources past a certain brightness excluding the sun melt ice. Don't worry, you didn't break any rules and there's nothing wrong with adding what you think is valid trivia. --Moxxy 00:49, 18 August 2012 (UTC)

I agree that on the rotten flesh and egg article I put in information that was already there. But nowhere in the pumpkin article did it state that the way pistons interact with pumpkins (Besides the link to the auto melon farms)--Minecraftdino 22:49, 14 February 2012 (UTC)
 * It's there. --Moxxy 22:59, 14 February 2012 (UTC)

Delete tags
There is no need to tag the jp pages. -- Wynthyst  talk  00:55, 17 February 2012 (UTC)
 * Yeah, that's why I stopped. Bit of a derp moment on my part. Wish I could help you by deleting stuff starting with "z". You have a lot of work ahead of you.--Moxxy 00:58, 17 February 2012 (UTC)

Inventory
Well, I was in third person, I went into my inventory, and I noticed my players head (in the backround of the inventory) It was turning spinning and twisting like mad until I exited my inventory. Sorry it didnt make sense. --Heavy weapons pie 01:03, 28 April 2012 (UTC)

Golems
Couldn't something be said about how golems are created? They're the only mob that is "constructed", as well as the only entities in the game that aren't built in a gui (e.g.; table) of some kind.--Chilangosta 07:54, 24 February 2012 (UTC)
 * Disambiguation pages are usually fairly short; they're not meant to be an exhaustive comparison. I don't think it would be unreasonable to have a sentence making it clear that they're constructed by placing blocks in the correct configuration, though. -- Orthotope 08:36, 24 February 2012 (UTC)

Iron Golems and Endermen
I created a topic due to your edit: Talk:Iron_Golem.

I figured you wanted to be a part of it, due to my notion that you are very perfectionist about keeping things the way you think they should be.

Nether Generation in 1.2
Since you're feeling it like "not important enough to appear in the Version History page", where can we report that "The Nether generator isn't using the entire height, making the level 128 to 256 only accessible in Creative Mode" ?

Not a bug, but an important information, sorry.
 * Not a problem, I see you've already added it. It is indeed important info. --Moxxy 18:04, 1 March 2012 (UTC)

About 1.2.2
Hello. This problem doesn't occurred to you?--MisterSanderson 02:17, 2 March 2012 (UTC)
 * No, all my villagers are there. --Moxxy 02:18, 2 March 2012 (UTC)

Did the spamming stop?
I was reading the admin noticeboard and heard that you were getting spammed.Did it stop?

Biomes
Why did you undo my edits? It was only a little observation about how biomes generate after Beta 1.8...Ua 14:38, 12 March 2012 (UTC)
 * They grouped like that since they were added in the Halloween update. --Moxxy 14:54, 12 March 2012 (UTC)
 * I remember that it was different how biomes generate: from the Halloween Update to the Adventure Update I've never seen a desert next to a tundra.Ua 15:40, 12 March 2012 (UTC)
 * Just to chip in, I have seen deserts next to tundras. it is rare, but it happens. --Kizzycocoa 15:42, 12 March 2012 (UTC)

Ocelot
Why'd you undo my revision? The other half of the sentence wasn't really needed. Saying that the player entering a portal was enough. --Lolmaster 01:25, 13 March 2012 (UTC)
 * Whoops, read it out of context. To me all I saw was "When entering a portal" which seemed incomplete and like you removed it by mistake. You can revert my revert. --Moxxy 01:27, 13 March 2012 (UTC)
 * Okay. --Lolmaster 01:28, 13 March 2012 (UTC)

Renewable Resource (XP Orbs)
I see what you mean about the note I added (you deemed it a non sequitur, I believe), but I feel like that information is relevant to the gameplay and should be mentioned somewhere. Rather than start an edit war, I'll ask: any ideas on where best to place it?

Oh, and I've noticed your frequent mentions in the history pages. Keep up the good work. -Marksmanship 02:08, 29 March 2012 (UTC)
 * Sorry for taking so long to respond. The reason I removed it is because the page pretty much deals with infinity, it either is or it isn't. Most of what you were talking about was how it extends the period of diamond tools in which case it's still non-renewable. The page isn't meant to talk about extending the use of non-renewable resources, just about what is infinite and what isn't. What you added is relevant to gameplay but is pretty well covered already in the enchanting pages. --Moxxy 06:27, 9 April 2012 (UTC)

Removing others' bug reports
Hi. In removing my bug report about animals randomly fleeing /towards/ the source of the thing that harmed them, I think you are starting to get just a bit too trigger-happy - a trend I have been noticing over the last couple of weeks. (As it says in the reporting guidelines, 'Please do not spontaneously delete an issue report or comment...') Even though I know you don't agree with me that it's a bug, I think it is, and as such I am entitled to draw it to Mojang's attention. Removing the report entirely rather than just downgrading it to an annoyance was definitely not on. Rather than get into an edit war, I'm asking you to put it back again, or reply here so I know you won't just remove it again if I do. 82.69.54.207 14:06, 6 April 2012 (UTC)


 * Pardon me for interrupting (watchlisted this page waiting for a reply to my own query), but I'm pretty sure the animals were deliberately coded to "flee" in a random direction, rather than explicitly away from the player. I personally think this makes them harder to hit than if they tried running away from me.  Thus, it's a case of individual opinion on whether or not this needs to be improved, making it hard to properly classify this as a bug rather than a note or trivia.  Marksmanship 17:34, 8 April 2012 (UTC)

Village Blueprints
Hey, could you delete the old village blueprints because we have a new one under projects. Minecraft Wiki:Projects/Village Blueprints

Unknown Blake 00:55, 19 April 2012 (UTC)

Mobs
Why did you undo my edit on the "mobs" page. (Just looking for an explanation) Officerpup 20:25, 11 April 2012 (UTC)
 * Sorry, forgot to put the edit description. It's vague whether he's actually adding pandas or if he's just experimenting/messing around. Devs do that stuff all the time like Jeb and his 50ft Spiders. There's even a video out there of all the weird stuff Skyrim developers made that weren't actually made to be put in the game. Hopefully he will be more clear next time it's brought up. --Moxxy 22:22, 11 April 2012 (UTC)
 * Sorry, I also undid some useful edits you made. I reverted back to your edit but without the panda comment. --Moxxy 22:27, 11 April 2012 (UTC)
 * Thanks for the clarification! Officerpup 15:15, 12 April 2012 (UTC)

Reddit
Do you have an account on Reddit? --Lolmaster 16:22, 15 April 2012 (UTC)
 * Nope --Moxxy 18:39, 15 April 2012 (UTC)
 * Hmm. Thought I saw an account with your name. --Lolmaster 18:45, 15 April 2012 (UTC)

Smelting
Why did you remove two of the four notes on smelting ores? —kpreid 22:58, 16 April 2012 (UTC)
 * Because unlike lapis and redstone they normally drop one so smelting isn't a bad idea. Yes you can get more with fortune but that isn't the norm and would require us to add a subnote to a subnote. I really wish I could go back and edit my revision notes, after I realized I didn't put any in I knew you would come here to ask me --Moxxy 23:03, 16 April 2012 (UTC)

No, Diamond ore sometimes drops more than one diamond, and I'm pretty sure Coal does too — they just don't always drop more than one, like Lapis and Redstone do. In both cases, a Fortune enchanted tool can also cause much higher drops — unless one is against using enchantments or has a chest full of diamonds already, smelting is just not a good idea. —kpreid 00:22, 17 April 2012 (UTC)


 * Without Fortune or mods, diamond and coal ore always drop exactly one item. -- Orthotope 01:45, 17 April 2012 (UTC)

Huh, OK. I yield to your expertise. I half expected you to have a table of the exact results... (I've thought that perhaps Drops be expanded to cover block drops.) I've re-added the notes but with appropriate phrasing to the actual situation. —kpreid 11:52, 17 April 2012 (UTC)


 * Fine, fine. ;) -- Orthotope 08:45, 18 April 2012 (UTC)

Ideas
Where do we post our ideas? I designed a item/block for minecraft but I don't know where to put it to get it confirmed. I may design some more too so telling me would be helpful for the rest of my ideas.

I currently have them under User:Unknown Blake/Ideas

Unknown Blake 01:13, 17 April 2012 (UTC)

Books having colored titles, more than 50 pages, etc.
I have created a section on the talk page of Book and Quill, but I'm also posting it here if you prefer to respond here:

A user has repeatedly been removing evidence that books can be edited to contain more than 50 pages, more than 256 characters and 13 lines per page, colored and formatted titles, custom player names (also with colors and formats), etc.

These are all properties which a book in vanilla Minecraft can have, but they require an editor such as NBTedit to be created. A vanilla Minecraft player may encounter books like this in adventure maps, or on multi-player servers, and they will work as my screenshots have shown. Moxxy has insisted, however, that this information should be excluded from the article, simply because a vanilla player cannot create the books, disregarding that they may still encounter them.

If this is a sort of standard the wiki community wishes to set, then fine. But please be consistent about it. The article on signs provides evidence that signs can have colored text, even though this requires mods/programs. The article on snow mentions that snow can actually have varying height, but that this does not occur in singleplayer Minecraft without mods or editing (I myself have encountered varying-height snow on servers in the past, and I was playing vanilla). The article on slabs shows a special doubleslab which requires mods/editing to insert into the world. The map article mentions the zoom level property of maps, which is unused in vanilla. Grass makes prominent the existence of a third grass type, which resembles dead shrubs but cannot be obtained without mods/editing (again, I have witnessed it playing vanilla on servers before). All pages of blocks mention the unused, unobtainable Locked Chest.

Now, do tell me, why is it that this information on books must be removed, when all that other information can stay? If you want this information removed, you ought to remove all of that information as well, to keep this wiki consistent.

Or, you could acknowledge that this information is relevant to vanilla players, because they could very well encounter it themselves and wonder what is going on. Then we'll have people re-adding information in a far less organized and informed manner than I have, with trivia sections such as "sometimes a book can have a colored title on some servers. it is not known why this is" or "some adventure map makers may get famous people, like notch, to write books for their maps". Honestly, I fail to see why that is preferable to what I have contributed. --WolfieMario 03:42, 27 April 2012 (UTC)

Do you have any comments on this? You say there is nothing more to say. Well, I have said it anyways, because I don't understand why you're so convinced that information must be removed, unless of course you also feel all the information I linked should be removed as well... In which case there will probably be more than just you and me involved in this discussion.

And before you say it, I know the doubleslab, grass, and locked chest can be obtained with the /give command in vanilla SMP (and now, with commands in singleplayer). I didn't think of that at first. But all the other things I mentioned cannot be obtained with vanilla server commands, so my point still stands in that regard.

Anyways, nobody said you couldn't reword my contributions to sound less referential to editors and hacking - I'm not objecting to that at all. On the complete removal of the information, however, I have voiced my opinions above. Sorry that I did not post here sooner; I had not thought to check your userpage and see that you are open to discussion on the things you have removed. --WolfieMario 04:11, 27 April 2012 (UTC)

Admin?
Hello I was just curious wether or not you were an adimn. if you aren't an admin you certainly deserve it.KingFlameTail 19:09, 16 May 2012 (UTC)
 * No I'm not an Admin. Thank you for the compliment though. I would like to be an Admin eventually but as of now there are certainly more deserving users than me to take the position. --Moxxy 19:10, 16 May 2012 (UTC)
 * Yeah you should be admin. You have been here in this wiki a long time, you have undid vandalism and whatnot and you have endless contributions. Quatroking, make Moxxy admin!--88.110.120.116 20:00, 13 June 2012 (UTC)

Ore image
"Like the caption says, it's a mock-up"

Meh, nevermind then, there's no point in adding it, but that wasn't even a good edit summary reason.- Asterick6 (talk) 19:43, 24 May 2012 (UTC)

Pyramid
It is not redundant. - zeel 00:31, 25 May 2012 (UTC)
 * It's kind of a silly point to make. The article already mentions it is valuable in the first sentence, we really don't need a reminder. --Moxxy 00:33, 25 May 2012 (UTC)

About At The Time statement
I put "(at the time)" to the... what's the word(s)? Future-active... Something. Basically, the statement wouldn't need to be corrected once he was married. I think it should stay, maybe be rewritten. MegaScience 19:28, 31 May 2012 (UTC)
 * Just change when they get married or break up. Right now it sounds like they aren't together or already married. Somebody will update it when they get married within the day. --Moxxy 21:03, 31 May 2012 (UTC)

Deletions
Look, instead of deleting an old, existing, non-stub article on a non-game item, just move it to the Tutorials section where they're meant to be, or redirect it to an existing topic. You don't know how to redirect or move a page? Just tagging delete notices everywhere you see a non-game topic without assessing the notability/scope of the content is quite unhelpful. - Asterick6 (talk) 23:47, 4 June 2012 (UTC)

And how is this not a bug report? You say it's not signed? "Confirming, this also happens when you make enclosed bunkbeds that are only open on the side (no air above them), with top bed having 2 blocks of air at the end of the bed (no air above it). Bottom bed seems to be fine, always exiting you next to the bed but the top bed seems to suffer from this occaisonaly. Reason seems to be that it exits you at the head of the bed instead of in the open space at the end of the bed sometimes, where as the lower bunk always exits you next to the bed. Note that this behaviour is erratic, it can work fine for days on end then all of a sudden you spawn at the head and die. --95.97.131.78 13:22, 5 June 2012 (UTC)"
 * Just stop editing if you're going to be disruptive. - Asterick6 (talk) 23:39, 5 June 2012 (UTC)


 * "Bug reports that do not provide enough useful information or contain too much opinionated or anecdotal waffle may be subject to removal ".
 * Piss off. I've been editing this wiki since it was created. --Moxxy 14:32, 6 June 2012 (UTC)
 * It's quite funny you've been editing since 2010 cause the first time I met you here, you were acting like a noob who didn't know the rules around here. Looks like you still don't. Pretty conceited aren't you? You want a ban this badly? It's been 2 years - still haven't had enough? Just leave. Your contributions aren't welcome anyways. - Asterick6 (talk) 01:40, 8 June 2012 (UTC)
 * Wow, way to be rude. The text expands on the reported bug (one block of air above it to no blocks of air above it, describes a situation where it doesnt occur and adds information on how to duplicate the bug. Therefor, even though long worded, it's a fine addition. --95.97.131.78 14:48, 6 June 2012 (UTC)

Xbox 360 Edition known bugs
Stop deleting reported bugs and comments in Xbox 360 Edition known bugs without discussing them on the talk page or without notifying the user that submitted them. If you feel something is not a bug you can say so in the comments as per reporting instructions on the page. Do not delete content. --95.97.131.78 13:16, 5 June 2012 (UTC)
 * They are completely unsigned comments so they are allowed to be removed. Saying "this is not a bug" not only doesn't help keep the page clean of things that don't belong, it fills it with even more text useless to Dinnerbone, Jeb_ etc... --Moxxy 14:34, 6 June 2012 (UTC)
 * Firstly they are all signed, those unsigned that I was able to reproduce myself I have signed. Secondly you are removing content flagged by 3J Studios as fixed. Thirdly read Xbox 360 Edition known bugs;
 * Quote: ''Please do not spontaneously delete a bug report unless it is blatant nonsense submitted by an unregistered user. Try to contact the submitter by user-talk first and tell them about your concerns. Almost all active submitters will be co-operative. Always assume good faith.


 * You may also leave a comment explaining why you feel the bug should be removed, allowing time for others to weigh in on the decision or for the original poster to give additional information. Where possible, removal of a bug should be a group decision, not a decision made by a single individual.'' --95.97.131.78 15:05, 6 June 2012 (UTC)
 * Reread those rules you just posted again. It contains the clause I used as the grounds for deleting them. --Moxxy 17:54, 6 June 2012 (UTC)
 * Which part of;
 * 1. do not spontaneously delete a bug report
 * 2. contact the submitter by user-talk first
 * 3. leave a comment
 * 4. removal of a bug should be a group decision
 * do you fail to understand? They are reproducable bugs (except for one), flagged as annoyances, do you even own the mcx360 version or do you simply like to pvp on the wiki? The reason you state for deletion is either; unsigned comments (which they are not) and those are not bugs (page moderation is very clear about how to handle issue you feel about that way), the other reason you used for deleting the bunk bed duplication instructions has been reversed by mulitple users now. Follow the guidelines and stop vandalizing. --Z Doc 14:02, 7 June 2012 (UTC)
 * No, they are not signed. The only one that is signed is the bunkbed comment which falls under the "anecdotal waffle" category as it adds nothing to the bug report. The comment reports the exact same thing except in an entire paragraph. --Moxxy 14:34, 7 June 2012 (UTC)
 * They are all signed. Comments need to be signed, which they are, bug reports are not allowed to be signed, which they aren't. The bunk bed comment has been placed back by multiple users now, with another user above this section complaining about you removing valid content, yet you choose to ignore that. You deem it "anecdotal waffle", me and others don't.


 * I've tried to be reasonable with you but as you continue to refuse notifying users, refuse to leave comments (history page is not a talk page), refuse to start a group discussion on the talk page of the article, insist on deleting bug reports, keep deleting issues flagged as fixed by 4J Studios, refuse to discuss or listen to discussions why something should be in or out you are starting to force this into a need of admin intervention, which is silly, unneeded and unwanted. Act mature please and take this discussion to the talk page of the article for a group decision. --Z Doc 15:41, 7 June 2012 (UTC)

Maps started before latest version are relevant
Minecraft maps are specifically made to work with new versions.

Bugs reports associated with maps generated before the latest version are still bugs, and do not qualify as nonsense or other unrelated things which need to be deleted. -Wickedshot
 * There's nothing that can be done. Outdated content cannot be reported. --Moxxy 04:20, 10 June 2012 (UTC)

There is something to be done, it was done before and it was fixed, and then a new change caused the bug to happen again. I don't know if you don't understand the problem or what, but issues having to do with maps generated in earlier versions can and have been fixed, and new ones need to be noted so they can also be fixed. -Wickedshot
 * I guess if it's been fixed before then we can keep it. We delete bugs from outdated maps as a rule of thumb to keep out the swarms of land generation and other things that are obviously going to break when things change. For example wooden planks are going to be burnable in the future but ones that were already placed won't be burned. You can expect there will be several reports of people saying "Wooden planks placed prior to 1.3 can't be burned but new ones can!!!!". I'll leave it alone now. Sorry for the trouble. --Moxxy 05:26, 10 June 2012 (UTC)


 * There has never been a guarantee of complete forward compatibility. Changing already-generated chunks is dangerous, and there's a good reason Mojang hasn't done it. Suppose someone built a base in the same place a stronghold would generate. Is it acceptable for the game to overwrite their work without warning? You might say 'only replace blocks that haven't been changed by a player', but how can you tell which ones those are? You'd have to compare the existing chunks with fresh ones made by the exact same version of the world generator. Given how many times it's been changed, that's a needle-in-a-haystack problem. Also, end portal frame blocks have been added to the creative mode inventory, so the End will be accessible in any world, no matter how old it is.


 * Can you tell us exactly what world-generator-change bugs have been fixed in the past? -- Orthotope 07:00, 10 June 2012 (UTC)


 * The exact problem I mentioned was fixed in the past, i.e. Leaf blocks from previous versions not decaying. At one point they ceased to decay, but then it was brought up, and Notch fixed it, and it wasn't an issue for a while, but more recently it became an issue again.  The bug tends to happen when changes are made to leaf blocks in general and these older leaves get lumped together with decorative instead of real leaf blocks, atleast that is my understanding.


 * About Strongholds, that's actually another issue I have, but that's less a bug, more an annoyance (a HUGE annoyance heh) and lack of a feature.  My best suggestion for solving that would be infinite strongholds (thought we were supposed to get infinite strongholds in 1.9) or generating the strongholds in the first ungenerated lands it can find, because like you say, you wouldn't want it generating over top of existing terrain.-Wickedshot


 * Leaves might be fixable, we'll see what Mojang says. Alpha 1.2 broke leaf decay entirely, not just for leaves from previous versions; it was re-implemented in Beta 1.0 . Re-setting the 'check for decay' bit for all leaves might work, but the only reasonable time to do that in-game is when converting an old world. Perhaps it's a job for a third-party program. -- Orthotope 23:48, 10 June 2012 (UTC)

Edit comments
"This page is basically 90% bugs"

Really? Your edit comments don't help much if you're going to exaggerate all the time. - Asterick6 (talk) 05:16, 11 June 2012 (UTC)


 * It's Hyperbole, give me a break! --Moxxy 19:15, 11 June 2012 (UTC)

Dye
Gray is spelled Grey! Minecraft5025 21:15, 27 June 2012 (UTC)
 * Both are correct. If it was wrong wouldn't someone else have noticed by now :P --Moxxy 21:16, 27 June 2012 (UTC)

Just stick to one spelling and stop moving pages until this situation is resolved. English (US) says "gray", and I'm assuming that English (UK) (if it exists) says "grey". Rainbowfridge42 21:21, 27 June 2012 (UTC)
 * This wiki uses English (US) for consistency. --Moxxy 21:27, 27 June 2012 (UTC)
 * Adding on to what I said before, I'd suggest that we stick with Gray, seeing as English (US) is the default language (at least for me), and have all "grey" articles redirect to "gray". Then, within the articles themselves, a note could be added, e.g. "Gray/grey dye is", etc. etc. etc. Rainbowfridge42 21:30, 27 June 2012 (UTC)
 * We use US English, not UK English as a rule, however, this is an item in game, so the name should be spelled as it is in the game. -- Wynthyst [[Image:User Wynthyst sig icon.png ]] talk  21:56, 27 June 2012 (UTC)
 * Thing is, in-game has English (US) and English (UK) as two language choices; US says gray, UK says grey. Rainbowfridge42 22:04, 27 June 2012 (UTC)
 * That's a relatively new feature. The original game only had US English. Also this site is American run. --Moxxy 22:05, 27 June 2012 (UTC)
 * I guess we're sticking with US (gray) then. It seems like the most reasonable idea. Rainbowfridge42 22:08, 27 June 2012 (UTC)

Please write some words in your commit messages
Can you please put some addional word(s) besides the default section name in the commit message, e.g. "Remove issue", that helps to see through in the clobbered history of the Known Bugs page. Thanks. --Kumasasa 19:40, 28 June 2012 (UTC)
 * Sorry, I forgot to say that I was doing clean-up in my first edit. I'm just removing duplicates, nonsense, reported for removal and fixing spelling. I work one section at a time to avoid getting conflicting edits. --Moxxy 19:42, 28 June 2012 (UTC)
 * Yes, I do that the same way. A simple "cleanup" as commit message helps already ;-) --Kumasasa 19:46, 28 June 2012 (UTC)

WTF
I fixed it and you revert. What??????
 * Nope, we both reverted the same edit at the exact same moment. It should go back to normal in a few minutes if you leave it alone. Images take time to change when you revert and if you keep trying to fix them it will keep looking incorrect. I was actually just going to make a comment on how funny it was how we both noticed your mistake at the exact same time. --Moxxy 06:08, 10 August 2012 (UTC)