Can you make it so there is no limit to enchantment in commands?I really am hating these enchantment s like knockback 2 and Fire Aspect 1 and they are really weak so could you add no limit to enchantment s from commands?

- Report Post
38 Comments
Please sign in to leave a comment.
-
You can /give an item with any level of enchantment, though values over 32,767 overflow into negatives, and can have unintended consequences.
In 1.13, the NBT involved is as follows: {Enchantments:[{id:"minecraft:protection",lvl:10s}]}
When attached to an item, that gives it Protection 10. You can find a full list of IDs on the Minecraft gamepedia.
This only needs to be implemented in bedrock as it is already in java using the hive command. You should be able to bypass the enchantment cap with the /enchant command.
Ex. /enchant ExamplePlayerName sharpness 200Speaking from a Java Edition player's perspective
You can already bypass enchantment level limits by using /give, /replaceitem, loot tables, etc. with custom NBT, and you can already add enchantments beyond the level limits to existing items using a roundabout method involving multiple commands, but it would be nice to be able to bypass the limits using the much friendlier /enchant command.
Good idea
@Thainhawk
That’s already true for the effect command. Unlike the limits on the enchant command, effect is not artificially limited to what is possible in survival. There’s a hard limit of 255 that comes from the way that effect levels are stored, and it should stay that way.
KillerTron please update title name or post to indicate what version you are talking about.
There is a command that can do that but it has a max: /give @p minecraft:netherite_sword{display:{Name:"[{\"text\":\"Netherite Sword\",\"color\":\"aqua\",\"italic\":false}]",Lore:["{\"text\":\"Sharpness 1000\",\"color\":\"gray\",\"italic\":false}"]},Unbreakable:1,HideFlags:7,Enchantments:[{id:sharpness,lvl:10000}]}
Version: 1.16
if you do it to high then the level will be 0
And it is java
I, for one, find it pointless that one command should be more limited than another in creating the same result. In fact, I find it pointless that either of them should have restrictions. They're commands, not an intended gameplay function. By definition they are admin tools, for playing outside the normal rules of the game.
This is about minecraft bedrock not java, on console/pc/mobile, there is a level cap for every enchantment, not a lvl 255 lvl cap. Very annoying to map makers on console since we can't fix it without switching from console to pc and using a separate program not licensed by mojang/microsoft
Hi deception You are correct. From the Minecraft Wiki:
lvl: The level of the enchantment, where 1 is level 1. Saved as short when created by enchanting tables or loot tables, but read as an int and supports full int range.
So you are correct, and 2,000,000,000 is in the range of accepted values. But, there actually is still a limit, it's just higher. The limit is actually 2,147,483,647.
you can, it just has to be with the /give and not /enchant command.
for example if I wanted to enchant a stick with knockback 1000 I would do this:
/give @p minecraft:stick{Enchantments:[{id:knockback,lvl:1000}]} 1/give @p netherite_sword{Unbreakable:1,CanDestroy:[missingno],Enchantments:[{id:bane_of_arthropods,lvl:2147483647},{id:fire_aspect,lvl:255},{id:knockback,lvl:255},{id:looting,lvl:255},{id:mending,lvl:1},{id:sharpness,lvl:2147483647},{id:smite,lvl:2147483647},{id:sweeping,lvl:2147483647},{id:unbreaking,lvl:255},{id:vanishing_curse,lvl:1}]}
Post a new comment: