cmdinfo

{
  "id": 659448,
  "created_at": "2021-03-07T22:18:48.000Z",
  "tag_name": "cmdinfo",
  "nsfw": false,
  "owner_id": "142417715452313600",
  "uses": 12,
  "description": null,
  "restricted": false,
  "shared": false,
  "deleted": false,
  "safe": "unrated",
  "hidden": false,
  "guild_id": "721573566277222470",
  "sharer": "142417715452313600",
  "content": "{=(largs):{lower:{args}}}\n{=(&comment): The error message if an incorrect option is put.}\n{=({args}): Incorrect option, try running `#cmdinfo help`.}\n{=(&comment): The help command.}\n{=(longhelp):\n**Available commands for information such as syntax and advanced usage.:**\n**How to read:** Run dictionary.\n**1.** Execute.\n**2.** Testfor.\n**3.** Testforblock.\n**4.** Testforblocks\n**5.** Tellraw\n**6.** Title.\n**7.** Conditional.\n**8.** MCExtension\n**9.** Manifest\n**10.** Setblock\n**11.** Fill\n**12.** Give\n**13.** Clear\n**14.** Spreadplayers\n**15.** Scoreboard\n**16.** Loot\n**17.** Replaceitem\n**18.** Tag\n**19.** TP\n**20.** Summon\n**21.** Effect\n**22.** Particle\n**23.** Function\nToo long? Try running `cmdinfo help` instead.}\n{=(help):\n**Command Info Help**\n\n**Hard to read? Try running `cmdinfo longhelp`.**\n\n**Don’t understand the vocabulary with these? Try running `cmdinfo dictionary`.**\n\nAvailable subcommands you can use:\n\n`execute, testfor, testforblock, testforblocks, tellraw, title, setblock, fill, give, clear, spreadplayers, scoreboard, loot, replaceitem, tag, tp, summon, effect, particle`\n\nOther things you **may need** information with as a command developer:\n`\nconditional, MCExtension, manifest, function\n`\nIf you’re new, be sure to read the MCExtension part to learn how to make your own map with an mcworld extension or your function pack.\n{embed(color):#2C2F33}}\n\n{=(&comment):Those are the commands, to replace one simply change the text for example execute to name the command and change up the text.}\n{=(execute):The execute command is used to force entities to run commands. The command’s syntax is as the following without detect.\n`/execute <target> <location> <command> <selected command syntax>`\nThe syntax with a detect is as the following:\n`/execute <target> <location> <detect> <block to detect> <detectPos> <command>`\nIf the entity detects the block to detect on the detect position, the command will be executed.\nFull syntax tree for java edition: [View syntax tree.](https://pastebin.com/raw/t5mM7E2G)}\n{=(testfor): This command tests for entities, it can be used to activate conditional command blocks. If the testfor command finds the entity, the command is successful.\nThis command can also be used to count entities.\nCommand syntax:\n`/testfor <target>`}\n{=(testforblock): This command tests for whether a certain block is in a specific location. See testforblocks (with an S) for multiple block testfor. This command can be used to activate conditional command blocks.\nCommand syntax:\n`testforblock <position: x y z > <Block> [dataValue]`}\n{=(testforblocks): This command tests whether the blocks in two regions match.You can use this for conditional command blocks.\nCommand syntax:\n`testforblocks <begin: x y z> <end: x y z> <destination: x y z> [masked|all]`\nArguments in masked/all.\nSpecifies how to match blocks. Must be one of:\nall — every block in the source and destination regions must match exactly.\nmasked — air blocks in the source region will match any block in the destination region.\nIf not specified, defaults to all.}\n{=(tellraw):This command sends a raw json message to the specified target. This appears without any external text, the message appears in chat alone, unlike a /say message.\nCommand Syntax (bedrock):\n`/tellraw <target> <raw json message>`\nThe [raw json](https://minecraft.gamepedia.com/Raw_JSON_text_format) message field is to be filled with something like this `{“rawtext”:[{“text”:”your text”}]}`.\nCommand Syntax (Java Edition):\n`/tellraw <target> <message>`}\n{=(title): The title command shows text onto the middle of the player’s screen, their action bar or under it as a subtitle.\nSyntax:\n`/title <target> (title | subtitle | actionbar) <text>`\n[View gamepedia syntax](https://minecraft.gamepedia.com/Commands/title#Syntax)}\n{=(conditional): Conditional command blocks are command blocks usually used in chains are command blocks that only work if the condition is met. These can be used in chains for shop systems and such.\nCopy paste from gamepedia:\nCondition\n\nTop: Command blocks in \"Unconditional\" mode. Bottom: Command blocks in \"Conditional\" mode.\nClick the \"Conditional/Unconditional\"‌[JE only]/\"Condition\"‌[BE only] button to change the command block's conditional behavior:\n\"Conditional\": A command block in conditional mode executes its command only when the command block behind it has executed successfully (\"Succeess count\" is greater than 0).\n\"Unconditional\" (default): A command block in unconditional mode executes its command even if there's a command block behind it that didn't execute its command successfully.\n\"Behind it\" in the sense of opposite to the direction the command block is facing, regardless of chain direction or even if chaining is occurring.}\n{=(mcextension):\n**.mc file extensions**\n**What are .mc extensions?** These extensions are used to quickly import worlds, behavior packs, resource packs, addons, function packs, etc onto Minecraft easily. .mc file extensions are currently exclusive to the Bedrock Edition of Minecraft.\n**How do I use a .mc extension?** To download anything from a .mc extension (.mcworld, .mctemplate, .mcpack, etc), simply open the file with Minecraft.\n**How do I create a .mc extension?** To create a .mc extension, zip all content (NOT THE FOLDER) then rename the .zip extension to .mc.\nFor maps: .mcworld.\nFor behavior packs: .mcpack\nFor resources: .mcpack.\n**Please run `cmdinfo function` for a full guide on how to setup the folders for your function pack.**}\n{=(manifest):\nThe manifest is a key file in all resource packs, worlds, behavior packs, etc. The manifest is what allows the pack to show on the list.\nSources:\n[Bedrock Manifests](https://minecraft.gamepedia.com/Bedrock_Edition_add-on_documentation#manifest.json)\n[Java Manifests](https://minecraft.gamepedia.com/Version_manifest.json)\n[Example of a Manifest](https://pastebin.com/raw/Lf73EJHe)\n[Bedrock Resources Manifest](https://pastebin.com/DXjv75sb)\n[Bedrock Behaviors Manifest](https://pastebin.com/zUFzsuVU)\n}\n{=(setblock):\nSetblock is a command that places a block at the specified location.\nSyntax: \n`/setblock <location> <block> [data]`}\n{=(fill):\nFill is a command that places blocks from a specified location to another.\n`/fill <from: x y z> <to: x y z> <block> [data]`.\n}\n{=(give):\nThe give command allows users to obtain items normally unobtainable, or items that already are through commands\nJava edition syntax:\n`give <target> <item> [<count>]`\nBedrock syntax:\n`give <player: target> <itemName: Item> [amount: int] [data: int] [components: json]`\nThe cans for that are: (on bedrock)\n`{“can_place_on”:{“blocks”:[“BLOCK”]}}`\n`{“can_destroy”:{“blocks”:[“BLOCK”]}}`\n[Available arguments (gamepedia)](https://minecraft.gamepedia.com/Commands/give#Arguments)\n}\n{=(clear): The clear command is a command used to remove items from a player’s inventory.\nSyntax (bedrock):\n```/clear <target> <item name> <data: interval> <maxCount>```\nThe data interval makes sure that the item matches the data interval, or the command will fail, this will not a trigger a conditional command block.\nTo test for an item in a player’s inventory, use the following syntax:\n```/clear <target> <item name> <data> 0```\nThe 0 will replace the command instead of deleting an item from a player’s inventory, it will check for one.\nSyntax (Java Edition):\n```/clear <target> <item> <maxcount>```\n[Gamepedia conditions table](https://minecraft.gamepedia.com/Commands/clear#Result)\n}\n{=(dictionary):\n**How to Read Guide:**\n**1.** Syntax \nThis means the format the command is used in.\n**2.** Manifest\nThis is the file in which you’ll have for things such as texture packs or bedrock edition addons.\n**3.** <> bracketing in syntax\nThis means that this part of the command is required for the specified use.\n**4.** () bracketing in syntax\nSeparated by |, this means that this part of the syntax must be one of the things within the brackets.\n**5.** [] bracketing in syntax\nThis means that the part of the syntax is optional.\n**6.** Target\nThis is the entity the command is being executed on.\n**7.** Entity\nAn entity is a mob, a player, a dropped item, an armor stand, falling gravel/sand or anything in the game that isn’t in a completely solid state and fixed to it’s location. This may not be the best explanation for an entity, but you get the point.}\n{=(spreadplayers): This command teleports entities to surface within a specified area.\nBedrock Edition Syntax:\n`/spreadplayers <x: value> <z: value> <spreadDistance: float> <maxRange: float> <victim: target>`\nJava edition syntax:\n`/spreadplayers <center> <spreadDistance> <maxRange> <respectTeams> <targets>`\n[Gamepedia arguments](https://minecraft.gamepedia.com/Commands/spreadplayers#Arguments)\nThis command can be used in advanced maps to allow players to spawn at random places.}\n{=(scoreboard): This is probably one of the most advanced commands in the game, it can be stored as currency in shop systems using conditional command blocks. This command adds a scoreboard.\n[Gamepedia (Bedrock)](https://minecraft.gamepedia.com/Scoreboard#In_Bedrock_Edition)\n[Gamepedia (Java)](https://minecraft.gamepedia.com/Scoreboard#In_Java_Edition)}\n{=(loot): This command is exclusive to Java Edition.\nSyntax Tree:\n`/loot <target> <source>\n<target>:\nspawn <targetPos>\nreplace entity <entities> <slot> [<count>]\nreplace block <targetPos> <slot> [<count>]\ngive <players>\ninsert <targetPos>\n<source>:\nfish <loot_table> <pos> [<tool>|mainhand|offhand]\nloot <loot_table>\nkill <target>\nmine <pos> [<tool>|mainhand|offhand].`\n[Gamepedia Argument Info](https://minecraft.gamepedia.com/Commands/loot#Arguments)}\n{=(replaceitem): This command can be used to replace an item in a player’s inventory or a chest/furnace/etc.\nJava Edition Syntax:\n`/replaceitem block <pos> <slot> <item> [<count>]`\n`/replaceitem entity <targets> <slot> <item> [<count>]`\nBedrock edition syntax is kinda.. longer. \n[Jump to syntax](https://minecraft.gamepedia.com/Commands/replaceitem#Syntax)}\n{=(tag): Controls scoreboard tags for entities.\nBedrock Edition:\nThis can also be used to add certain tags on entities in the [tag=tagname] entity selecting part.\nBedrock Syntax:\n```tag <entity: targets> <add|remove> <name: string>\ntag <entity: targets> list```\nJava Edition:\nThis is distinct from entity type tags, which are applied to entity types and cannot be changed by commands.\nVisit [here](https://minecraft.gamepedia.com/Tags) for more info regarding the above sentence.\nJava Edition Syntax:\n```tag <targets> <add | remove> <name>\ntag <targets> list```\n[Gamepedia Information Page](https://minecraft.gamepedia.com/Commands/tag)\nThis command could be used to set-up a restriction for users other than OP. However, regular commands cannot change permissions,}\n{embed(timestamp):now}\n{=(tp): The teleport command teleports entities to a specified location, or another entity.\nSyntax Laws:\nEntity/ies can be teleported at once to one target.\nIf an entity is requested to teleport to more than one target, the condition will fail.\nThis can be used to determine if a mob has died.\nMultiple entities can teleport to one coordinate.\nCommand Syntax:\n`teleport <victim> (location | target)`\nAdvanced usage of the syntax is very complicated, click [here](https://minecraft.gamepedia.com/Commands/teleport#Syntax) for more information regarding advanced usage of the syntax.}\n{=(summon):\nThe summon command is used to spawn in new entities into the world.\nEntities such as TNT can also be summoned with the /summon command.\nSyntax (Bedrock):\nWith spawn event\n`summon <entityType: EntityType> [spawnPos: x y z] [spawnEvent: string] [nameTag: string]`\nWithout spawn event\n`summon <entityType: EntityType> [nameTag: string] [spawnPos: x y z]`\nSyntax (Java Edition): \n`summon <entity> [<pos>] [<nbt>]`}\n{=(effect):\nThis command can add or remove status effects on players and other entities.\nYou know what effects are, they’re just potion stuff.\nSyntax (Bedrock):\nClear Effects\n`effect <player: target> clear`\nAdd or remove an effect\n`effect <player: target> <effect: Effect> [seconds: int] [amplifier: int] [hideParticles: true/false]`\nAmplifier is the level of the effect. eg: strength 5 (amplifier).\nSyntax (Java Edition):\nRemove an effect\n`effect clear [<targets>] [<effect>]`\nAdd an effect \n`effect give <targets> <effect> [<seconds>] [<amplifier>] [<hideParticles>]`\n}\n{=(particle): Particle is a very interesting command, it can be used in multiple different ways to add effects such as smoke effects without using things like campfires, or villager anger effects. These are just some examples of what you can do with particle. \nIn some editions of Minecraft, you can modify how the particles look, effectively adding things such as custom holograms.\nThe syntax for Bedrock Edition is the following:\n`particle <effect: string> <position: x y z>`\nThe syntax for Java Edition is the following:\n`particle <name> [<parameters>] [<pos>] [<delta>] <speed> <count> [force|normal] [<viewers>]`\n[Click here to see all particles and their names.](https://minecraft.gamepedia.com/Particles#Types_of_particles)\n}\n{=(function):\nFunctions are a way to kinda import a ton of commands into new worlds easily, unlike command blocks however, they cannot be conditional.\nWhen you run the `function` command, it executes the .mcfunction file named by your argument.\n\nFor example, a file named `cool_file.mcfunction` will execute if you return the argument as `cool_file` in other words,\n`/function cool_file` , however, if a different argument is written, the game will search for the .mcfunction named by that, if none, the command will fail.\n\n.mcfunction files are always filled with nothing but commands.\n\nNow for the folder setup.\n\nBedrock Edition:\n`<your pack name> \n<functions> <manifest.json> <pack_icon.png>\n<cool_file.mcfunction> <cool_file2.mcfunction>`\n\nJava Edition one’s a lot less simple, visit gamepedia link [here](https://minecraft.gamepedia.com/Function)\n\n**See `cmdinfo manifest` and be sure that the pack icon is in the png format, sometimes even if the png is capitalized it will not show it.**}",
  "embed": "{\"color\": 3669760, \"title\": \"Information\", \"timestamp\": \"2021-03-07T17:00:00.000\", \"description\": \"{{largs}}\"}",
  "last_fetched": "2026-10-21T00:35:48.186Z"
}