When throwing a trident into an unloaded chunk, even with loyalty is does not return and becomes impossible to take again once found.
Linked issues
Attachments
Comments 7
migrated
I was not able to reproduce this problem in 1.12.1 (Windows 10). I tried both an unenchanted trident and one enchanted with Loyalty III. I also tried in both Creative and Survival modes. I threw the trident 98 blocks with my simulation distance set to 4.
"Unloaded chunk" isn't really a concept in the Bedrock version. I assumed you meant the closest analog, which is an unticked chunk. The nearest unticked chunks to a player are at a distance of (simulation distance + 1) x 16 blocks, so I made sure to throw my tridents more than 80 blocks to get them to land in an "unloaded chunk".
It's possible that by "unloaded chunk" you meant a chunk that had never been generated. Most chunks are generated the first time you can see something in them, so if your render distance is set very low and/or intervening terrain blocks your view of where the trident landed, it could land inside a chunk that the game hasn't generated yet. I did my tests in a world where all the chunks over a large area had long since been generated, so this could explain why my results were different.
When you throw a trident into (or through) a chunk that hasn't been generated yet, I imagine the game should force that chunk to be generated, but it's quite plausible that there's a problem with this mechanism and it caused your problem. So to reproduce the problem, I would like to try it in a world more similar to yours. Please provide the following information:
The world seed
Your render distance setting
The simulation distance setting for your world
The coordinates you were standing at when you threw the trident. Be as accurate as you can, but it shouldn't matter if you're a block or two off.
The coordinates of the block the trident landed in.
This ticket will automatically reopen when you reply.
I was not able to reproduce this problem in 1.12.1 (Windows 10). I tried both an unenchanted trident and one enchanted with Loyalty III. I also tried in both Creative and Survival modes. I threw the trident 98 blocks with my simulation distance set to 4.
"Unloaded chunk" isn't really a concept in the Bedrock version. I assumed you meant the closest analog, which is an unticked chunk. The nearest unticked chunks to a player are at a distance of (simulation distance + 1) x 16 blocks, so I made sure to throw my tridents more than 80 blocks to get them to land in an "unloaded chunk".
It's possible that by "unloaded chunk" you meant a chunk that had never been generated. Most chunks are generated the first time you can see something in them, so if your render distance is set very low and/or intervening terrain blocks your view of where the trident landed, it could land inside a chunk that the game hasn't generated yet. I did my tests in a world where all the chunks over a large area had long since been generated, so this could explain why my results were different.
When you throw a trident into (or through) a chunk that hasn't been generated yet, I imagine the game should force that chunk to be generated, but it's quite plausible that there's a problem with this mechanism and it caused your problem. So to reproduce the problem, I would like to try it in a world more similar to yours. Please provide the following information:
The world seed
Your render distance setting
The simulation distance setting for your world
The coordinates you were standing at when you threw the trident. Be as accurate as you can, but it shouldn't matter if you're a block or two off.
The coordinates of the block the trident landed in.
This ticket will automatically reopen when you reply.
Cleaning up old tickets: This ticket had been set to 'Awaiting Response', but has not received a response from the reporter (~3 months+) so is being closed as Cannot Reproduce. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines which includes steps to reproduce the problem.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
Cleaning up old tickets: This ticket had been set to 'Awaiting Response', but has not received a response from the reporter (~3 months+) so is being closed as Cannot Reproduce. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines which includes steps to reproduce the problem.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
This issue is now tracked at MCPE-73193.
This issue is now tracked at MCPE-73193.