Hello there! We are conducting a survey to better understand the user experience in making a first edit. If you have ever made an edit on Gamepedia, please fill out the survey. Thank you!

Talk:Commands

From Minecraft Wiki
Jump to: navigation, search
Talk Archive

Tellraw command not working.[edit]

Please Update The Json Provided. The Command is Not Working Properly Thank You--112.198.75.145 03:35, 21 February 2016 (UTC). --112.198.75.145 03:35, 21 February 2016 (UTC)

Fixed. Skylinerw (talk) 03:44, 21 February 2016 (UTC)

operator level[edit]

A recent edit to the page was made, where different operator levels were noted for each command in the commands summary table. I couldn't find anything on the wiki about operator levels. If this is a thing, maybe it should be on this page, and on the Operator page. – Sealbudsman talk/contr 19:59, 3 April 2016 (UTC)

Apparently it is used on servers to allow some operators to have more permissions, see User talk:Cat7373#Op Level?. KnightMiner t/c 22:56, 3 April 2016 (UTC)

Behavior of /particle with colorable particles[edit]

The usage of /particle suggests that the xd, yd and zd parameters when applied to a colorable particle (eg reddust) and a count of 0 specify an RGB color offset from the default color. The problem here is that it is not offset, but rather uses specific cases. The game applies the default value to each color channel only if the entered value is exactly zero. This means that even at 0.0000001 on xd, the reddust particle is black. This of course makes no visible difference to the other currently applicable particles (mobSpell and mobSpellAmbient) as their default values are all zero anyway. Not sure how to incorporate this info into the existing paragraph. –Preceding unsigned comment was added by Techy4198 (talkcontribs) at 19:14, 20 July 2016 (UTC). Please sign your posts with ~~~~

Did some testing and made it more correct, hopefully clearly enough. Thanks, good catch! – Sealbudsman talk/contr 03:50, 22 July 2016 (UTC)

Commands in single player mode?[edit]

Hi i have tried th give command in my singleplayer world now, only trouble is, that it responds by saing that it cannot find a player by that name, even thoug I am typing in my own username? What am I doing wrong?

What command? PC or PE? – Sealbudsman talk/contr 11:43, 30 August 2016 (UTC)
Try using the right capitals/lowercase in your name, see if that works. – Sealbudsman talk/contr 11:47, 30 August 2016 (UTC)
Also try typing just the first letter of your name and then TAB. Or just use @p. —munin · Grid Book and Quill.png Grid Stone Pickaxe.png · 16:14, 30 August 2016 (UTC)

PE 0.16.0 commands[edit]

There are three commands in 0.16.0 that aren't in PC: /clearfixedinv, /setfixedinvslot and /wsserver. Do we know what these do? – Sealbudsman talk/contr 16:42, 30 August 2016 (UTC)

The /setfixedinvslot command is in Education Edition, described here, though doesn't necessarily mean it's the same implementation. Unfortunately that's all I myself can offer as I don't have PE. Skylinerw (talk) 17:03, 30 August 2016 (UTC)
Sorry for replying so late, but wsserver stands for web socket server and is used to connect to a server via web sockets to receive automated command messages. Basically it's a way for the devs to send commands to a client to test stuff remotely rather than having to do it manually. There is another command, /closewebsocket, that's used solely by the automation server to terminate sending/receiving messages via web socket. Jocopa3 (talk) 02:44, 28 October 2016 (UTC)
Nice; I've included that info on the page, since it's still a current command that shows up, might as well explain what it does, even if it is developer only. – Sealbudsman talk/contr 03:57, 28 October 2016 (UTC)

Need some help[edit]

How /title works? Is hard--72.50.82.222 22:59, 1 December 2016 (UTC)

It really  Doesn't work--72.50.82.222 23:09, 1 December 2016 (UTC)

... grammar exists... Boorider7 (talk) 23:57, 21 December 2016 (UTC)

New PE command: /connect[edit]

Pocket Edition 1.0.0 added a /connect <serverURI: string> command. Unfortunately, I know nothing about playing on a server and I'm not on Reddit (yet?), so that's all I know about it. Would somebody else be willing to write it up? — Auldrick (talk) 04:03, 14 January 2017 (UTC)

