This bug still affects release 1.16.4 (vanilla client and server) using the following custom spawner:
/setblock ~ ~-1 ~ minecraft:spawner\{SpawnData:{id:iron_golem},SpawnCount:3,SpawnRange:4,RequiredPlayerRange:25,Delay:20,MinSpawnDelay:9600,MaxSpawnDelay:9600,MaxNearbyEntities:25} replace
Spamming the client logs with thousands of warnings about:
Exception loading entity: u: Loading entity NBT at aqa.f(SourceFile:1663) at aqe.a(SourceFile:473) at x.a(SourceFile:402) at aqe.a(SourceFile:472) at aqe.b(SourceFile:535) at aqe.a(SourceFile:516) at bqz.d(SourceFile:254) at ecp.a(SourceFile:22) at ecp.a(SourceFile:12) at ecd.a(SourceFile:107) at ecd.b(SourceFile:96) at ecd.a(SourceFile:128) at ecd.a(SourceFile:96) at eae.a(SourceFile:1260) at dzz.a(SourceFile:727) at dzz.a(SourceFile:546) at djz.e(SourceFile:1048) at djz.e(SourceFile:681) at net.minecraft.client.main.Main.main(SourceFile:215) Caused by: java.lang.ClassCastException: class dwt cannot be cast to class aag (dwt and aag are in unnamed module of loader 'app') at bai.a(SourceFile:170) at aqa.f(SourceFile:1654) ... 18 more
As a consequence, user logs can grow very large.
Confirmed for pre4. This comes up in lots of situations, particularly when making datapacks:
Example commands:
/data get entity @p
and since I have a lot of scoreboard objectives: 🙂
/scoreboard objectives list
EDIT: Linux client and server. Java 8.
Also on Fedora 36 Linux. And this (extra 't' and '//') has been troubling me for many years and many versions of Fedora. Is it really that hard to fix or do you just not care?