Join Our Discord! 0 MEMBERS ONLINE

How to get your base back if you lose it! (By accident).

Not open for further replies.


New Member
2021 Gold Founder
2022 Gold Founder
It is pretty easy to lose your base. Whether you tp out of it, delete the home, or just simply wandered in the wrong direction, it is easy to return to your base by scanning error reports!

The Red Text:
This is not a 100% guaranteed as a way to return to a lost base. Some clients do not index logs or outright delete them, making this method risky for individuals that play modded profiles. Most of what you are doing to find a lost base will be guesswork or trial-and-error, but if you have good recollection of the approximate location of where your base is, you can find it using error reports as a reference. If you lost your base to a non-player error, then congrats! You're in the wrong section and you should go make a ticket to have your base restored.

Regardless of how nice your setup is, which profile you use, or how you plan your bases, Minecraft creates a ton of errors while you play the game. For the most part, these errors are from a sound that forgot to play, a bit of lighting that just *didn't* happen, or an animation that didn't render. Errors recorded in your logs are on the client-side, and thus cannot be checked by the server (to the best of my knowledge, although this type of accident falls under "player error," so you probably wouldn't get anything from the admins anyways). These errors are indexed by your game's console, which starts running when you enter a world, and ceases when you leave the world. When you leave, the console log is placed in an editable text file called "Latest" before eventually being compressed when you next log in to a server or world.

How to recover your coordinates:
1. If you just accidentally lost the base, immediately disconnect from the server. Once you have fully disconnected to the main menu, exit out of your game. You want to minimize the extra steps in this process, and accidentally logging into a singleplayer world or another server adds extra steps.

2. Get some information. You're going to need the approximate time and general coordinates of your base. If you know that your base sits between 4500 and 5000 X, and -2000 and -3500 Y, and you were last in it at 18:30 (6:30PM), then you have a good reference for the scan.

3. Open up your ".minecraft" folder. This is found (on PC) by going to the search bar and typing "%appdata%" and then opening the folder. For Mac users, go into files, type "~/Library" into file locator, and open up the folder labeled "minecraft."

4. Navigate to the "logs" folder. It should be under "libraries," and above "mods." Once you're in this folder, find the "Latest" text file (it should be at the very bottom of the folder). If you open the file and see no chat information that is related to MCDrugs, then you have extra steps! You now have to open a compressed log file, which requires a file decompressing tool. I recommend using 7zip, but any others work perfectly fine. Navigate to the log with the current date (or the day you lost the base) (should be a .gz file), and then open it using the decompressing tool.

5. Use the text editor search tool to find any of the following strings: "[Render thread/WARN]" "Entity azu" "ClientLevel" "does not have attribute minecraft:generic.flying_speed" - There are many others, but the first three will open every console error that exists, so it works for a variety of client-side errors. If you can, try and find when you first set the home, as chances are there will be an error nearby alongside the "Created a new home: xyz!" which will better help you isolate the location.

6. Find the coordinate list associated with the error. It should be next to the "ClientLevel" string. From personal experience, errors record from the nearby chunks, so the coordinates will be nearby where your base is located, and you will either need to do a bit of digging besides the given location, or just hope you get really lucky.

7. Go find the coordinates! I would recommend making a copy of the log file you used (so you don't have to search for it later). At this point, you're going to walk or use an elytra to go to the approximate coordinates of your base. If you recognize surface things, then congrats! You have found it (probably). If you don't recognize anything, or you kept digging and didn't find a base, then you should probably go back and find a different set of coordinates to try!

8. Protect for the future. Set two homes if you have an unclaimed base, spawn a bunch of animals to rack up entity errors, or just write down the coordinates!

Extra Tips:
When you get to the error location, you're obviously not going to find your base if it was a bat in a hole or something. I would recommend mining in all directions (forward, backward, sideways, diagonal) for at least four chunks. It isn't going to be an instant find every time, and is often within reach of the coordinates you found.

Look for errors involving chests. If you can find render errors where a chest didn't open on time, or the sound got canceled out, you have a much better chance of finding the exact location of the base.

Check your world. When you play on MCD, you often will switch between the different worlds. If you are going to coordinates that sound right but have no familiarity or any results whatsoever (such as no caves), you might also be looking at coordinates in FarmA or FarmM.

If you have a good friend who has been in your base, cross-check error coordinates with them! You might be able to better figure out where your base actually is!

Once again, this method is not guaranteed as a way to recover a lost base. If you are trying for hours and not yielding anything, it's entirely possible that there are no errors that happened near your base, and it is not recoverable by this method.
Not open for further replies.

Latest posts

Members online