I added it as an alias to the /wsserver command, because they have the same syntax. In retrospect, I should have verified that with Jocopa3 first. It was a complete guess. – Sealbudsman talk/contr 04:11, 14 January 2017 (UTC)

/function[edit]

Needs /function command (added in 1.12-pre1).  Nixinova T  C  • 04:32, 11 May 2017 (UTC)

I see you redirected the "function" page to here because of this /function command. Do you also think the whole function system should be listed here (I'm assuming not)? If not, I don't think the "function" page should redirect to here. --Pepijn (talk) 16:50, 11 May 2017 (UTC)
Especially since the only remotely relevant information in this article contains a link back to Function, which brings them right back here. In situations like this you should create the Function article, or at least a stub, or you could just let the link in this page be a redlink until somebody else creates the article. I will check into having the redirect page deleted. – Auldrick (talk · contribs) 19:29, 11 May 2017 (UTC)
Can't we just edit the existing page and remove the redirect? --Pepijn (talk) 21:04, 11 May 2017 (UTC)
What would be the point of that? It would just show the user a completely blank page (which I don't think is even allowed by the Wiki software, let alone the Wiki rules). No, it's perfectly fine to let your link be a redlink; it's a normal and expected thing in a hypertext document where so many pages link to so many others. – Auldrick (talk · contribs) 21:09, 11 May 2017 (UTC)

Commands#Data_tags needs update.[edit]

as it was changed in 1.12. The Byte Array type is not unavailable to commands anymore... 58.128.2.108 11:12, 23 May 2017 (UTC)

You can specify the type of a list by including a prefix. For example, [I;16777215] specifies a TAG_Int_Array, whereas [16777215] specifies a TAG_List, which often doesn't work as a substitute. Similarly, B or L prefixes can be used for TAG_Byte_Array and TAG_Long_Array.
- Andrio Celos (talk) 15:31, 13 August 2017 (UTC)

Long Page[edit]

I think the list of commands should be converted to {{LoadPage}}s because the page is long. Dentedharp90041tc 13:00, 8 July 2017 (UTC)

 Support And move all commands to Commands/kill, Commands/give, etc, and then have {{LoadPage|(Commands)/kill}}, etc. Nixinova Grid Book and Quill.png Grid Diamond Pickaxe.png Grid Map.png 19:13, 8 July 2017 (UTC)
I agree that the page is rather long, but how would we deal with links, such as from {{cmd}}? An empty section header with another link to click for the actual content is not very user-friendly, but making links go directly to the subpages loses context. -- Orthotopetalk 19:25, 8 July 2017 (UTC)
Can't we just change the {{cmd}} template to link to commands/give instead of commands#give? Nixinova Grid Book and Quill.png Grid Diamond Pickaxe.png Grid Map.png 20:38, 8 July 2017 (UTC)
We could change load page to automatically show when its section is targeted, so hash links would still show the content, albeit with a slight delay. Potentially less of a delay than loading the entire page though, so it might be a net win. MajrTalk
Contribs
02:33, 9 July 2017 (UTC)
I replaced all the cross-platform commands with {{LoadPage}}. -134,000 bytes. Should load way faster. Nixinova Grid Book and Quill.png Grid Diamond Pickaxe.png Grid Map.png 02:35, 9 July 2017 (UTC)
Not really. About half a second difference on my desktop on an uncached page, not including generation time, which is only relevant to editors. The real difference will be on slow devices without much RAM (which I can't measure). MajrTalk
Contribs
02:44, 9 July 2017 (UTC)
Well, even if it doesnt load faster, it is still wayyyyyy for user-friendly, and when I can be bothered to do the Education Edition, scrolling down the page will be a lot less annoying. -Nixinova Grid Book and Quill.png Grid Diamond Pickaxe.png Grid Map.png 02:50, 9 July 2017 (UTC)
I disagree. Viewing more than one command, and especially comparing them is quite a bit more difficult. They might as well be entirely separate pages. The whole page acts as a pseudo TOC now, whereas before you could just scroll around to view nearby commands. The only real issue before was having to scroll back to the top to get to the TOC if you wanted to find another command, which would've been better solved by making the TOC always visible. Another potentially better option for reducing the page length would've been to split up the "List of commands" section to its own page, reducing both page sizes, while keeping the commands together.
I also don't agree with you making such a major change without anyone actually agreeing to it, other than the topic creator themselves. MajrTalk
Contribs
11:45, 22 July 2017 (UTC)
I don't like the LoadPage approach as well, but having all the commands on the same page is not a good approach either I think. The German wiki for example only has general usage on the Commands page, and all the commands split up to own articles, with an own navbox. The advantage is that you can go into detail even more while not having to care about the page becoming too long. | violine1101(Talk) 12:00, 22 July 2017 (UTC)
I agree with the TOC to have a fixed position. For the LoadPage, I kinda agree with that, but is there any way to make the LoadPage uncollapsed? It seems like the discussion was about the page size, not the long page scrolling. I also thought of separating the List of commands, Education Edition, and Removed commands sections onto their own subpages, not the every single commands. – ItsPlantseed|⟩ 13:04, 22 July 2017 (UTC)


The page wasn't very big though, it's 49KB now, and was 97KB before, which is nothing really. Text compresses really well. MajrTalk
Contribs
00:07, 23 July 2017 (UTC)
Now, It's very hard to update "Commands" page on Chinese Minecraft Wiki for Chinese Minecraft Wiki users. So many sub-pages to open.SteveZihang zh.Patroller Book and Quill.png 03:57, 31 August 2017 (UTC)
I think it is a really bad idea to use LoadPage on this page. It is not friendly to other-language Minecraft Wikis at all.SteveZihang zh.Patroller Book and Quill.png 04:03, 31 August 2017 (UTC)

This LoadPage format has completely sapped my interest in watching and maintaining this page. Is that a valid criticism?

The page was long and something needed to be done so I gave it a chance, but I don't like it.

I suggest that the article be broken into three pages: "Commands" (no command descriptions, but everything else), "List of commands" (non-EE command descriptions), and "List of EE commands" (EE command descriptions). —munin · Grid Book and Quill.png Grid Stone Pickaxe.png · 13:25, 29 September 2017 (UTC)

Education Edition[edit]

If in Education Edition there are commands, then should be {{exclusive|java|pocket|education}} ? (sfme) — RDmitriyS (talk) 13:25, 8 July 2017 (UTC)

I was late for a minute... — RDmitriyS (talk) 13:34, 8 July 2017 (UTC)
Alright, but that was a good question, since Education Edition always equals to Pocket Edition, shouldn't we add {{{education}}} to all the exclusive page for PE? For instance Nether Reactor, this page is exclusive to PE but also available on EDU since it has the same codebase. – ItsPlantseed|⟩ 13:45, 8 July 2017 (UTC)
 Support Dentedharp90041tc 02:46, 9 July 2017 (UTC)

Command Radius[edit]

Does the radius target selector argument use euclidean distance or taxicab distance? --MCweb 19:11, 7 August 2017 (UTC)

Command Syntax[edit]

An official post by Dinnerbone was made awhile ago regarding some major changes in 1.13 (upcoming): https://www.reddit.com/user/Dinnerbone/comments/6l6e3d/a_completely_incomplete_super_early_preview_of/ In this post, a certain syntax is used for commands (literals, arguments, optional, required, etc). Which is different from what this wiki is currently using. Normally I wouldn't think of this as a big issue, but one of the additions in 1.13 is an ingame command UI display the syntax of commands, which is gonna use DB's syntax. To be consistent with the game, I think we should switch to this new syntax. I'm only not certain WHEN to do this: Now? The first snapshot including it? Or only when 1.13 if officially out? I personally vote for now since I don't see a reason for DB to change this syntax anymore. --Pepijn (talk) 20:34, 11 August 2017 (UTC)

To be consistent with the game, I think the command syntax on this wiki should be updated to the new form. I think that we should be working on a fast method (like a bot) to update all of the command formats that aren't being messed with as of now, but aim to have all the commands changed at 1.13 release. Due to the nature of the update command syntax could change at any time during the snapshot cycle, so updating the syntax of every command on a page other than 1.13 might be a waste until the update is officially released. -- OSX (talk) 20:43, 11 August 2017 (UTC)
I second this --FVbico (talk) 22:40, 11 August 2017 (UTC+1:00)
Based on the style guide, the information may not be included until it is at least in a snapshot, and should not replace the old information until its fully released. Typically with large changes like this (Trading is an example), once a snapshot is released I created a subpage with the new information, and once its released I move much of the old information to a subpage, to prevent from overly cluttering the history. Check out that article for an example. KnightMiner t/c 03:04, 12 August 2017 (UTC)
Update Aquatic has now released and the command syntax has radically changed. This is a major change: most of the old syntax currently on the page does not work in 1.13 anymore. The information on the page should now be changed now that 1.13 has been released. -BillusThecat (talk) 12:38, 27 July 2018 (UTC)

About /tickingarea[edit]

I am an anonymous user from Chinese Minecraft Wiki.

Could you please add the descripsion of /tickingarea123.15.129.9 04:52, 19 August 2017 (UTC)

Why not getitemdata command page?[edit]

–Preceding unsigned comment was added by 180.190.51.135 (talk) at 06:22, 6 September 2017‎ (UTC). Please sign your posts with ~~~~

Each command does not have enough information to have its own page, so we combine them into one page about commands in general. The BlobsPaper.png 03:55, 7 September 2017 (UTC)

I think clickEvent suggest_command doesn't apply to written books[edit]

I'm currently experimenting with written books; making one which will give players easier access to certain specific server commands. In the RAW JSON section I came across suggest_command which is said to be the same as run_command with the difference that it inserts the text into the persons chat without running it. However, this doesn't seem to apply for a written_book. Could someone verify this before I insert a small disclaimer? ShelLuser (talk) 15:09, 1 January 2018 (UTC)

This is indeed correct. insertion, open_file (not available at all, it's only used internally) and suggest_command are unavailable for books. --Pepijn (talk) 15:47, 1 January 2018 (UTC)
Thanks for the fast reaction! This is one of those wiki pages where I'm really careful and wanted to be absolutely sure before editing. ShelLuser (talk) 17:01, 1 January 2018 (UTC)

Education Edition commands and Removed commands under List of commands?[edit]

I believe they should be, because Education Edition commands can be stated as List of Education Edition commands and Removed commands can be stated as List of removed commands. – ITechieGamertce 09:17, 1 February 2018 (UTC)

Regarding my edits being reverted[edit]

@PepijnMC and Skylinerw: I added an {{{extra}}} parameter into the {{LoadPage}} template, so that the {{only}} templates would appear below the heading, without being brought down when showing the {{LoadPage}} contents. I even removed the <strong> tag from the {{LoadPage}} because I thought that it was the reason why my edits are being reverted. I wanna know why my edits are being reverted. – ITechieGamertce 12:57, 6 February 2018 (UTC)

Your revert of my corrections also deleted a bunch of extra templates you completely forgot to add in previously (and my corrections on all your upcoming templates), please look at what you revert next time. An example is /data, it's only for Java and it's an upcoming command. You only specified it as upcoming. I have no problem with them being integrated in the LoadPage template, IF it is done correctly. You could have simply moved them into the {{{extra}}} parameter instead of reverting. --Pepijn (talk) 13:24, 6 February 2018 (UTC)
He's talking about this edit being reverted here and here respectively, I believe. – Jack McKalling [ Grid Book and Quill.png Grid Diamond Pickaxe.png ] 13:13, 6 February 2018 (UTC)

dx, dy, & dz[edit]

How will dx, dy, & dz behave if they're non-integers or if the x, y, or z target selector arguments are non-integers?

--MCweb 03:41, 20 February 2018 (UTC)

I don't know if it is supported in Bedrock very well / at all as of yet, but on Java Edition it uses those values more strictly.
This causes x=0.75,dx=0.5 to match X between 0.75 and 1.25, covering an equal 1/4th of where blocks at x=0 and x=1 touch. CtrlAltCuteness (talk) 16:42, 30 September 2018 (UTC)

Command block selection corner[edit]

A few areas on the wiki mention that the command blocks select from the "lower northwest corner". Doing singleplayer and server testing on 1.13.1 with the command tell @p[dx=0,dy=0.5,dz=0] x (and tell @p[dx=0,dy=1,dz=0] x from further away) and standing on top of the command block - the command is only ran when you are near the *Upper South-East* corner. According to the page, this should select a player at the same x and z as the command block's northwestern corner.

Here is an image showing the commandblock and the areas that are selected as glass: Glass on Southeast. Am I missing something here? -- 72.214.181.74 12:32, 16 September 2018 (UTC)

Face the absolute direction where, if you move forward, you go towards positive infinity on Z. Now +Z is in front, +Y is above, +X is to your left (←).
You want your first corner to be on the -X, -Y and -Z end (read: closer to negative infinity). Second corner should be towards +X, +Y and +Z (read: closer to positive infinity).
Now that you have your corners, the first X Y Z becomes your X Y Z pair while the second becomes dx=(second X - first X) and same idea for dy and dz.CtrlAltCuteness (talk) 16:35, 30 September 2018 (UTC)

Hey, uh, quick question about /forceload that wasn't very clear in the article....[edit]

So, uh, yeah, haven't been here in a while, but, uh, kinda need some urgent help involving /forceload. So, um, could I use /forceload to generate a Zoom-Level 4 map in game from a distance if I create the map in a chunk within the desired area? Also, can I use it to load more than one chunk at at time with only one command needing to be used? That would be really helpful, as I kinda need this info by, uh, tomorrow.... So, yeah, any help, or should I look somewhere else? Also, how exactly would I go about entering said command into a command block? Rockatoa, Brickticks out! Brickticks (talk) 22:19, 23 October 2018 (UTC)

Forceload is just used to keep chunks loaded server side and only one chunk can be parsed per command. – Nixinova Grid Book and Quill.png Grid Diamond Pickaxe.png 23:10, 23 October 2018 (UTC)
Thanks, that helps me in absolutly no way, shape, or form... Sigh, any other advice for getting all the Zoom-Level 4 maps I need done completed quickly? Brickticks (talk) 23:27, 23 October 2018 (UTC)
You can use /spreadplayers in a repeat command bloxk to randomly teleport yourself around the map to try and fill it all up. – Nixinova Grid Book and Quill.png Grid Diamond Pickaxe.png 23:38, 23 October 2018 (UTC)
Thanks, but I kinda need something a little more controlled than that.... Any advice? Brickticks (talk) 00:50, 24 October 2018 (UTC)
You'd probably have more luck on the Minecraft Discord, or maybe Reddit. This isn't really a technical support site: Only a very few people are probably monitoring this page, and most probably only check it once a day or so. (Incidentally, I can't help you because I don't know enough about Java Edition; I use Bedrock.) – Auldrick (talk · contribs) 04:26, 24 October 2018 (UTC)

Time argument[edit]

There is a new time argument for some commands, I think /weather and /schedule are some of them. It definitely does not apply to all, judging by this suggestion. Also I don't know what arguments are possible, there's definitely "t" for "ticks", "s" for "seconds" and "d" for in-game days, but I don't know if there are any other. I also can't find the blog post again, because I don't know which snapshot it was. Can someone please figure out how this works and document it in an appropriate place in the wiki? Fabian42 (talk) 09:16, 1 February 2019 (UTC)

Yes, there is a time argument now (parser minecraft:time). It's used by /schedule, /time set, and /time add. /weather does not use it. It was added with /schedule, in 18w43a. I checked this using the commands report data generator. The actual serializer supports "d" for days, "s" for seconds, "t" for ticks, and blank for ticks as well. --Pokechu22 (talk) 17:37, 1 February 2019 (UTC)

Suggest renaming: target selector → entity selector[edit]

The targt selector only selects entities. I think "entity selector" is more clear and accurate. --SolidBlock (not good at English!) 04:41, 14 February 2019 (UTC)

Is there any instance where mojang calls it something other than just "selector"? If so, it should follow that naming. FVbico (talk) 12:15, 20 February 2019 (UTC)
 Oppose In Bedrock Edition, target is used in many of the parameter descriptions. Java Edition also uses target for a few commands such as Commands/kill and Commands/tag. Admittedly, Java Edition does use <entity> for some however. –Preceding unsigned comment was added by Jahunsbe (talkcontribs) at 00:41, 8 April 2019 (UTC). Please sign your posts with ~~~~
Note that various command arguments do have different parser IDs, with the one that accepts entities being minecraft:entity. (This can be controlled to allow only one or allow multiple entities, and also to restrict it to only players). Of course, that's the name for the whole argument type, and not selectors themselves (which I don't think have an actual ID). I myself am  Weakly opposed to this rename. --Pokechu22 (talk) 00:49, 8 April 2019 (UTC)

"Education Edition only" commands missing[edit]

I can't find a navigation for edu commands. And the link in Education Edition exclusive features is redirected to Commands#Education Edition, which is a removed section.-- Ff98sha (talk) 13:01, 15 February 2019 (UTC)

Edit that removed links to removed commands[edit]

IMO this edit is a massive mistake. Yes, MCW:UPTODATE says that you shouldn't include old information in the main article, but this is an article that lists commands. It's useful to be able to search it and find a command, even if that command no longer currently exists (note that Block also lists removed blocks). Saying that those articles should be deleted is an even larger mistake; they're interesting historic information.

I think it's important to remember WP:IAR (and WP:IARMEANS and WP:UIAR). Sure, we're not wikipedia. But the point stands: removing that information makes the article less useful, so it's best to just ignore that part of the style guide here. --Pokechu22 (talk) 15:57, 7 April 2019 (UTC)

The style guide already has a convention to solve this: "Anything that is outdated should be moved to the History section of the article." I think the best move would be to make a small table in the history section of outdated commands, including the version they were last seen in each of the editions. Stops the articles from being unlinked and stops the commands from appearing as still in the game. –KnightMiner t/c 21:18, 7 April 2019 (UTC)
That would work (and is better than the current state), but I still thing it's a bit awkward to not distinguish between "never existed" and "removed" in the main table. --Pokechu22 (talk) 21:24, 7 April 2019 (UTC)
Or, you could just move the obsolete commands to Java Edition removed features, which is what that page is for in the first place, and move the command subpages to it. – Auldrick (talk · contribs) 17:37, 8 April 2019 (UTC)
That just sounds gross to me, and it would also break (or require a gross special case within) the {{command}} template. --Pokechu22 (talk) 18:38, 8 April 2019 (UTC)
... and that would also cause massive issues with the commands that were removed from the game for a better alternative, but still exist in other editions. Basically, following that guideline here leads to massive problems that are solved by simply ignoring it here. --Pokechu22 (talk) 18:46, 8 April 2019 (UTC)
I think the only thing "gross" here is your exaggeration of the value of information that nobody needs or has any use for, beyond satisfying idle curiosity. The {{command}} template is just a tool. We don't judge the worth of information based on how well our tools support it, that's preposterous! Besides, the only reason I suggested keeping the subpages at all was as a concession to your (and perhaps others') wish to keep them. Frankly, summarizing them in the Removed Features article and deleting them seems more appropriate to me. If that's a "massive mistake", please explain to me how it's "useful to be able to search it and find a command [that no longer] exists", and why "interesting historic information" justifies ignoring a long-established and previously uncontroversial guideline to "keep articles concise and up to date". If useless commands are an exception, then what in the world isn't one? It seems to me that this kind of obsolete information is precisely what the guideline targets. If you don't agree with its advice, you should be challenging the guideline, not an edit that applies it. – Auldrick (talk · contribs) 21:18, 8 April 2019 (UTC)
Part of my grumpyness about moving them was because I thought there were a bunch of commands that fit the criteria I was referring to of having been in multiple editions but now only existing in one. Turns out that the only such command is /toggledownfall and the rest were exclusive to either classic or the main version. (But to be clear: I still think that what would need to happen for that — copying /toggledownfall into two places — is gross, and that complicates everything else. The other commands are a less of an issue.)
You claim that this is the only such violation to that guideline, but the other overview pages are all the same: Block § Removed Blocks, Item § Removed items, Mob § Removed/Unimplemented mobs. And the inclusion of these has been relatively uncontroversial. You shouldn't have to go to 3 different edition-specific pages to get an overview of all commands (or mobs or items or blocks) that exist/ed.
I know I care about historical information than most people, but that's because I use it. It's useful to find when a command was added to figure out when a bug was first introduced, for instance. While any particular case is unlikely, the number of potential cases is high and impeding access to information when it actually comes up causes major pain. So I am pretty strongly against anything that could lead to that (say, things that lead to loss of page revision — I've used those too) in the future.
Since you've suggested it, I'll go propose a change to make this explicit. But I still stand by WP:IAR and similar applying here — this seems like an obvious case where having information is better than not. --Pokechu22 (talk) 00:54, 9 April 2019 (UTC)
Instead of putting them into the history table, a separate table could be created under the summary of commands. It would be better formatted that way and could keep a description of the command. The table is pretty big as it is; I think it would be good to break it up in other ways too if possible. jahunsbe (talk) 18:59, 8 April 2019 (UTC)
I'm mostly fine with that, other than the complexity associated with commands that still exist in some editions but not in others. But given that there's only one, it's probably not that big of a deal. --Pokechu22 (talk) 00:54, 9 April 2019 (UTC)

NBT[edit]

Can someone please document the "nbt" component? It's mostly documented at Java_Edition_1.14#Command_format_2, but not fully, for example it's questionable where you can use it. I just tried to summon an entity with such a component in its name and it didn't work. Fabian42 (talk) 15:50, 5 May 2019 (UTC)

Added basic format for it in the JSON structure part, but not sure on its usage still. Maybe it is used like score components? liach (talk) 02:17, 9 May 2019 (UTC)

/resupply?[edit]

there command exist? 180.190.51.87 00:30, 9 May 2019 (UTC)

Feedback to new section "List of argument types"[edit]

  1. Where do the "official examples" come from? There should be a link in the article.
  2. The syntax "{foo=bar}" is wrong, if that's really in the official examples, those should be changed. Who should get poked for that depends on where they even come from.
  3. Mixed positions like "1 ~2 ^3" are allowed, right? If yes, that should be mentioned in the article.
  4. The JSON component syntax should mention the new (1.14) syntax with the single quotes ('). I don't even know myself how that syntax works.
  5. Why are the examples for status effects "spooky" and "effect"? Those are not valid status effect IDs.
  6. Are the objective criteria namespaced or not? The explanation text says that they are not, but one of the examples is "minecraft:foo". Either that is one name that just happens to include a colon, then it's an extremely bad and confusing example or it is in fact namespaced.
  7. What is a "resource location"? The explanation and examples don't really explain it well.
  8. The score holder section should mention the fake player names starting with #, which can't be real player names and do not appear in sidebars etc. and the fake player names starting with $, which can also not be real player names, but do appear in sidebars etc.
  9. The NBT compounds, tags and paths should get better examples, for example returning multiple paths is not explained at all, as well as matching paths by values or selecting the root tag (I think that was {}) or matching by missing tag (I think that was {foo:}). Here is a gamingSE answer by me which explains a lot of these things, but it's also not complete (because that wasn't the main point of the answer): https://gaming.stackexchange.com/questions/351488/would-someone-give-a-thorough-explanation-of-1-14-minecrafts-data-modify/351499#351499 There should also be examples for nested NBT compounds. Fabian42 (talk) 10:42, 6 June 2019 (UTC)
RE Mixed positions like "1 ~2 ^3" are allowed, right? If yes, that should be mentioned in the article.: not like that, only absolute and relative may be mixed, local may only be with other local coordinates.
RE The JSON component syntax should mention the new (1.14) syntax with the single quotes ('). I don't even know myself how that syntax works.: simple, in " strings " has to be escaped, in ' strings ' has to be escaped, that's it.
RE Are the objective criteria namespaced or not? The explanation text says that they are not, but one of the examples is "minecraft:foo". Either that is one name that just happens to include a colon, then it's an extremely bad and confusing example or it is in fact namespaced.: They are not, but statistics are, as such statistic based objectives are, the rest not.
RE What is a "resource location"? The explanation and examples don't really explain it well.: It's the same as a namespaced ID, but then it refers to a file, eg minecraft:block/stone for a texture.
RE The score holder section should mention the fake player names starting with #, which can't be real player names and do not appear in sidebars etc. and the fake player names starting with $, which can also not be real player names, but do appear in sidebars etc.: Specifically the second part, this is not specific to $, player names can only contain A-Za-z0-9_- (IIRC), but not characters like : ; , ", etc. so this applies to everything that a player name cannot have (and is not specific to the beginning of the name either).
That being said, I didn't add this, nor read the change, just making some remarks regarding your message. FVbico (talk) 11:36, 6 June 2019 (UTC)
First, I made this change because I want to make my graphviz-based commmand graph dump reach perfection, in which every argument node can link to some description.
All official examples are directly copied from what vanilla offers in code. These examples are exposed with brigadier hooks; I see that many of them are indeed very erroneous, but I just copied what vanilla has exactly. In the example they offer for raw json text, they are even missing a double quote in the end! Simple conclusion: Don't trust the examples! Look at suggestions instead!
For the nbt path thing, I strongly recommend adding it here in the command arguments' section.
Objective criteria names are namespaced, but they are not namespaced IDs in commands. Much like how slots are integers but they aren't integers in commands.
For mixed positions, you can mix tildes with numbers or mix carets with numbers, but you cannot mix tildes and carets together.
For the resource location thing, I understand that my namespaced ID article needs some furnishing and clarifications (most likely in the usage part). Will do that some point soon (TM) liach (talk) 15:44, 6 June 2019 (UTC)
@Liachmodded:This section is about the type of argument parsers in brigadier ,not necessary to introduce commands and making the page cumbersome and the contents long. It's not convenient for players who want to consult how to use commands. How about moving it to brigadier?-Chixvv (talk) 15:12, 20 June 2019 (UTC)
@Chixvv: Note that this is not brigadier; this is another layer vanilla (Minecraft) offers beyond brigadier, and is a part of the Java Edition protocol. See https://wiki.vg/Protocol#Declare_Commands
Also, all argument nodes in all svg graphs in link to one of the command argument descriptors and we can gradually add links in the individual command pages to link each argument to one of the argument types on the page. liach (talk) 07:50, 26 June 2019 (UTC)

Thoughts on revising Commands#Command Guide to reflect in-game helper text[edit]

In the in-game helper text for commands, accessed mostly with the /help command, it uses <angle brackets> to describe entries the user would replace with their own values, not italics. (Notice the game would say [<target>] for the optional entry where you replace <target> with your own thing.) Removing italics from this article's Command Guide would remove the possibility for confusion when italics are used for other reasons, like for emphasis. Additionally, the game uses (parentheses|with|pipes) to describe a list of word options, and [brackets|with|pipes] when such lists are optional. I've writ up the edit and I'll submit it later this evening, unless anyone has any objections. - JavaRogers (talk) 00:37, 18 June 2019 (UTC)

I would  Agree with this proposed change. – Nixinova Nixinova sig1.png Nixinova sig2.png 03:30, 18 June 2019 (UTC)
 Agree Fabian42 (talk) 12:00, 18 June 2019 (UTC)

Thoughts on using headers on our [Commands/] subpages[edit]

What say ye to using proper ==headers== for "Syntax", "Arguments", "Results", and "Examples" on our Commands/ subpages? Currently they use semicolon+colon lists for these, a style suited for subject+definition types of lists. This change would free up the semicolon+colon style for use under the Arguments header, where such use might be more appropriate. (That style looks like the following):

Results
The page talks about results here

I've just started working through the Commands/ subpages to ensure they also fit the previous revision I brought up (^ one topic up), so I could implement these headers myself as I iterate through them. — JavaRogers (talk) 20:47, 30 June 2019 (UTC)

These were just copy and pasted from the main page two years ago without any formatting changes. Yee, I do think these should have subheadings, and have been adding them to whatever command pages I edit. I think the headings should include Syntax, Result and History. – Nixinova Nixinova sig1.png Nixinova sig2.png 20:50, 6 July 2019 (UTC)