I recently updated my server from 1.19.2 to 1.19.3. Whenever I start the server, I get these messages after the spawn area is loaded:
[13:19:01] [Server thread/ERROR]: No key selector in MapLike[{event_delay:0,event_distance:0.0f,range:8,source:{pos:[I;-9,-43,255],type:"minecraft:block"]}}[13:19:01] [Server thread/ERROR]: No key selector in MapLike[{event_delay:0,event_distance:0.0f,range:8,source:{pos:[I;-9,-39,252],type:"minecraft:block"]}}[13:19:01] [Server thread/ERROR]: No key selector in MapLike[{event_delay:0,event_distance:0.0f,range:8,source:{pos:[I;-9,-42,253],type:"minecraft:block"]}}[13:19:01] [Server thread/ERROR]: No key selector in MapLike[{event_delay:0,event_distance:0.0f,range:8,source:{pos:[I;-8,-40,252],type:"minecraft:block"]}}[13:19:01] [Server thread/ERROR]: No key selector in MapLike[{event_delay:0,event_distance:0.0f,range:8,source:{pos:[I;-10,-39,255],type:"minecraft:block"]}}[13:19:01] [Server thread/ERROR]: No key selector in MapLike[{event_delay:0,event_distance:7.873975f,range:8,source:{pos:[I;-72,-45,270],type:"minecraft:block"]}}[13:19:01] [Server thread/ERROR]: No key selector in MapLike[{event_delay:0,event_distance:0.0f,range:8,source:{pos:[I;-74,-46,260],type:"minecraft:block"]}}[13:19:01] [Server thread/ERROR]: No key selector in MapLike[{event_delay:0,event_distance:0.0f,range:8,source:{pos:[I;-73,-47,258],type:"minecraft:block"]}}[13:19:01] [Server thread/ERROR]: No key selector in MapLike[{event_delay:0,event_distance:0.0f,range:8,source:{pos:[I;-73,-47,262],type:"minecraft:block"]}}[13:19:01] [Server thread/ERROR]: No key selector in MapLike[{event_delay:0,event_distance:0.0f,range:8,source:{pos:[I;-10,-38,260],type:"minecraft:block"]}}[13:19:01] [Server thread/ERROR]: No key selector in MapLike[{event_delay:0,event_distance:6.067549f,range:8,source:{pos:[I;-12,-39,267],type:"minecraft:block"]}}[13:19:01] [Server thread/ERROR]: No key selector in MapLike[{event_delay:0,event_distance:0.0f,range:8,source:{pos:[I;-15,-38,258],type:"minecraft:block"]}}
This doesn't crash the server, it just prints these lines during startup and while running the server.
Linked issues
is duplicated by 1
Attachments
Comments 11
We do not have enough information to find the cause of this issue.
Please attach the affected (zipped) world file. If the file size is too large, please upload it somewhere else and then link to it here.
This issue is being temporarily closed as Awaiting Response. Once the requested information has been delivered, the report will be reopened automatically.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
I have found that over time this occurs less and less. I recreated the world without the datapack I was using and updated it from 1.19.2 to 1.19.3 in the same way and it gave no errors. I have determined that it is something that the datapack is causing, but as I said the long people are on the server the less it has happened. Restarting the server occasionally also helps.
I have been getting this issue as well. It exists on fresh vanilla worlds created on 1.19.2 that are updated to 1.19.3.
To replicate the issue:
Make a new server using minecraft_server.1.19.2.jar
Log into the server and walk around for a bit (not sure if this is necessary)
Save and stop the server
Run minecraft_server.1.19.3.jar in the same folder
Log into the server and walk around
There are sculk sensors at the reported block locations. The server seems to correct the block, so that the error is not reported again at this location. These messages are only displayed for chunks with sculk sensors generated in 1.19.2. All newly generated chunks with version 1.19.3 do not cause any error messages.
How is this "resolved"? I see it's been marked as such by "[Mojang] Moesh" with "Won't Fix" but with no comment or explanation. I am also getting this on my server since upgrade to 1.19.3 and the server lags badly for about a minute when it happens. Even if this only happens once per chunk generated pre 1.19.3, isn't this still a bug and worth resolving by actually fixing the bug?
My understanding is that it was a bug with skulk sensors generated in 1.19.2. I assume the bug has already been fixed in 1.19.3 and that these error messages are indicating that this and future versions are correcting the bugged skulk sensors.
Can anyone confirm that?
Hi all; just a reminder that the bug tracker is not a discussion forum. If you want to discuss an issue, please do so on either the Mojira Discord or Mojira Reddit and not in the comments section of a ticket. 🙂
I don't understand the purpose of the comments section for a bug then, Avoma. My previous comment (asking why this has been marked as resolved and won't fix) directly relates to the bug so why post it on Discord or reddit instead of as a comment on the bug?
Hello @unknown. We use the comments section as a place for supplying more information regarding the bug in question, not actually for discussing the bug. In other words, the purpose of the comments section of a ticket is not to discuss its outcome; please refer to the Bug Tracker Guidelines for more information regarding this.
If you want to initiate a discussion about a bug or need to report someone, take the discussion outside of the bug tracker (see FAQs), do not comment directly on the bug tracker.
As for the "Won't Fix" resolution, explanations regarding the reasoning behind these choices aren't always provided. Mojang does consider this to be a bug but has chosen not to fix it. Once again, please do not comment on this ticket; you are welcome to talk about this further outside of the bug tracker. Thanks! 🙂
It'll probably be helpful if you provide a (zipped) world where this occurs. If it's too big, upload to an external site and provide the link.