Torabi
Assigned
Reported
Comments
Are you able to find the folder with your worlds in it on your hard drive? If you point at the profile in the installations tab in the launcher, there should be a button to edit that profile. On the screen that pops up, there's an option for "Game Directory". It should match the location on your hard drive that contains the "save" folder where your worlds are located. If it says "<Use default directory>", then it's looking in the .minecraft folder.
Mods typically have to be updated for each version of Minecraft. If you have worlds that depend on particular mods, they will likely not open until Forge and those mods have updated, and you install the appropriate versions.
However, the problem in this case is likely that you're not signing in with the correct account. You need to select the Mojang Login and use your old Mojang account. Migration is not yet available, so signing in with a Microsoft account isn't going to give you access to Minecraft.
It is possible that by signing in with the wrong account, something got changed in the launcher profile you're using, so that even when you do sign in with the correct account, it's not pointing to the correct folder with all your worlds in it, and is just displaying the demo world that was generated when you signed into the wrong account. I suggest you either edit the profile and ensure that it is pointing to the correct folder, or try creating a new profile.
Your images show the "Bedrock Edition" of Minecraft, but you've posted on the "Java Edition" bug tracker. That's why your report was resolved as "Invalid".
Did you have access to these worlds before? Was there a specific event that caused them to become locked, such as updating either the device or the game?
The worlds are locked because the game doesn't think you have the appropriate licenses active for content in those worlds. Either you're not logged into the correct account, it's unable to connect, or there's something wrong with your account. The people on the Community Support Discord may be able to help you figure out what's wrong, and help you fix the problem, but most likely, you'll have to contact the official Mojang Customer Support to fix your account so that your purchases are recognized.
@unknown marked MC-66068, which this report is resolved as a duplicate of, as Works as Intended. Any new reports would also be resolved as duplicates of MC-66068. The bug tracker is simply not the correct avenue to convince Mojang to change this, and I would recommend pursuing other means of building support for such a change, such as the feedback site or the suggestions subreddit.
You've already explained that the behavior makes sense as is, so why are you expecting it to be different? The used stat tracks the number of beds placed, the slept stat tracks the number of times you've slept in a bed. There is no stat that tracks setting your spawn point, whether you use a bed to do it or not.
@unknown, my comment was in response to the claims that this wasn't a bug. As for why it's been postponed, the reason is much the same as why it's been in the game for so long. The player movement code is ancient and ugly. Most of the bugs related to it would be difficult to fix, and there's a considerable risk that attempting to do so would introduce new bugs. It would be safer, cleaner, and easier to overhaul that section of code completely than to make changes to it, and thus most bugs related to it will probably be postponed until they can fit it into their development schedule.
Presumably, zombies do not bear children, and baby zombies are instead the result of infection. Whether or not the player can breed the mobs is irrelevant – the question is how the babies are produced.
Duplicate issues are not a good way of getting the attention of the devs. They rely on our volunteer moderation team to collect all the relevant information about an issue in one place, so that they don't have to search through dozens or hundreds of issues themselves trying to find useful information. "Whitespace" isn't free – clutter drowns out important information, and when the devs turn to the bug tracker looking for bugs to fix, they want that information as efficiently as possible, so they don't have to waste time digging through low-quality reports, and can spend as much time as possible improving the game.
This report is about a symptom of multiple other bugs, and is not a bug in and of itself. Given the nature of the issue, these bugs are most likely hiding in some of the deepest, ugliest code in the game. They're fully aware that the whole entity tracking system is awful, and needs to be overhauled or replaced entirely. However, this is a significant and difficult undertaking, and not something that can be done in an afternoon. They have to plan these things out and fit them into the larger schedule.
This issue is still open, and will be fixed in some future update. The suggestion to use a datapack is a workaround that the user can implement themselves, rather than wait for it to be fixed officially.
Nothing in those logs indicates that there's a problem. If the game is crashing, then there should be a crash report in the "crash-reports" folder in your Minecraft profile. What exactly are you seeing occur?
You haven't updated the issue for the past three years, and your last activity on the tracker was in december, nine months ago. The fact that you created the issue is still listed in the issue history, and the reporter field just allows regular users to update the issue directly, rather than leaving a comment for someone else to take care of it. Unfortunately, the JIRA software the tracker runs on does not allow for multiple users to have edit permissions on a single issue, without having those permissions across entire projects, like our helpers and mods do.
We have an internal selection process for bringing on new helpers and mods, and consider not only how active a user is, but the quality and tone of their interactions with the tracker and other users. We like to watch a user over a period of time, to see how well they understand the tracker and the community, before we consider offering them additional roles.
As far as I'm aware, persistent mobs are not supposed to count towards the mob cap. The ocean spawning rules seem to have a few bugs that have become consequential now that there are more water mobs than just squid.
I've updated the attached resource pack so that it will stop complaining about being out of date.
"Resolved" does not mean fixed. It means that a decision has been made on your report, and in this case, it's that the bug has already been reported, and your report has been marked as a duplicate of MC-52974, which is still unresolved. Once the bug has been fixed, MC-52974 will be "resolved" as "fixed".
Duplicate of MC-5694 – If you searched the tracker before creating this report, and were unable to find the indicated ticket, please comment with the keywords you searched for so that the original report can be improved.
My brand new keyboard has a "broken bar" rather than a "pipe". In fact, I don't know that I've ever seen a "pipe" character – I've always seen a "broken bar", in every program, font, or operating system I've ever used.