Don't close as a duplicate nor merge

The 2024 question is distinct from the 2017 question and shouldn't be closed as a duplicate or merged.

According to tuskiomi, the OP of the 2024 question, their post has specific criteria that set it apart from the 2017 question:

If you look at the accepted answer for the linked [2017] question, you will see that none of the answers, including the accepted answer fit the criteria listed in my short description. That is enough on the face for a sufficient distinction.

They further clarified:

I think there's a bit of technicality that I may have not put an emphasis on in my 2024 question. I'll make the technical requirement more clear. it has to do with "All blocks should be accessible in survival at all times.", which is a veiled multiplayer requirement. I've added this to the question. It doesn't change any of the existing answer that are on it currently.

This aligns with a previous meta discussion: Is a question a duplicate just because it asks for something that can be part of another question's answer? That discussion concluded that more specific questions shouldn't be considered duplicates of broader ones, even if their answers could overlap. Since the 2024 question is more specific, it shouldn't be closed as a duplicate nor merged with the more general 2017 question.

Regarding the issue of the wrong accepted answer on the 2017 question, we don't close questions because the OP accepted an incorrect answer. This should be treated like any other wrong answer: downvote it, leave a comment explaining why it's incorrect, and add the correct answer if it hasn't been provided already.