Enchantments don't reset in multiplayer
I'm playing in multiplayer on a MCPE 0.12.1 Server.
I've built a enchantment table and placed it accessible for all.
When the Host enchants an Item, he'll get different enchantments offered afterwards.
When I (Client) enchant items, the enchantment doesn't change afterwards. I can reproduce the same enchantment over and over.
I can abuse the bug to get lots of luck I books, but somehow this isn't what i want...
Update by [Mojang] Adrian Östergård
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
Please avoid duplicate comments. Post only NEW information regarding this bug.
Linked Issues
is duplicated by7
relates to1
Created Issue:
Enchantment don't reset in multiplayer
I'm playing in multiplayer on a MCPE 0.12.1 Server.
I've built a enchantment table and placed it accessible for all.
When the Server enchants an Item, he'll get different enchantments offered afterwards.
When I (Client) enchant items, the enchantment doesn't change afterwards. I can reproduce the same enchantment over and over.
I can abuse the bug to get lots of luck I books, but somehow this isn't what i want...
Enchantments don't reset in multiplayer
I'm playing in multiplayer on a MCPE 0.12.1 Server.
I've built a enchantment table and placed it accessible for all.
When the
Serverenchants an Item, he'll get different enchantments offered afterwards.When I (Client) enchant items, the enchantment doesn't change afterwards. I can reproduce the same enchantment over and over.
I can abuse the bug to get lots of luck I books, but somehow this isn't what i want...
I'm playing in multiplayer on a MCPE 0.12.1 Server.
I've built a enchantment table and placed it accessible for all.
When the Host enchants an Item, he'll get different enchantments offered afterwards.
When I (Client) enchant items, the enchantment doesn't change afterwards. I can reproduce the same enchantment over and over.
I can abuse the bug to get lots of luck I books, but somehow this isn't what i want...
relates to
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
I'm playing in multiplayer on a MCPE 0.12.1 Server.
I've built a enchantment table and placed it accessible for all.
When the Host enchants an Item, he'll get different enchantments offered afterwards.
When I (Client) enchant items, the enchantment doesn't change afterwards. I can reproduce the same enchantment over and over.
I can abuse the bug to get lots of luck I books, but somehow this isn't what i want...
Update by [Mojang] Adrian Östergård
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
Please avoid duplicate comments. Post only NEW information regarding this bug.
is duplicated by
I have new info on this bug! On Minecraft Windows 10 Edition 1.0.5 on realms, this bugs comes back in a different way! In my realm I enchanted a few items, changing the enchantments shown in the enchantment table. However when I leave my realm then rejoin my realm, the enchantments reset and go back to the first enchantments I had before!
I have new info on this bug! On Minecraft Windows 10 Edition 1.0.5 on realms, this bugs comes back in a different way! In my realm I enchanted a few items, changing the enchantments shown in the enchantment table. However when I leave my realm then rejoin my realm, the enchantments reset and go back to the first enchantments I had before! This bug was fixed in 0.16.0 but now comes back in MCPE 1.0.5 realm.
Please add any further information you may have on MCPE-10832.
Duplicate of MCPE-10832
Thank you for your report! However, this issue has already been reported as MCPE-10832. Consider doing a search next time, to check if a report on the issue you're submitting doesn't already exist.
Duplicate of MCPE-10832
Thanks for your report! This is however a Duplicate of MCPE-10832 – If you have not, please use the search function in the future, to see if your bug has already been submitted, as currently over 47% of tickets are being closed as duplicate.
This issue duplicates MCPE-10832. Please perform a search next time to make sure your bug hasn't already been reported.
You're right Shannon but that's a different known bug MCPE-10832.
Thank you for your report!
However, this issue has been closed as a Duplicate of MCPE-10832.
It has been linked to this report. If you have additional information, please add it to that report.
Please search before reporting, as it's likely that one exists already.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Feedback – 📖 Game Wiki
If I understand, enchanting another item does not refresh the enchantments, correct?
Yes. I've tested it yesterday evening.
The server can use the enchantment table, and will get different enchantments when he does an enchantment (as expected)
The client can enchant an item, and when trying to enchant the next item he'll be offered the exact same enchantments. (Different Item types (e.g. book vs. sword) will get different enchantments, though - but for books and for swords its the same list all the time. You can alter the lists by blocking some bookshelves, but even those are fixed lists for max-level 28)
Interesting and found while testing: When the Server has the enchantment table open & an item placed in it, and the client does the same, both UIs change to show the same enchantments (the fixed list of enchantments the client gets to see all the time).
My educated guess: The random seed isn't set properly when the client is using the table (or not saved to the client-slot, after using the table)
This happened to me on all of the world I play on local multiplayer when I am not the creator on my IPad Mini IOS 9.1 and when after I enchant and get experience my experience number goes back to the number before I enchanted (My guess is maybe after I enchant on the table it reverses and goes back to the time before I enchant, that might be why I get all my experience back after I kill like one mob).
This is also an issue for me when I play multiplayer. My sister (client) will get the same enchantments after enchanting an item, but if I open the enchantment table while shes already in it and place an item that I know has something like "Unbreaking III", her enchants will change to that item, thus allowing us to make many copies of books with that enchantment.
Her experience will also work as described above. she could be at lvl 30 and use up her xp repairing items, like down to lvl 4, but the next time she levels up her xp will go to lvl 31 instead of 5 as expected. the max XP level never gets reset if that makes sense.
I'm also seeing this behavior. Happened on 12.1 iOS iPad retina and air 2. Still occurring after update to 13 on newly generated world.
Is there any documentation I can provide that would help?
Happened to me on 0.13.1 (Win 10) while playing as a client connected to an android acting as local server- I have got 3x Diamond picks with Fortune 3 Unb 3 in a row now; the enchants are not resetting/changing.
Has anyone found a workaround for this at least? Very frustrating being stuck with the same enchantment options :/
Still an issue for local mulitplayer on 0.13.2.
Has anyone tested this out on 0.14.0 Bx yet?
Affects 0.14.0
Still affects 0.14.2
... And 0.14.3
... And 0.15.1
Still not fixed on 0.15.0
happening on my realm! I, the host, am stuck with the same enchantments, while my friends on my realm can gather new enchants after enchanting an object. I have 100 pickaxes with the same enchant

