Guardians are spawned in random places
Guardians are spawned in an ocean where there is no ocean monument. The place is illuminated by Jack'o Lanterns. The chunks were generated in 1.7.9.
Environment
OS: Windows 8.1; Java version: 1.7.0_55-b13; using a Minecraft server
Linked Issues
is duplicated by5
Created Issue:
Guardians are spawned in random places
Guardians are spawned in an ocean where there is no ocean monument. The place is illuminated by Jack'o Lanterns. The chunks were generated in 1.7.9.
Environment
OS: Windows 8.1; Java version: 1.7.0_55-b13; using a Minecraft server
is duplicated by
is duplicated by
is duplicated by
is duplicated by
relates to
is duplicated by
relates to
is duplicated by
is duplicated by
A comment with security level 'global-moderators' was removed.
A comment with security level 'global-moderators' was removed.
Dupe of MC-65214
Dupe of MC-65214
Hm, I went to another Stronghold, also under the sea, to check if this happened there too, but no guardians spawning there. Therefore, it does seem like a dupe of MC-65214 as Sonic has pointed out... I'll try generating the world with the same seed to check if a temple is genned on the coordinates.
A chunk or chunks very near my oceanfront base started spawning guardians suddenly. My last backup on Oct 2nd does not spawn guardians in this area, but my live version started doing so Oct 5th.
I created a new creative world using the same seed, tp'd to the location and it does not spawn guardians (nor is there an ocean monument)
Possible duplicate with MC-65214 though I am not loading old area created before guardians were added. Also I appear to have the Guardian Sound bug (MC-57057)
Seed: -6501567322576795968
World created in version 14w30c
Current version is 1.8 (upgraded automatically by launcher when released)
This issue is a duplicate of MC-65214. It has been linked to the original bugreport.
Please search before reporting any bugs, as it's likely that one exists already.
Thanks Mustek. I did search and quoted the (possible) duplicate in my submission. MC-65214 seems to be instances of guardians spawning "randomly", but were in worlds created prior to guardians being introduced. In these cases the chunks update to spawn guardians even though an underwater monument is not created by the game.
However in my case since a) the world was created after guardians were introduced, and b) the same chunks did not spawn guardians a few days previously I judged it a sufficiently different different bug. Apologies if we disagree on the matter.
Dupe of MC-65214
Dupe of MC-65214


