#fill command "replace" and "keep" not working
1 messages · Page 1 of 1 (latest)
@mild path Could you do that?
You need to add a blockState if you use replace
grass is somehow not the block, use grass_block instead
With the latest version and using [] for the state you should be able to use the command
ok thanks, i will try when we update to latest 👍
its working now but the wrong way
for the op example it replaces air with snow_layer now instead of snow_layer with air
@mild path
open
Still not fixed
For reference how it should work:
https://tomocraft.github.io/bedrock-commands-docs/#cmd-fill
@trail sedge could you check if /fill works with the latest build?
Sorry for taking almost a year, omg.
Thanks a lot, it's mostly working now. Only a few less important bugs I encountered:
- Some blockstates are throwing errors (see attached log)
- The destroy fillmode doesn't drop destroyed blocks (even though dotiledrops is set to true)
- The block enum still contains the old, unsupported block names (e.g. "grass") (although I think it would be better if these also worked, as in Vanilla, the fill command still works with the old names, but it doesn't on PNX)
Also, is the 32768 block limit a technical limitation or could this be raised/removed as it was before?
I set the limitation again since it's vanilla behavior. It could be raised, but you're better off using WorldEdit then
Hmm, error looks more like a parsing error, not a /fill error. Does that also happen when using /setblock?
Can't try that since /setblock is still using tileData
/setblock command issues:
- coordinates autocompletion suggests numbers with two decimal digits
- blockStates are not working at all (shows "syntax error" in chat)
- it's still using the old tileData
Reference: https://tomocraft.github.io/bedrock-commands-docs/#cmd-setblock
Hmm okay, but I already found the issue with block data so it doesn't really matter anymore
Unfortunately my Minecraft client is failing to boot so this might take a few days again
Amazing, thank you
It's not that much of an issue so no worries 👍