5

Follow

Don’t remove /replaceitem

For everyone who has done data packs or commands, you know how frustrating it is to have commands no longer work because syntax changed over the years. For example, when the zombified piglins replaced the zombie pigmen and the syntax changed, I had problems for about 3 weeks with a datapack, and the ONLY problem was the pigmen change. Especially for Bedrock edition players, who have had the same commands forever, and can’t use a text editor for datapacks, they can only use command blocks, changing every replaceitem to item replace would take forever and be really annoying. Don’t get me wrong, item replace is awesome, but nobody wants to redo all their work because of it. Mojang, please keep replaceitem for all our sanity. Thanks.

Registered User shared this idea

• December 14, 2020 02:59
• Report a Concern

Please sign in to leave a comment.

• 3

  Registered User commented

  Comment actions Permalink

  • December 24, 2020 21:45
  • Report a Concern
  • Comment actions Permalink

  This is a very interesting proposal. Unlike Java Edition, Bedrock Edition doesn't keep its legacy versions, instead, you're forced to update and it's a point of no return. Backwards compatibility is always an issue while updating, and it's the reason why you can't name a folder CON in Windows 10. try it, you'll get an error.

  I understand the problem that moving commands will take a while, but at the same time, Mojang would prefer new commands to use the new syntax. I think that as a good compromise, the syntax helper for /replaceitem should just vanish. It will still work, but it won't be shown as a valid command in the autocomplete form. If the team does not like the idea of hiding commands from view, perhaps they'll be more open to changing the message to something like this:

  /replaceitem: Deprecated, use /item instead.

  And that will tell people to use the new syntax, while keeping the old one in for backwards compatibility.