User talk:BDJP007301

Patroller right
Hi! Dinoguy1000 has put you in the patroller user group, which allows you to mark other edits as patrolled and rollback edits. Please take a look at MCW:Patrollers for an explanation of the role, as well as a quick guide. Here's a brief overview of both of the main permissions:
 * Marking edits as patrolled. This basically tells other patrollers and administrators that the edit has been reviewed and any problems both content-wise and formatting-wise, have been fixed - e.g., open HTML tags or incorrect information. Since you're a new patroller, if you're unsure about something, it's better to leave it to a more experienced patroller or administrator. Additionally, you can take a look at Special:log/patrol, to get an idea of when other patrollers mark edits as patrolled.
 * Rolling back edits. Clicking "rollback" will instantly rollback all of the last contributions to the page by the user without leaving an edit summary, while clicking the pencil button will allow the summary to be edited. The most important thing here, is if there's any chance that the user was trying to be helpful to the wiki or the information might be correct but you haven't tested it, make sure to leave an explanatory edit summary.

If you have any questions, don't hesitate to let me know! Additionally, if you don't want this user right, feel free to ask for it to be removed here, and I can ping Dinoguy.-- Madminecrafter12 Orange Glazed Terracotta.png to meLight Blue Glazed Terracotta.png 13:14, 2 August 2018 (UTC)

