mojira.dev
MCPE-46182

We're being attacked! achievement unattainable on Realm, Xbox One + Win 10

This is occuring on a realm!  I heard other players saying they can unlock the achievement by playing as the host in a single-player world.  We CAN NOT unlock this achievement in my realm!  You can watch the video for proof!  Thank you!

 

8/28/2019

I attempted my 8th or 9th try today to unlock these achievements. It is STILL not working!... This bug report is almost 6 months old... I haven't recieved a reply for this bug report, and it has not been fixed!

------------------------------------------------------------------------------------

This affects both Xbox One and Windows 10!

I just tried my third attempt today. Got Bad Omen, went to a village, triggered a raid, rang the bell 50 times during the raid and with tons of mobs in the village. Clearly not working. It would be nice if they would still give bugs comments like they used to!

Can you guys please respond to this?

Achievement that is broken/cannot be achieved:

 

-We're being attacked!

The first time I tried to complete this, I used my own man-made village.  Since I did not get the achievement from that raid, I tried again using a naturally generated village.  It had the same results.

I can not unlock the achievement! I have attempted this more than 10 times.

I recorded the whole event on my second attempt, so the video is a bit lengthy, and you can see step-by-step what I did... I'm pretty sure this is a bug.  I've tried it x times and they are still locked!..

This world, I have earned all achievements except these 2, and you will know they are enabled on the world!

Video: https://www.twitch.tv/videos/423571533

Related issues

Comments

migrated

Can you guys look at this? Please watch the video I posted, You can see how I got bad omen, triggered a raid, rang the bell 20+ times, and never got the achievements.  The world I'm using, I have earned every achievement in the game except these two, so they are enabled. I also did this two tries already with a man-made village and a naturally-generated village. Please help!

Jonathan5733

Cannot Reproduce on any device. Unlocked both achievements on all my devices.

migrated

Got multiple videos as proof... on my 10th try... I heard others are confirming this also...

Auldrick

You removed the South the Alarm achievement, which you had originally reported as well as We're Being Attacked. What happened? Did it suddenly decide to work for you, or did you figure out you'd been doing somethng wrong? (In your video it looks like you were ringing the bell quite often, but it only counts when there's a pillager in the village, and I can't tell where the village boundaries are just from the video. If any beds or workstations have been added or moved, the boundaries might not include all the houses we can see, or they might extend far beyond the houses; you just can't tell easily.)

I can't think of any reason why you wouldn't get the We're Being Attacked achievement, unless the world was already disabled for achievements, but you'd be able to see that on the game settings screen. So I'll pass this along for reporting to the developers.

[Mojang] Mega_Spud (Jay)

Thank you for your report!
We're actually already tracking this issue at MCPE-45060, so we will resolve and link this ticket as a duplicate.

If you would like to add a vote and any extra information to the main ticket it would be appreciated.

If you haven't already, you might like to make use of the search feature, to see if the issue has already been mentioned.

Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki

migrated

Auldrick… We discovered sound the alarm could not be achieved during a pillager raid... Like in the video provided, we tried ringing the bell during a pillager raid each time.  - Once we rang the bell without a pillager raid, we got the achievement!  As I stated in the bug report, "This world, I have earned all achievements except these 2, and you will know they are enabled on the world!" Achievements are not disabled..

Auldrick

Ok, you've given me a clue to another possible cause of the problem. It's possible that the bell you were ringing was not in the village at the time you were ringing it. The way the game defines where the village boundaries are is different from how players do it. The game defines it based on the locations of bells, beds, and workstations that the villagers are aware of, but during a raid the villagers go to their homes (beds), and if they were all too far from the bell to detect it and that situation persisted for long enough, the game would eventually drop the bell from the village inventory and shift the village boundaries. That would mean the bell you were ringing was not in the village any more, by the game's definition. After the raid was over and the villagers came back out, they might have wandered close enough to the bell to add it back to the village again, so you could ring it to fulfill the conditions for the achievement.

migrated

That is a good suggestion Auldrick, but I was aware of all those parameters well-before trying to earn the achievement... The bell in the video I believe was centrally close to the village, in fact just a couple blocks from a villagers house... What might not be shown in the video, is that we tried moving the bell, removing-and replacing single and multiple bells, and many other things to make the bell "valid."  We tried basically everything...  Including using different villages and different circumstances... There are two things I can confirm:  1.  The achievement could not be earned by ringing the bell during a pillager raid.  2.  Ringing that EXACT same bell, without a pillager raid, (and a zombie inside the village instead) successfully earned the achievement!

Auldrick

I strongly encourage you to add the findings in your last comment to MCPE-45060. Without repro steps, hints like this can be very helpful to the developers.

Incidentally, now that you've earned the achievement you can't experiment with the bug any more. We on the bug tracker have the same problem when it comes to achievement bugs: Either we've already earned the achievement and can't test it at all, or we only get one chance to test it because if we guess wrong about what causes it, we'll trigger the achievement and then can't try something different.

migrated

(Unassigned)

Plausible

Xbox

1.11.2

Retrieved