MC-99434worldborder damage command not giving any feedback with invalid argument
The bug
When using the /worldborder damage command with any argument except the allowed ones creates no command feedback.
How to reproduce
Use the following command
/worldborder damage invalidArgument
→ No command feedback is displayed in the chat
The reason
The following is based on decompiled version of Minecraft 1.9 using MCP 9.24 beta. All method and class names are the names used in the decompiled version.
The reason why this happens is because the method net.minecraft.command.CommandWorldBorder.execute(MinecraftServer, ICommandSender, String[]) only tests if the given argument is "buffer" or "amount". It should however throw a WrongUsageException if this is not the case.
Linked Issues
relates to1
Created Issue:
Missing command feedback for worldborder damage command
Relates to
MC-56162The bug
When using the /worldborder damage command gives no command feedback anymore.
How to reproduce
Use the following command
/worldborder set 1No command feedback is displayed in the chat
Missing command feedback forworldborder damage commandworldborder damage command not working anymore
Relates to
MC-56162The bug
When using the /worldborder damage command gives no command feedback anymore and the damage that will be dealt does not change.
How to reproduce
Use the following command
/worldborder set 1No command feedback is displayed in the chat
Relates to
MC-56162The bug
When using the /worldborder damage command gives no command feedback anymore and the damage that will be dealt does not change.
How to reproduce
Use the following command
/worldborder set 1No command feedback is displayed in the chat
relates to
NoteThis might be the intended behaviour for 1.9.1 pre releases based on [Mojang] Searge (Michael Stoyke)'s comment on
MC-56162:It will be fixed in 1.9.1, but there's already a workaround for 1.9 by using the worldborder buffer zone, setting that to a very high value means that within the distance of x blocks outside of the border, no damage will be applied.
The bug
When using the /worldborder damage command gives no command feedback anymore and the damage that will be dealt does not change.
How to reproduce
Use the following command
/worldborder damage 1No command feedback is displayed in the chat
worldborder damage command notworking anymoreworldborder damage command not giving any feedback with invalid argument
NoteThis might be the intended behaviour for 1.9.1 pre releases based on [Mojang] Searge (Michael Stoyke)'s comment on
MC-56162:It will be fixed in 1.9.1, but there's already a workaround for 1.9 by using the worldborder buffer zone, setting that to a very high value means that within the distance of x blocks outside of the border, no damage will be applied.
The bug
When using the /worldborder damage command
gives no command feedback anymore and the damage that will be dealt does notchange.How to reproduce
Use the following command
/worldborder damage1No command feedback is displayed in the chat
The bug
When using the /worldborder damage command with any argument except the allowed ones creates no command feedback.
How to reproduce
Use the following command
/worldborder damage invalidArgumentNo command feedback is displayed in the chat
The reason
The following is based on decompiled version of Minecraft 1.9 using MCP 9.24 beta. All method and class names are the names used in the decompiled version.
The reason why this happens is because the method net.minecraft.command.CommandWorldBorder.execute(MinecraftServer, ICommandSender, String[]) only tests if the given argument is "buffer" or "amount". It should however throw a WrongUsageException if this is not the case.
The bug
When using the /worldborder damage command with any argument except the allowed ones creates no command feedback.
How to reproduce
Use the following command
/worldborder damage invalidArgument→ No command feedback is displayed in the chat
The reason
The following is based on decompiled version of Minecraft 1.9 using MCP 9.24 beta. All method and class names are the names used in the decompiled version.
The reason why this happens is because the method net.minecraft.command.CommandWorldBorder.execute(MinecraftServer, ICommandSender, String[]) only tests if the given argument is "buffer" or "amount". It should however throw a WrongUsageException if this is not the case.
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
![[Mod] Neko](../../../data/avatars/users/92901.png){kind=small}
Can confirm for MC 1.12.1.