• 0

    posted a message on Looking for help setting up my functions for my server 1.13

    Try

    /world/datapacks/server/data/server/functions/cbh_spawn_protection.mcfunction

    Posted in: Commands, Command Blocks and Functions
  • 1

    posted a message on Looking for help setting up my functions for my server 1.13

    For your command, if you run it in command block, the default coordinate would be where the block is. execute as @a at @s <fill the rest...>

    For your mcmeta, there is no such tag name Contains functions for the server, "description":"your description here"



    That's all I can help, since I am not familiar with the server's file structure. If the datapack still doesn't shows up on the list, there must be something wrong for the path.

    Posted in: Commands, Command Blocks and Functions
  • 0

    posted a message on Speed Up Brewing, and Furnaces

    I tried, and it work.

    Can't tell where you did wrong if you don't shows us how you did it.

    Posted in: Commands, Command Blocks and Functions
  • 0

    posted a message on Speed Up Brewing, and Furnaces

    Not sure about Brewing. To speed up the furnace, you can change the vanilla recipes for the one you want. Either put it in your datapack or data folder in your saves.


    Here is a vanilla iron ingot recipe

    data\minecraft\recipes\iron_ingot

    {
     "type": "smelting",
     "ingredient": {"item": "minecraft:iron_ore"},
     "result": "minecraft:iron_ingot",
     "experience": 0.7,
     "cookingtime": 200
    }


    See the cookingtime at the end? 200 ticks, which is 10 seconds. By the way, smelting type was added in 1.13.

    Posted in: Commands, Command Blocks and Functions
  • 1

    posted a message on Java edition, vanilla - /tp and /teleport behave identically from console.

    Thats is before 1.12 I believe. tp and teleport now are just the same command.



    All the command use the coordinate base on the executor. Except tp, which use the coordinate of the target instead of executor.

    So teleport is there to match up with how the command get their default coordinate. Then they decided to replace tp completely with teleport. Tp hasnt remove, but it does the same as teleport.


    So what you read is outdate.

    Posted in: Commands, Command Blocks and Functions
  • 0

    posted a message on Need help with syntax and making items emit light

    There is only one way to emit light, which is to place blocks(torch/brown mushroom/sea pickles/lava...). You may also want to change the texture of this block for better visual experience.



    Or you can apply glowing effect on them by doing data merge entity @s {Glowing:1b}

    The down side is you can see through, and this is not a light source, just a highlight.

    Posted in: Commands, Command Blocks and Functions
  • 0

    posted a message on /execute holding named item 1.13

    If the command above doesn't work, try this...

    /execute as @a[nbt={SelectedItem:{tag:{display:{Name:"{\"text\":\"meh\"}"}}}}] run say hi

    Posted in: Commands, Command Blocks and Functions
  • 0

    posted a message on Test for weather

    The only way that I know is spawn or data merge an entity with Fire:2s, detect if it becomes Fire:-1s in the next tick. Raining if is -1s.




    To differentiate normal rain and thunderstorm, you may want to use a spawner or light detector for light level detection. Haven't tried it myself but since you require no block place, I think you cannot differentiate them.

    Posted in: Commands, Command Blocks and Functions
  • 0

    posted a message on New 1.13 Commands, is there a reference anywhere?

    Some(or most prehaps?) of the changes aren't even listed on the version.


    I had read every 1.13 snapshot changes as soon as they came out. Yes, the new command format are listed there, but most of the nbt changes aren't listed.


    I remember Enchantments is one of those.

    Another one that I found is suffix for Damage. Before 1.13, if you check a weapon's Damage nbt, you get Damage:1s. Where s means this is a short type value. Since 1.13, it become Damage:1 without suffix. And some strange things happen when detecting Damage:1s.


    Since I am working on my own resourcepack, I also noticed that "normal" variant in blockstates changed to "". Which doesn't quite make sense to me, and they said is work as intend in JIRA...

    Posted in: Commands, Command Blocks and Functions
  • 1

    posted a message on CanPlaceOn data tag problem
    /give @p emerald_block 1 0 {CanPlaceOn:["prismarine"]}

    This one can place on Prismarine, Prismarine Bricks, and Dark Prismarine.



    You cannot specific which block data value in CanPlaceOn and CanDestroy until 1.13. Which means if you want a emerald block to place only on red wool, you have to do CanPlaceOn:["wool"], and that will allow it to place on other wools as a result. I think they were planning to remove the block id limit at that time, that's why they didn't fix this since it came out. And now in 1.13, every block has it own id. So this is not a issue anymore if you are using version 1.13 or higher.

    Posted in: Commands, Command Blocks and Functions
  • 0

    posted a message on What was the bad thing about the "lookfor" command?

    I won't answer 6 or extra "challenge" just to prove you how /testfor is outdated.

    Instead, here is one example. (yes, one is good enough to show how useless /testfor is)





    Example: Kill all the on ground dropped item.


    Before 1.13, If you use /testfor

    First method

    /testfor @e[type=item] {OnGround:1b}

    [comparator]

    /kill @e[type=item]


    Second method

    /testfor @e[type=item] {OnGround:1b}

    [comparator]

    /scoreboard players tag @e[type=item] add onground {OnGround:1b}

    /kill @e[tag=onground]



    There's absolutely a huge problem for the first method. All the other non-OnGround item will be kill together as long as one OnGround item was found.

    In order to kill only the on ground ones, we have the second method to add tag and kill those will tag. It works now, but the /testfor doesn't do much here, it just restate the target selector and nbt tags, so why bother to use /testfor.


    Without using testfor

    Third...

    /scoreboard players tag @e[type=item] add onground {OnGround:1b}

    /kill @e[tag=onground]



    In 1.13, /testfor is replaced by /execute, so now you just need one command to achieve this.

    /kill @e[type=item,nbt={OnGround:1b}]


    Of course if you prefer the /testfor+comparator way, where /execute is playing the exactly same role as /testfor in 1.12(but again...why detect it twice)

    /execute if entity @e[type=item,nbt={OnGround:1b}]

    [comparator]

    /kill @e[type=item,nbt={OnGround:1b}]







    Yes, /testfor and /testforblock are able to detect what you want, but what next?

    What we are trying to tell you is that, what you found in /testfor doesn't really relate to whatever command you use, or chain. And this is the limit and the main problem for /testfor.



    /testfor(testforblock,testforblocks) aren't removed. They are just replaced by /execute, because /execute can do the same, and better.

    The difference between removed and replaced, hope you can understand that.





    But hey, if you still prefer /testfor, that's fine. 1.12 is always there for you :D

    Posted in: Commands, Command Blocks and Functions
  • 0

    posted a message on What was the bad thing about the "lookfor" command?

    I think Skylinerw explained well enough...


    Since the day "execute" came out, I rarely used "testfor". And "testfor" is nearly useless in function.

    Posted in: Commands, Command Blocks and Functions
  • 0

    posted a message on Can't Use an 'Execute' Command to Kill One Person

    Not sure how Bedrock Edition works. In java edition, this would be

    /execute @a ~ ~ ~ detect ~ ~-1 ~ concrete 15 kill @s


    @s means the player that run this command, and execute @a means let every player run the following command. Together it means, everyone who stand on those block will run "kill @s" command.

    Posted in: Commands, Command Blocks and Functions
  • 0

    posted a message on 1.13 Score command Fix?

    /scoreboard players set @a[scores={Mana=101..}] Mana 100

    http://minecraft.gamepedia.com/1.13

    Posted in: Commands, Command Blocks and Functions
  • 0

    posted a message on Execute If block ~ ~ ~ hopper run ... doesn't seem to work with hopper{<nbt>}

    Quotation mark and suffix are important, always.


    Slot:0b,id:"minecraft:ender_pearl",Count:1b...

    Posted in: Commands, Command Blocks and Functions
  • To post a comment, please or register a new account.