Running this command:
give @p[score_Name] 166crashes the game.
Affected IDs: 36, 144, 166, 237, 500
Linked issues
is duplicated by 39
relates to 2
Attachments
Comments 31
This was a typo I meant 266 with is a golden ingot. I had that in the commandblok but I didn't copy & paste it to here, so give @p[score_Name] 266 it is 😛
Here:
---- Minecraft Crash Report ----
// Don't do that.
Time: 27.09.13 16:24
Description: Adding item to inventory
java.lang.NullPointerException
at zi.g(SourceFile:151)
at zi.i(SourceFile:171)
at vd.a(SourceFile:234)
at tq.b_(SourceFile:199)
at vf.r(SourceFile:436)
at vf.e(SourceFile:428)
at pb.h(SourceFile:1194)
at vf.h(SourceFile:211)
at kq.i(SourceFile:204)
at kv.a(SourceFile:201)
at gs.a(SourceFile:136)
at eb.b(SourceFile:63)
at kv.e(SourceFile:69)
at ky.b(SourceFile:40)
at box.b(SourceFile:83)
at net.minecraft.server.MinecraftServer.u(SourceFile:494)
at net.minecraft.server.MinecraftServer.t(SourceFile:411)
at bou.t(SourceFile:121)
at net.minecraft.server.MinecraftServer.run(SourceFile:346)
at jc.run(SourceFile:582)
A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------
-- Head --
Stacktrace:
at zi.g(SourceFile:151)
at zi.i(SourceFile:171)
-- Item being added --
Details:
Item ID: 0
Item data: 0
Item name: ~~ERROR~~ NullPointerException: null
Stacktrace:
at vd.a(SourceFile:234)
at tq.b_(SourceFile:199)
at vf.r(SourceFile:436)
at vf.e(SourceFile:428)
at pb.h(SourceFile:1194)
at vf.h(SourceFile:211)
-- Player being ticked --
Details:
Entity Type: null (kq)
Entity ID: 1093
Entity Name: DayCraftMC
Entity's Exact location: -503,38, 65,20, 76,18
Entity's Block location: World: (-504,65,76), Chunk: (at 8,4,12 in -32,4; contains blocks -512,0,64 to -497,255,79), Region: (-1,0; contains chunks -32,0 to -1,31, blocks -512,0,0 to -1,255,511)
Entity's Momentum: 0,00, 0,00, 0,00
Stacktrace:
at kq.i(SourceFile:204)
at kv.a(SourceFile:201)
at gs.a(SourceFile:136)
at eb.b(SourceFile:63)
at kv.e(SourceFile:69)
-- Ticking connection --
Details:
Connection: kv@78ebdb9f
Stacktrace:
at ky.b(SourceFile:40)
at box.b(SourceFile:83)
at net.minecraft.server.MinecraftServer.u(SourceFile:494)
at net.minecraft.server.MinecraftServer.t(SourceFile:411)
at bou.t(SourceFile:121)
at net.minecraft.server.MinecraftServer.run(SourceFile:346)
at jc.run(SourceFile:582)
-- System Details --
Details:
Minecraft Version: 13w39b
Operating System: Windows 8 (amd64) version 6.2
Java Version: 1.7.0_25, Oracle Corporation
Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 103673424 bytes (98 MB) / 304349184 bytes (290 MB) up to 477233152 bytes (455 MB)
JVM Flags: 3 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx1G -Xmx512M
AABB Pool Size: 5078 (284368 bytes; 0 MB) allocated, 4880 (273280 bytes; 0 MB) used
IntCache: cache: 0, tcache: 0, allocated: 12, tallocated: 94
Profiler Position: N/A (disabled)
Vec3 Pool Size: 1308 (73248 bytes; 0 MB) allocated, 1092 (61152 bytes; 0 MB) used
Player Count: 1 / 8; [kq['DayCraftMC'/1093, l='King Quest3', x=-503,38, y=65,20, z=76,18]]
Type: Integrated Server (map_client.txt)
Is Modded: Probably not. Jar signature remains and both client + server brands are untouched.
Did you really use 266? Just check your Command block again, maybe a screenshot (with Print key, because F2 doesn't work in Interfaces anymore) would help us as well.
Is this still a concern in the current Minecraft version 1.7.2 / Launcher version 1.3.4 or later? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
No more crash. Yes still log spam with /summon Item ~ ~-2 ~ {Item:{id:36}}
(Or something like that)
Really, items that have a invalid id should not become id 0 (which is still invalid), they should become 1.
@User who's comment appears to have been deleted:
My guess is that they saw "Invalid value" and went "Hm, must be invalid". Similar thing happened to me with 33:6 or 33:7 (piston, data value 6 or 7), because those crash the game too. They don't corrupt the chunks though. Whatever code is reasponcible for that needs to be changed, probably to something that puts a message in the chat and deletes the block.
This is caused because you are using an invalid block id. There currently is no block 166.