Stop reverting my edits
Can you please stop reverting my edits to PlayStation 3 Edition, PlayStation Vita Edition, Xbox 360 Edition, Wii U Edition and Legacy Console Edition version history? They will continue to receive bugfix/non-feature updates, such as the one that came yesterday for PS3 Edition. --Giorgosarv18 (talk/contribs) 12:21, 21 September 2018 (UTC)
 * See Talk:PlayStation_3_Edition. -BDJP (t 13:51, 21 September 2018 (UTC)

Rollbacking edits
Hi BDJP, and thank you very much for your vandalism fighting - your work here is greatly appreciated! I just wanted to remind you that unless an edit is clear vandalism, you should always leave an edit summary when reverting. Vandalism has a very specific meaning - the act of deliberately trying to destruct the wiki. Many times, an edit will seem like vandalism but it's really not. Not all unconstructive edits are vandalism. Test edits, inserting opinions, and not following the style guide are all examples of edits that might seem obviously unconstructive to you, but are often in fact an honest effort that just is bad style. In these cases, it's better to assume good faith and leave a civil, clear, and explanatory edit summary. Rollbacking good-faith edits without leaving an edit summary is harmful, as it can be confusing and discouraging for new editors.

A few recent examples where you probably should have explained your revert reasoning include this, this this, this, this, this, and this. For comparison: this, this, and this are great examples of where it's perfectly appropriate to rollback without any kind of edit summary, because these edits are clear, obvious, deliberate vandalism. Please don't take this as a warning or anything, but rather as some friendly advice that you might want to keep in mind while you continue your wonderful efforts to improve the Minecraft Wiki. :)-- Madminecrafter12 Orange Glazed Terracotta.png to meLight Blue Glazed Terracotta.png 01:22, 15 October 2018 (UTC


 * Thanks. I’ll do my best to improve. :) -BDJP (t 02:16, 15 October 2018 (UTC)


 * Thank you for your willingness to help the wiki and improve your editing; it's much appreciated. Again, your vandalism-fighting efforts are great; keep up the good work, but preferably with the things pointed out in mind. One more thing, though; when marking redirects for deletion, it's generally good practice to put delete below the redirect rather than replacing the redirect with the template. This way, admins don't have to dig into the history in order to view what the page redirected to, and readers searching for that title will be taken directly to the target page without having to view a random big red box, until an admin considers whether the redirect should be deleted or not. You can see a discussion related to this at MCT:PORTAL which you are more than welcome to comment on (even though it is a bit old). Happy editing!-- Madminecrafter12 Orange Glazed Terracotta.png to meLight Blue Glazed Terracotta.png 02:45, 15 October 2018 (UTC)

Programmer Art texture pack
Thanks for finding that source. I really did do a search for it and only found one reference, to 1.5.2 where it had something to do with changing the paintings, I think. And it's odd that just 10 hours ago Jappa said (Sorry for the partial post. Hit a wrong key I guess.) – Auldrick (talk &middot; contribs) 02:25, 4 November 2018 (UTC)


 * Your welcome. -BDJP (t 09:29, 4 November 2018 (UTC)

Private issue description rule
Good day. With regard to this edit you made, it isn't immediately clear which rule is referenced, and the style guide subpage on version articles doesn't seem to specify such an exception to listing bug titles. Could you please link to a rule restricting private issue titles, or a discussion resulting in such a restriction? --AttemptToCallNil (report bug, view backtrace) 14:19, 23 November 2018 (UTC)


 * This edit by Dinoguy1000. -BDJP (t 14:38, 23 November 2018 (UTC)


 * Perhaps this should be formalized; MCW:Style guide/Versions should be the best place for this guideline. —  BabylonAS (talk | ru.Wiki Admin) 14:45, 23 November 2018 (UTC)


 * Strictly speaking, yes, we should list that in actual rules/guidelines pages (if we decide that's how we act). A single edit isn't a rule. It's more like a precedent. --AttemptToCallNil (report bug, view backtrace) 14:48, 23 November 2018 (UTC)

Needs consensus
How many people need to agree with a proposed edit in order to count as a consensus? an_awsome_person (talk) 03:44, 2 January 2019 (UTC)

Special:Diff/1309433
How can such a basic background be copyrighted? I don't understand, and it seems I'm not the only one. --AttemptToCallNil (report bug, view backtrace) 16:03, 24 January 2019 (UTC)


 * All it is is just cropped from the website shown in this video. -BDJP (t 16:55, 24 January 2019 (UTC)


 * Still, do the cropped screenshots contain Mojang-copyrighted assets? The skins are likely to have separate copyrights. --AttemptToCallNil (report bug, view backtrace) 17:22, 24 January 2019 (UTC)


 * Yes. The blue background. -BDJP (t 17:35, 24 January 2019 (UTC)


 * I strongly doubt single RGB colors are copyrightable, they are unlikely to meet the threshold of originality. --AttemptToCallNil (report bug, view backtrace) 17:42, 24 January 2019 (UTC)


 * I am pretty certain that a plain color is not copyrighted. If it were a complex pattern, maybe, but this is a completely uniform shade of blue. Nobody owns a color.-- Madminecrafter12 Orange Glazed Terracotta.png to meLight Blue Glazed Terracotta.png 18:17, 24 January 2019 (UTC)


 * Just because the background is a certain shade of blue does not mean it's automatically copyrighted by Mojang. For instance, this paragraph is obviously not copyrighted by Mojang even though it uses "its colour". The skin would be copyrighted by its owner so a plain fair use copyright template should be applied. – Nixinova Nixinova sig image 1.png Nixinova sig image 2.png 18:22, 24 January 2019 (UTC)


 * How exactly are plain colors copyrighted at all?-- Madminecrafter12 Orange Glazed Terracotta.png to meLight Blue Glazed Terracotta.png 18:25, 24 January 2019 (UTC)


 * The colours aren't copyrighted but they can be trademarked if the colour is associated very much with the brand. #a0b3de has not been trademarked by Mojang as its not automatic so it definitely has no ownership by Mojang. Even if #a0b3de was trademarked by Mojang they would still not be able to actually do anything against whoever uses "their colour" (using BDJP's argument) as its just a colour. – Nixinova Nixinova sig image 1.png Nixinova sig image 2.png 18:28, 24 January 2019 (UTC)


 * Apologies, but I'm not clear on what you're trying to say. I agree that they have not been trademarked by Mojang, it is just a standard RGB color, so why would we need a fair use rational and tag it as copyrighted?-- Madminecrafter12 Orange Glazed Terracotta.png to meLight Blue Glazed Terracotta.png 18:32, 24 January 2019 (UTC)


 * We need a fair use tag because the skin is copyrighted. --AttemptToCallNil (report bug, view backtrace) 18:34, 24 January 2019 (UTC)
 * tl;dr colors can't be copyrighted but can be trademarked if they're largely associated with one company. I would think the skin itself is probably copyrighted but I'm not completely sure. It's better than a Mojang rationale anyway. – Nixinova Nixinova sig image 1.png Nixinova sig image 2.png 18:35, 24 January 2019 (UTC)


 * We'll need to do that to other files BDJP batch-edited today then. --AttemptToCallNil (report bug, view backtrace) 18:36, 24 January 2019 (UTC)


 * Oh, you're talking about the skin, that makes a lot more sense then. Thanks for the explanation and apologies for not realizing that. In that case, because the skin was created by the image's author, they get to decide the license. However, because they've been inactive for 8 years, it's very unlikely that we would be able to contact them about it, so yeah, a fair use/copyright license would probably be the best idea.-- Madminecrafter12 Orange Glazed Terracotta.png to meLight Blue Glazed Terracotta.png 18:37, 24 January 2019 (UTC)