Hello,
I have quite a few aquariums set up in my Windows 10 Bedrock Edition survival world. Axolotls are cool and always will be, but I was beyond enraged at this. It took me a lot of time and hard work trapping a guardian, getting it into my boat, and into my island's prismarine aquarium... the guardian was named and everything. The same thing happened with my named squid and named glowsquid (at first i thought they were despawning then I saw this). Now I'm scared to have any aquarium at all, if an axolotl spawns inside, it will kill whatever else is in there with it. The official Minecraft Wiki (https://minecraft.fandom.com/wiki/Axolotl#Spawning) states:
"Adult axolotls spawn naturally in groups of 1-4 on any water with blocks above it below y: 63, typically in caves. This includes bubble columns.
After the world generation, axolotls spawn individually in total darkness and where there is a block with base_stone_overworld
tag (i.e. stone, deepslate, andesite, diorite, granite or tuff) less than 5 blocks below the spawning space."
Every aquarium in my world is well-lit and doesn't have any exposed natural stone inside! It takes hard work and is time consuming capturing the ocean mobs and getting nametags. I'm reluctant to try capturing more fish, guardians and squids and naming them with nametags knowing an axolotl can spawn inside the tank and kill them all over again. It's really hurting the progress of my summer build project in my survival world. Please fix this ASAP Mojang!!! I know a lot of players who love building aquariums. Imagine having an aquarium full of beautiful ocean mobs for years in your survival world just for some wild axolotl to spawn in and kill them all.
Thanks.
Linked issues
Attachments
Comments 3
I'd consider this to be a duplicate of MCPE-130635, since MC-222302 mentions that axolotls can spawn everywhere in water where it's dark.
Thank you for your report!
We're tracking this issue in MCPE-130635, so this ticket is being resolved and linked as a duplicate.
That ticket has already been resolved as working as intended, which means this is not considered a bug and won't be fixed. Please do not leave a comment on the linked ticket.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
-- I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
The requirement for total darkness is included in 1.17.10.22 beta. It will likely be in the 1.17.10 update, but there is no guarantee of that. Note that the wiki is not an official source for game behavior.