0.15.0 on iOS please fix!!!
This is happening in Realms, iOS9, 0.15.0, iPad - I am the host, the enchantments do not randomise.
Also, if I enchant things, using up experience, if I leave the Realm and log back in, my experience has magically returned
Realms, IOS9, 0.15.0, All IDevices, also Android client.
Enchants stuck for each item type: i.e. Books stuck on Respiration III, Picks stuck on another enchant, swords on another.
Attempted to circumvent by breaking and replacing enchanting table, moved bookshelves about, no change.
0.15.2... still an issue.
This is an issue in 0.15.3 for me in the realm I created (Android). I always get the same enchantment seed no matter how many times I enchant something.
Ugh. Still effects 0.15.4 for the Realms on there. As someone who is paying monthly to keep their realm alive, it seems to have a LOT of issues. My horses die when I get off of them. I can't enchant anything other than one particular enchantment on everything....
@HyperCamel, any chance of getting a fixversion on this?
Should this be a REALMS issue?
I'm in the same boat as Edward. I'm paying for a monthly subscription and the game is completely broken.
+1 I'm actually paying for 10 users that can't play properly
This really sucks, enchantments are a brilliant gameplay idea to speed up and enhance time-consuming gameplay bits - I'm stuck with slow digging, no Fortune to multiply ore extraction, can only get Silk Touch on iron picks. Really holding back my exploration of the Nether at higher difficulty levels.
As a temporary workaround, try placing torches in various patterns between the enchanting table and the bookshelves (thus blocking those bookshelves), this can enable you to get some different enchants.
Possible work around for some (but still sucks royally) and more info regarding bug:
On realms, this is is currently locking all users (including host) to a list of enchants specific to the user but potentially different from each other. For example: Pickaxes - I have Unbreaking III as the highest enchant. My wife plays on our realm and has Fortune I as the highest enchant. Again, this never changes regardless of how many enchants you do (we've done hundreds). However, we are able to get all the enchants we want by having the other people on our realm fulfill enchant requests for each other.
This is what we did:
1. Create an enchant chest for each player.
2. Put a sign above each chest with their name
3. Put another sign above that is the request sign, and the player can place their requests there.
4. Players fulfilling requests will enchant the item and then place it in the chest and take the sign down.
5. Logout and back in (utilize
REALMS-91) to get XP levels back.So long as
REALMS-91is an issue, this isn't too big of an inconvenience for other players. Hope that this is fixed before the XP bug! It makes it more bearable.Affects 0.15.7 This should be a high priority bug considering how important enchanting is to the gameplay
I have this problem in single player. I'm the host, obviously, with no one in the game. Not realms. Just local single player.
If this isn't fixed in the next release I'll be reluctantly cancelling my Realms subscription; it's pointless having a server that I cannot play properly on. I mean lets face it, not being able to get the full range of enchants does kind of put the dampers on things.
Unfortunately Mojang/Microsoft are unlikely to see much revenue impact from this bug (but bless you Dean for having principles) and since they perceive there to be a hack/workaround for this (see mod comments above) we're just going to have to wait until the competing bugs/features get done and this bubbles high enough on the backlog to get some attention.
Luckily, No Man's Sky has come out, and is scratching my sandbox game itch at the moment, although I wish you could build instead of just mine and explore.
Version 0.15.10 is out and still no fix for this. I will suspend my realms subscription. I'm very sorry because I have already a nice world in which I play with my daughter but, with this bug is really demotivating
I feel your pain Pedro.. I cancelled mine a week ago, it's a shame because I'd spent hundreds of hours on it and it's not even possible to back it up.
It's pointless playing 1/2 a game.
I'm about to cancel mine as well. Very frustrating but rather than get upset I will just be voting with my wallet. Oh well, maybe I will re-evaluate later if it gets fixed but I really wouldn't look forward to having to rebuild all I've already done. I /really/ wish Win10 could backup/upload PE realms worlds.
I read that with 0.16.0 we will be able to backup/upload realms. Supposedly to use addons you need to download your world, apply the addon, then upload it back to the realm? I wonder if loading the world locally would change the enchant seeds? Or, if some enterprising individual could figure out how to modify the save file to edit the seeds...
Do you have a link for that info?
If that´s true, those are good news. If they are working on realms, maybe the issue gets fixed. Let´s see.
It´s funny. The issue does not happen if I connect to the realm from Windows 10. So it must be client related.
Really?! I hadn't tried that yet. That's great news as it's at least a semi-workable workaround as long as logging in with the same xbox account gets my same character. Maybe I will reinstate my subscription...
Yes, try it and tell us if it worked for you
Can't find the original page I read, but the official Addons FAQ page implies it:
I will have to try with Windows 10 tonight... hmm
Aha - here it is. Confirmation of realm import/export from Minecon.
I can confirm that if I log into my realm from my windows 10 machine, I am offered different enchants. Upon enchanting an item, the enchants offered then change as they should!
HOWEVER, when I go back to my iPad, I am again offered the ORIGINAL enchants.
The real question is does win 10 have just a different-
but still fixed-set of enchantments? Or does it properly change?I have unsubscribed from the realm service due to this bug.
On win10, my available enchants did change after enchanting a book. They also change each time I enter the world.
It's odd - i'd expect this to all be controlled server-side and not to behave differently on different clients. Seems that the enchant seed is calculated client-side and that there is a bug on the iOS & android versions where that calculation always comes out the same for a given player.
Very strange then that they had like 5 different updates on mobile without fixing the bug. Sure doesn't seem like a complicated one, though of course it's hard to tell.
Let's all tweet at the developers so they take a look at this. They have probably just not hear of this bug so they haven't fixed it yet. Give them a link to this page- this is should be a high priority fix for them considering they are losing revenue
Please note that this bug has been reported to our internal bug tracker for further testing and a fix, and the developers are aware it. It is scheduled to be fixed in one of the future updates (no specific date can be provided). Additionally, post only NEW information regarding this bug. This is not a forum for discussion.