Centural

There is the EXACT code running on the server right now, use `/trigger phase` over and over again causes it.

I will try and get a video and remove line by line to figure out what is causing this.

ONE Moment let me add the load function file as well...

I do not know how to do that, please tell me how to do this? I am sorry.

probably unrelated but this also appears in the logs periodically

java.lang.NullPointerException: Cannot invoke "it.unimi.dsi.fastutil.objects.ObjectSet.remove(Object)" because "☃" is nulljava.lang.NullPointerException: Cannot invoke "it.unimi.dsi.fastutil.objects.ObjectSet.remove(Object)" because "☃" is null at abe.b(SourceFile:202) ~[server.jar:?] at aay.a(SourceFile:914) ~[server.jar:?] at abj.a(SourceFile:460) ~[server.jar:?] at acd.a(SourceFile:944) ~[server.jar:?] at ua.a(SourceFile:114) ~[server.jar:?] at ua$a.a(SourceFile:42) ~[server.jar:?] at ph.a(SourceFile:21) ~[server.jar:?] at xh.run(SourceFile:18) ~[server.jar:?] at aqe.c(SourceFile:152) ~[server.jar:?] at aqi.c(SourceFile:23) ~[server.jar:?] at net.minecraft.server.MinecraftServer.b(SourceFile:766) ~[server.jar:?] at net.minecraft.server.MinecraftServer.c(SourceFile:161) ~[server.jar:?] at aqe.z(SourceFile:126) ~[server.jar:?] at net.minecraft.server.MinecraftServer.bd(SourceFile:748) ~[server.jar:?] at net.minecraft.server.MinecraftServer.z(SourceFile:742) ~[server.jar:?] at aqe.bn(SourceFile:111) ~[server.jar:?] at net.minecraft.server.MinecraftServer.y(SourceFile:726) ~[server.jar:?] at net.minecraft.server.MinecraftServer.x(SourceFile:678) ~[server.jar:?] at net.minecraft.server.MinecraftServer.a(SourceFile:261) ~[server.jar:?] at java.lang.Thread.run(Thread.java:831) [?:?][11:07:17] [Server thread/FATAL]: Error executing task on Serverjava.lang.NullPointerException: Cannot invoke "it.unimi.dsi.fastutil.objects.ObjectSet.remove(Object)" because "☃" is null at abe.b(SourceFile:202) ~[server.jar:?] at aay.a(SourceFile:914) ~[server.jar:?] at abj.a(SourceFile:460) ~[server.jar:?] at acd.a(SourceFile:944) ~[server.jar:?] at ua.a(SourceFile:114) ~[server.jar:?] at ua$a.a(SourceFile:42) ~[server.jar:?] at ph.a(SourceFile:21) ~[server.jar:?] at xh.run(SourceFile:18) ~[server.jar:?] at aqe.c(SourceFile:152) ~[server.jar:?] at aqi.c(SourceFile:23) ~[server.jar:?] at net.minecraft.server.MinecraftServer.b(SourceFile:766) ~[server.jar:?] at net.minecraft.server.MinecraftServer.c(SourceFile:161) ~[server.jar:?] at aqe.z(SourceFile:126) ~[server.jar:?] at net.minecraft.server.MinecraftServer.bd(SourceFile:748) ~[server.jar:?] at net.minecraft.server.MinecraftServer.z(SourceFile:742) ~[server.jar:?] at aqe.bn(SourceFile:111) ~[server.jar:?] at net.minecraft.server.MinecraftServer.y(SourceFile:726) ~[server.jar:?] at net.minecraft.server.MinecraftServer.x(SourceFile:678) ~[server.jar:?] at net.minecraft.server.MinecraftServer.a(SourceFile:261) ~[server.jar:?] at java.lang.Thread.run(Thread.java:831) [?:?]

I was told the CPU is to low of a Clock Speed and unsupported by Mojang; is this the case for ALL CPUS that are below 3.1Ghz?

My question is why is it that Galaxy still tries to resolve a problem even on unsupported device?

We have been running Snapshots as a Server and can confirm this happens in parallel to furnaces, hoppers, chest, sticky pistons, etc breaking.
(Would venture to say this has been present in the first few snapshots and up until now has not been patched)

