The Meaning of Life, the Universe, and Everything.
Join Date:
8/4/2013
Posts:
124
Member Details
So i was playing Minecraft, making a player heads shop, when i got the idea to make a pressure plate that gives you your players head. So i tried this code: /give @p 379 1 3 {SkullOwner:@p}.
But that didn't work so i made a new thread and asked how i would do that and they said it was basically impossible without having every players name in a command block. So i figured when you do @p it jut targets the nearest player. I think it should target it then shortly replace it with that players name. If you where to do that it would work. This would be great in player heads shops and even some adventure maps.
So i was playing Minecraft, making a player heads shop, when i got the idea to make a pressure plate that gives you your players head. So i tried this code: /give @p 379 1 3 {SkullOwner:@p}.
But that didn't work so i made a new thread and asked how i would do that and they said it was basically impossible without having every players name in a command block. So i figured when you do @p it jut targets the nearest player. I think it should target it then shortly replace it with that players name. If you where to do that it would work. This would be great in player heads shops and even some adventure maps.
It's to difficult to implement, and I actually don't see this being used that much.
Quality of suggestion: ★★☆☆☆ [2/5 stars, vague and not needed] No support.
I'll rephrase for him:
In commands that support NBT tags (/give, /setblock, /testforblock, /summon), player selectors (@p, @a, @r) are not parsed, meaning you cannot automatically input player names into the tags. His suggestion is to allow the dataTags to parse player selectors.
This would allow map makers to accomplish the following:
1. Insert player names into the "Name" and "Lore" tags on all items.
2. Insert player names into the "title", "author", and "pages" tags in books.
3. Insert player names into the "SkullOwner" tag for player heads.
4. Insert player names into the "CustomName" tag for mobs and tile entities.
5. Insert player names into the "Owner" tag for all tame-able mobs.
6. Insert player names into the "ownerName" tag for thrown enderpearls, thrown EXP bottles, thrown potions, and thrown snowballs.
7. Insert player names into the "Owner" and "Thrower" tags for item entities.
8. Insert player names into the "Text1/2/3/4" tags for signs.
So essentially any string tag is applicable, but I've listed those that would be useful in some manner to folks.
So a fair bit of uses, all can come with aesthetic and technical features and ideas. As such, I support this function. I expect it would see a lot of use in maps and minigames (which is what these commands are usually for in the first place).
In commands that support NBT tags (/give, /setblock, /testforblock, /summon), player selectors (@p, @a, @r) are not parsed, meaning you cannot input player names into the tags. His suggestion is to allow the dataTags to parse player selectors.
This would allow map makers to accomplish the following:
1. Insert player names into the "Name" and "Lore" tags on items.
2. Insert player names into the "title", "author", and "pages" tags in books.
3. Insert player names into the "SkullOwner" tag for player heads.
4. Insert player names into the "CustomName" tag for mobs and tile entities.
5. Insert player names into the "Owner" tag for all tame-able mobs.
6. Insert player names into the "ownerName" tag for thrown enderpearls, thrown EXP bottles, thrown potions, and thrown snowballs.
7. Insert player names into the "Owner" and "Thrower" tags for item entities.
8. Insert player names into the "Text1/2/3/4" tags for signs.
So a fair bit of uses, all that can come with aesthetic and technical features and ideas. As such, I support this function. I expect it would see a lot of use in maps and minigames (which is what these commands are usually for in the first place).
Thank you so much you helped out my thread alot!.
You are awesome.
I would've known all that if I'd used command blocks more often i need to learn how to.
LOL
The only reason why you wouldn't add this is because you could have the problem of actually wanting the word "@p" in the data tag, which isn't ever realistically going to be used. This would help me a lot more than it would be hurt, people saying that "u ever need player skulls" are just assuming that is the only practical application. I was trying to get a pet for the player in my adventure map, a pet puppy dog that would stay a puppy and would be named "(player's) dog," which I couldn't do as it came to "@p's dog," and I couldn't get the dog to belong to the player.
Also, I tried a /tellraw to have the text say "@p is it" for tag, but it wouldn't work, so I had to use /say.
Support. There is no real reason this shouldn't be in game.
Being able to give player heads through a command block is totally useless, and unneeded.
Unfortunately, nosupport, from me.
I would hardly call this, and any other of the practical applications Skylinerw and I listed, useless and unneeded, this is actually really helpful for some mapmakers.
It's to difficult to implement, and I actually don't see this being used that much.
Quality of suggestion: ★★☆☆☆ [2/5 stars, vague and not needed] No support.
Difficult to implement? How so? The code's already present in-game, all it has to do is search for the words @p, @a, and @r inside data tags and /tellraw text. Vague, yes, this was a little undescriptive, but it is needed, or helpful in my opinion.
Thank you so much you helped out my thread alot!.
You are awesome.
I would've known all that if I'd used command blocks more often i need to learn how to.
LOL
The word "alot" does not exist, instead use "A lot" if talking about a large extent, or "allot" for a synonym for "distribute."
The only reason why you wouldn't add this is because you could have the problem of actually wanting the word "@p" in the data tag, which isn't ever realistically going to be used.
To add: if it were to be used, a typical 'escape' method could be implemented in the event you want to use "@p" as a word rather than a player selector. For example:
/summon Villager ~ ~1 ~ {CustomName:"@p"}
The above would give the villager a custom name of the nearest player.
If we use conventional escaping:
/summon Villager ~ ~1 ~ {CustomName:"\@p"}
Would create a villager with the name "@p".
Escaping is already seen in the /tellraw command for doubled-up quotes, allowing players to nest strings within the "text" and "value" tags (to allow for commands within commands). For example:
/tellraw @a {
text:"TEST",
clickEvent:{
action:run_command,
value:"/tellraw @a \"This is a test\""
}
}
So you can get the best of both worlds. I agree though; I don't see "@p" being used as a word anywhere, except for a command/command-block tutorial map.
But that didn't work so i made a new thread and asked how i would do that and they said it was basically impossible without having every players name in a command block. So i figured when you do @p it jut targets the nearest player. I think it should target it then shortly replace it with that players name. If you where to do that it would work. This would be great in player heads shops and even some adventure maps.
Quality of suggestion: ★★☆☆☆ [2/5 stars, vague and not needed]
No support.
I'll rephrase for him:
In commands that support NBT tags (/give, /setblock, /testforblock, /summon), player selectors (@p, @a, @r) are not parsed, meaning you cannot automatically input player names into the tags. His suggestion is to allow the dataTags to parse player selectors.
This would allow map makers to accomplish the following:
1. Insert player names into the "Name" and "Lore" tags on all items.
2. Insert player names into the "title", "author", and "pages" tags in books.
3. Insert player names into the "SkullOwner" tag for player heads.
4. Insert player names into the "CustomName" tag for mobs and tile entities.
5. Insert player names into the "Owner" tag for all tame-able mobs.
6. Insert player names into the "ownerName" tag for thrown enderpearls, thrown EXP bottles, thrown potions, and thrown snowballs.
7. Insert player names into the "Owner" and "Thrower" tags for item entities.
8. Insert player names into the "Text1/2/3/4" tags for signs.
So essentially any string tag is applicable, but I've listed those that would be useful in some manner to folks.
So a fair bit of uses, all can come with aesthetic and technical features and ideas. As such, I support this function. I expect it would see a lot of use in maps and minigames (which is what these commands are usually for in the first place).
You can find more info on NBT tags for:
Items: http://minecraft.gamepedia.com/Item_Format
Entities: http://minecraft.gamepedia.com/Chunk_format
Basic info: http://minecraft.gamepedia.com/Nbt_format
EDIT:
I suggest you read the stickied topic for suggestion criticizing here: http://www.minecraftforum.net/topic/503191-for-the-critics/
Specifically under "This cannot be coded" and "THIS WOULD BE USELESS!" sections.
Minecraft-things: http://skylinerw.com
More Minecraft-things: https://sourceblock.net
Guides for command-related features (eventually moving to Source Block): https://github.com/skylinerw/guides
I primarily hang out in the /r/MinecraftCommands discord, where there's a lot of people that help with commands: https://discord.gg/QAFXFtZ
Their corresponding subreddit: https://www.reddit.com/r/MinecraftCommands/
You are awesome.
I would've known all that if I'd used command blocks more often i need to learn how to.
LOL
Being able to give player heads through a command block is totally useless, and unneeded.
Unfortunately, no support, from me.
Also, I tried a /tellraw to have the text say "@p is it" for tag, but it wouldn't work, so I had to use /say.
Support. There is no real reason this shouldn't be in game.
I would hardly call this, and any other of the practical applications Skylinerw and I listed, useless and unneeded, this is actually really helpful for some mapmakers.
Difficult to implement? How so? The code's already present in-game, all it has to do is search for the words @p, @a, and @r inside data tags and /tellraw text. Vague, yes, this was a little undescriptive, but it is needed, or helpful in my opinion. The word "alot" does not exist, instead use "A lot" if talking about a large extent, or "allot" for a synonym for "distribute."
To add: if it were to be used, a typical 'escape' method could be implemented in the event you want to use "@p" as a word rather than a player selector. For example:
The above would give the villager a custom name of the nearest player.
If we use conventional escaping:
Would create a villager with the name "@p".
Escaping is already seen in the /tellraw command for doubled-up quotes, allowing players to nest strings within the "text" and "value" tags (to allow for commands within commands). For example:
So you can get the best of both worlds. I agree though; I don't see "@p" being used as a word anywhere, except for a command/command-block tutorial map.
Minecraft-things: http://skylinerw.com
More Minecraft-things: https://sourceblock.net
Guides for command-related features (eventually moving to Source Block): https://github.com/skylinerw/guides
I primarily hang out in the /r/MinecraftCommands discord, where there's a lot of people that help with commands: https://discord.gg/QAFXFtZ
Their corresponding subreddit: https://www.reddit.com/r/MinecraftCommands/