Killing raid captains spawned by a raid (ones with banners on their heads, not limited to just pillagers but vindicators and evokers as well) add more levels of bad omen, creating an infinite raid. I would take a picture but I am being instantly killed upon respawning (315 entities being loaded concurrently according to F3, normally somewhere just above 100 for my world, this includes my items and exp from death). Please fix this, it is of high priority for anyone wanting to start a raid.
Attachments
Comments 8
I added a screenshot but the zipped world save is too large to attach. Any suggestions on how to send that over?
@William Lee Do you have enough storage space on some file storage service (Dropbox, Google Drive, iCloud, etc) to upload the world there and post a link in this bug report?
Also, I failed to reproduce this issue in a creative singleplayer world. The raid captains I killed during a raid did not give me Bad Omen.
You can provide a copy of your world by uploading it to a service such as google drive, dropbox, etc... and then providing the link here. Please could you do this as this is needed to further investigate this issue? Thanks a bunch 😃
This issue is still there. I don't have the ability to do a video for this in the next days, but the well known YouTuber eckosoldier showed in his video a raid farm and you can see that the effect was obtained again, while killing raid entities.
Video: https://youtu.be/C9fQLuvm62g
At minute 6:40 - 6:50
This report is currently missing crucial information. Please take a look at the other comments to find out what we are looking for.
If you added the required information and a moderator sees your comment, they will reopen and update the report. However, if you think your update to this report has been overlooked or you want to make sure that this report is reopened, you can contact the Mojira staff on Discord or Reddit.
-- I am a bot. This action was performed automatically! If you think it was incorrect, please notify us on Discord or Reddit
Please try and provide some screenshots and/or videos of this issue occurring whilst the F3 debug screen is enabled.