[MC-192024] Forgive dead players not working

Zombie piglins will still attack you after death, despite the game rule forgiveDeadPlayers set to true.

I have a 25.44 MB video but cannot upload due to maximum file size limit set by administrator

Attachments

Comments 19

galaxy_2alex 2020-06-26T10:43:06Z

Please upload the video on a third party hosting website and provide the link. Also, please make sure that you do not have any datapack or command block setting it back to false constantly.

John Lucas 2020-06-26T20:43:32Z

https://youtu.be/ZM64qziWvnk
also this is survival mode with me and my 1 friend so I know we have no data packs or command blocks

galaxy_2alex 2020-07-02T00:38:09Z

Please provide a screenshot while you are on the server with your F3 debug screen enabled.

Nick Bastin 2020-07-02T22:38:09Z

I'm not sure why "awaiting response" is "resolved", that completely screws up people who are searching for the same issues such that you can't aggregate them properly, plus it's flat out rude.

We are having the exact same problem as shown in this ticket - Zombified Piglins will attack you forever regardless of the status of the gamerule. UniversalAnger seems to work properly, but this is almost worse because it means there's no incentive for people to clean up angry pigmen, and the new anger spreading almost always means that new pigmen have spawned when you're trying to deal with the old ones, making an endless stream of hell that can only be resolved if you manage to despawn them without unloading the chunk.

galaxy_2alex 2020-07-02T23:41:54Z

@Nick: It is always good practice to not only look for resolved reports. We are still waiting for vital information about this report, and so far have not gotten it - so if you can reproduce it, please provide a screenshot while you are on the server with your F3 debug screen enabled.

9 more comments

Nick Bastin 2020-07-02T23:57:10Z

If you are "awaiting response", the status is NOT RESOLVED. You are obviously waiting for something. If you would like someone to respond, it would help if you wouldn't also tell them that their ticket is resolved.

Nick Bastin 2020-07-03T00:01:53Z

The server is vanilla 1.16.1, the client is vanilla 1.16.1. I'm not sure what other "vital" information you could need. You do understand that by nature of the problem in this report, capturing it with a screenshot at all is non-trivial? (Since you'll be, well, getting your face smashed in while you try to take it). There's nothing in F3 other than this information that is relevant to this ticket.

Chandler 2020-07-03T00:03:57Z

The status of Awaiting Response has to be Resolved for ticket reporters that don't update their tickets. If the "awaiting response" resolution is Unresolved, then we would have a bunch of tickets that are unresolved without an active reporter to add the needed info. Awaiting Response is also considered Resolved because nothing else can be done on the issue until the info is added. If the reporter actually cared about their ticket, they would be paying attention to it and would be worried when it was resolved and add the info.

Nick Bastin 2020-07-03T00:10:09Z

Then the bot should set "Awaiting Response" to resolved after an appropriate amount of time (which I think it actually does). Setting it to resolved immediately ends up in an offensive feedback loop where people don't find tickets, report new ones, and then get dumped on for filing duplicates and not searching. I have no problem with asking for a response and then dumping the ticket after a few days as a policy. Setting a ticket to "Awaiting Response" and then setting it to "Resolved" immediately is nonsensical - it's obviously not resolved, since someone asked for more information.

Chandler 2020-07-03T00:17:51Z

Usually people don't even search for issues before reporting them. If you are searching though, you definitely should be looking through resolved reports because the issue you are reporting could have been already reported, and then resolved as Works as Intended or Won't Fix. Those issues are Resolved and won't show up if you search for only unresolved issues. And you could potentially create duplicates of those.

Nick Bastin 2020-07-03T00:22:48Z

You understand that the set of "resolved" reports in this tracker is more than 100k items, even when restricting to a single project? Sure, you can search for "resolved" and "won't fix" or "works as intended", and indeed I do, but there is no way a reasonable person thinks that they need to search for "resolved" and "awaiting response". Those are mutually exclulsive states.

Chandler 2020-07-03T00:25:54Z

I doubt this will be changed at all, even if that is your opinion. The best you can do is start searching for awaiting response as well as the other things in you search terms

thistriagonalsign 2020-07-03T03:44:55Z

@Nick Bastin I don't think they were asking you to take a screenshot with the F3 screen up while the bug was happening. I think they just wanted a screenshot with the F3 screen up in the server that you've encountered the bug on. Hope that helps.

John Lucas 2020-07-03T05:21:32Z

I uploaded the f3 screen

galaxy_2alex 2020-07-03T11:55:28Z

@unknown: This is a bug tracker, not a discussion forum, that is what we have Discord and Reddit for (see below).

@unknown: Are you absolutely certain that there is no datapack or command block constantly resetting the gamerule?

Quick Links:
📓 Issue Guidelines – 🛠 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
💬 Mojira Subreddit – 💬 Mojira Discord

John Lucas 2020-07-03T17:09:36Z

@unknown yes, I run the server that me and my friend play on, we dont have any datapacks or command blocks constantly setting the gamerule to false

galaxy_2alex 2020-07-03T20:09:48Z

Thank you for your report!
However, this issue has been temporarily closed as Awaiting Response - this does not mean the report is not valid, we just need more information to verify it.

While the lag occurs, please run /debug start, wait a while and then run /debug stop in order to create a debug profile. Afterwards, run /debug report.

If you do not have the permission to run these commands, open your world to LAN and enable cheats. If you're on a server, make sure that you're a server operator in order to execute these commands.

Then, please attach the profile results found in [minecraft/debug/profile-results-<DATE>.txt|https://minecrafthopper.net/help/guides/finding-minecraft-data-folder], as well as the debug report found in [minecraft/debug/debug-report-<DATE>.zip|https://minecrafthopper.net/help/guides/finding-minecraft-data-folder] here.

Quick Links:
📓 Issue Guidelines – 🛠 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
💬 Mojira Subreddit – 💬 Mojira Discord

Joe Thomas Piccolo 2020-07-11T03:12:38Z

I'm having the same issue in a nether only survival world. The first time i died to angry zombie pigmen they forgave after i respawned, 2nd time after though and they just stick to being hostile after death. only once i wipe them out (usually by setting the difficulty to peaceful for a second cause i'm tired of this bug) will they actually not be hostile. i've tried changing the gamerule to false and then back to true, but that didn't do anything. for reference, its an offline world, cheats are on, (so i could get to the nether at the start), and everything else about the world is unchanged. it was created a few days ago and has been optimized in the edit menu, but i dont think that matters.

Brevort 2021-03-03T14:55:48Z

I had the same issue yesterday in the snapshots. I died several times to the zombie pigmen and they kept picking up my armor, so I had to keep killing them. One time when I respawned, they killed me without aggroing them first. I was recording when it happened, but I'll have to edit the footage down because it is quite long. Will this video be sufficient or will reopening this bug require more information?

My world is survival mode, 100% vanilla without cheats, no data packs or command blocks, etc. It is hard difficulty, but not locked, but I have not switched it off hard since my first few nights in the world. Now I am >400 days in. Also 100% singleplayer, never opened to LAN.

I've rewatched the video and realized that I cut most of it out of the video, but I still have them chasing me, but it's not clear that I haven't already aggroed them.