Manually running /save-all helps with fixing broken chunks (Regarding not saving) but furances, hoppers, chest, stickypistons, etc.. is less deterministic (Usually relogging, leaving the chunk, coming back sometimes fixes it)

 Still Effects 21w17a

That looks like the exact same issue thank you!

Can you please provide me the absolute best link for a guide on the best way to make posts on Mojang Jira but not have the Bug Report be marked as Resolved?

I have noticed this over the years on different accounts and have not come up with the best way to report a bug as  more than half the time it is marked Resolved BEFORE it is actually resolved. (And honestly this may be the reason why some bugs still exist in the game)

I do see where the image might help but if I was the QA here I feel opening up the game and running the commands listed in the text above would have pointed any QA into the right direction on what is wrong here.

Verified still exists in 21w11a

You do not even have to have the whitelist enabled, currently on our server if you DEOP any players it kicks ALL players and says were are not on the whitelist

Verified still exists in 21w08b

Happened twice today when deoping a player it would kick quite a few other players offline instantly and tell them they are not on the whitelist; We also do not have whitelist enabled so they log back in fine but the kick still occurs for them as well as the message.

Kick some good people on accident 0:

Not sure exact steps but try OPing multiple players then DEOP them with the server setting in game for whitelist turned off (/gamerule whitelist off)

They must be online to see the kick occur. 

What is the issue? 

• Are Non Hostile Mobs Like Pigs, Cows, Sheeps, Bees, Chicken, Rabbit, Llamas, Horse, Fox, Wolf, etc. supposed to spawn in with these settings turned off. 

• (This may effect Hostile Mobs as well but have not tested it with further settings..)

Start a Server that has the following server.properties all set to false

Run These Commands Manually in Game 

/gamerule doMobSpawning false
/difficulty peaceful

Run this command in Repeat
/execute as @e[type=!player] run tag @s add track

Run another command either in chain or on another repeat block to further manipulate entities that are in the world based off that "track" tag example and you are able to grab and store entity data like Pigs, Cows, Sheep, etc. as they spawn in with the spawn settings turned to false. 

Example:
Run This In Repeat
/execute as @e[tag=track] run data modify storage entity track append from entity @s

Run This Manually
/data get storage minecraft:entity track
(You may need to run this get command in the Server Terminal if the storage is to large)

Is this an Intended Feature? (Should Pigs/Cows/Sheep/Bees/etc.. still exist in the map or "Spawn in" Temporarily before "Despawning" with these settings?) OR should it work more like Mob Spawning (As I have not see any Zombies/Skeletons/Spiders/Creepers/Etc. Hostile Mobs spawn in through this above method testing)

Notes: This seems to effect only Non Hostile Mobs (But may be given the settings I currently am using)

Yes that is a very similar issue; (In their case they are Manually attempting to spawn in a mob I think, but its a similar idea)

Essentially with Mob Spawning Disabled a Command can still access the mobs as they spawn in then they despawn; I am just curious if this is a Bug or a Planned Feature (If it is a planned feature I can plan to script with that in mind)

The structure file makes an entry of each entity in the storage minecraft:entity remove ; this happens then they despawn; which if fine if it is intended to work that way but if not then Id rather not write a script that expects this behavior. 

Thank you so much Tryashtar, I caught that a few moments later and was biting myself in the foot for opening the bug report. 

Appreciate the help!

As of 5 Mins ago this issue was NOT resolved.

The correct link is this one:

https://launcher.mojang.com/v1/objects/d0d0fe2b1dc6ab4c65554cb734270872b72dadd6/server.jar

The one given on the 1.14.3 patch notes page is incorrect. The one given on the server hosting page is correct.

Hosting Page (https://www.minecraft.net/en-us/download/server/)

Patch Note Page (https://www.minecraft.net/en-us/article/minecraft-java-edition-1-14-3)

As of 5 Mins ago this issue was NOT resolved.

The correct link is this one:

https://launcher.mojang.com/v1/objects/d0d0fe2b1dc6ab4c65554cb734270872b72dadd6/server.jar

The one given on the 1.14.3 patch notes page is incorrect. The one given on the server hosting page is correct.