Please provide the seed and the coordinates.
Seed: -1079477294021365449
Coordinates: -280 43 295
Are these chunks pre-14w25a?Try re-creating this world and /tp yourself to that, and see if there's a water temple.
Works as intended, there's a water temple there if it was in 14w25a+ but since it's not it shows no temple, but usually there would be.
I've tried it and there is nothing, it's simply an ocean.
There isn't a water temple if you generate it after 14w25a. So it's a bug.
Issue exists on my 1.8 server, chunks were originally generated in 1.7.9.
Seed: 26551365887039689
Coords: -333 32 -225
If seed is used in 1.8, a temple is present.
Although the Wiki says, "Ocean Monuments can spawn in existing chunks from older versions of Minecraft," it appears they do not, and only the Guardians spawn.
In my current world save, no monument spawned in an area I had previously explored, but I did find Guardians. So I loaded an older backup, in which that same area had not been previously explored, and found a monument.
It appears that monuments will NOT spawn in existing chunks, but the Guardians still do.
I encountered a similar problem. The Guardians are spawning in a River. But the World is generated in 1.8 and Amplified. When I try the same seed in a normal enviroment its still a river and no ocean nearby. (Seed: -4325619651631213966, coords: -319,y,291)
I encountered a similar problem. I created a new Single-player, Survival game on 1.8.1. I walked to a nice beach-y area, where I built my base and did all the playing. After a while, I started hearing strange noises which I couldn't identify (I hadn't been near Guardians yet). When I walked to the ocean the other day, I saw some guardians close to the surface. Because I couldn't see any monument around, I used "open to lan" in order to enable cheats, and flew there in creative mode, using a night vision potion to watch the water properly, and indeed there is no monument where I am standing, only a huge number of guardian mobs that immediately respawn if I use a /kill command.
The seed is 4354401103591561127. Coords are 301,74,-271. The save was created already on 1.8.1 and hasn't gone through any upgrade.
EDIT: I recreated the world in creative mode and teleported to the provided coords, and I can confirm that I do not see any monument, nor Guardians, in the area.
I don't know if this will be of use, but I used mcedit to make a copy of the save where only the affected area remains. I modified the spawn point and the player position to be close to the area where I have the issue.
Here is the link to the save: https://dl.dropboxusercontent.com/u/743491/Bug-Guardians.7z
@ David Quintana same situation, there are so many of them.
The issue lies in that the server is calculating DEEP_BIOME based on the 1.8 World Generator and NOT the worlds ACTUAL biome from previous versions.
I had a report of a biome in OCEAN (Not Deep), and when I generated a 1.8 world with exact same seed, sure enough that location was DEEP_OCEAN in that seed.
The Monument Structure check uses 2 different Biome lookup methods, and the one that does DEEP_BIOME check uses the World Gen calculations, and then the followup check for "Surrounding biomes" uses the actual worlds data.
I temp fixed for my server with the following change:
This issue has more flaws than this report states as it also causes monuments to spawn in the middle of Rivers, Frozen Rivers and Frozen Oceans, which is quite odd to stroll through the mountains and find a monument.
Like explain here : http://www.reddit.com/r/Minecraft/comments/2fco1f/is_it_possible_to_meet_guardians_without_an_ocean/
I have the same problem !
Happens in 1.8.8
Lets test with this code then
Happening in 15w46a. I didn't make a new world yet but the chunks they are spawning in were created before the bug started.
reaverofdarknes1 the fix only applies to newly generated chunks. Any created before 1.7, and visited during 1.8 with the bug will forever be marked as a water temple.
It just stops NEW cases of the bug.
A new world would not have this bug to begin with. It applies to pre 1.8 chunks being visited on 1.8+ worldgen.
But these chunks were spawned in 1.9 and initially they were not generating guardians. They have never been in 1.8.
edit: never mind, I see my mistake. Snapshots aren't really 1.9 in all regards.
Happening in 1.10.2 vanilla amplified. Prior to updating, when still in 1.9, no guardians in the ocean around my island. Since I updated to 1.10, there are two "ocean monuments" around my island, without the structures, but guardians spawn.
Please attach the world in its state before updating to 1.10.2.
Here's a world download. The guardians are spawning south-east of -1000x -240z. There were none before updating to 1.10. The world is amplified. http://bit.ly/29olW5v
Reopened pending further testing.
Is this still an issue in the most recent versions (currently that is 1.10.2, or 16w43a) of Minecraft? If so, please update the affected versions and help us keeping this ticket updated from time to time. If you are the owner/reporter of this ticket, you can modify the affected version(s) yourself.
It still is for me, in 1.10.2, in my LP world. I already attached a world download as it was in its state before updating to 1.10.2 in a previous comment.
with the nature of the bug, any chunk that loaded with the bug will be permanently 'bugged'.
The fix only applies to future chunk loads.
I gave Grum the fix to this bug, and it's still in place in 1.10.2.
To clarify more, the code says "is this block a monument" during structure generation.
These chunks loaded, and saved into the monument data file that there is a monument at that location when the logic for determining monuments was broken.
you would have to some how 'unprepare' the structures for that area and make it reprocess, which is not possible with vanilla tools/commands.
You mean that already generated chunks should be fixed ? That whould be quite complicated.
No, already generated chunks are near impossible to 'fix', as the game incorrectly registered a structure into the structure data files.
That code is only ran on the chunks first generation, which the previous code had faulty determination logic for.
That data has been saved to the file, and the only way to stop the spawns now is to delete the data marking that area as a monument.
Deleting the chunk/region isn't even enough to do that, as the data for structures is stored in 1 shared file.
I don't think the devs can realistically fix existing worlds that had monuments registered to the wrong location. But the problem that caused it to happen was fixed.
I created my world in 1.8 though, when the ocean monuments already existed.
I know that 1.10.2 is already in the list, but this is to add data and the high probability it is happening in 1.11.2. My world was created in 1.9.4 just before the release of 1.10. I did not explore this area until 1.10.2. At that time I do not remember hearing sounds and or seeing subtitles of guardians in that area. Since I was looking for a monument, I don't think I would have ignored it. I did not play after that until 1.11.2 as family event took priority. Just before the release of 1.12, I went that direction again and started hearing and seeing the guardian info. Checked and I now have guardians with no monument. I loaded the seed in 1.94, 1.10.2 and 1.12 and did not find the same situation. I use a copy of this world and a separate save folder to play snapshots, but cannot find any of the old saves to know just when this happened.
Is this still a issue in the latest version of the game(currently 1.13.1)?
If so, please add it to the affected versions, thanks!
@Urielsalis it is resolved in 1.13 at least. Likely was on 1.12 too as I don't recall dropping this fix in 1.13, we must of dropped it 1 or 2 versions ago.