---- Minecraft Crash Report ----
// Who set us up the TNT?

Time: 7/30/13 6:44 AM
Description: Sending packet

java.lang.NullPointerException
	at cm.b(SourceFile:116)
	at cm.a(SourceFile:41)
	at jz.b(SourceFile:421)
	at hm.a(SourceFile:90)
	at bkz.b(SourceFile:73)
	at net.minecraft.server.MinecraftServer.t(SourceFile:488)
	at net.minecraft.server.MinecraftServer.s(SourceFile:405)
	at bkw.s(SourceFile:124)
	at net.minecraft.server.MinecraftServer.run(SourceFile:339)
	at hh.run(SourceFile:582)


A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------

-- Head --
Stacktrace:
	at cm.b(SourceFile:116)
	at cm.a(SourceFile:41)

-- Packet being sent --
Details:
	Packet ID: 4
	Packet class: fw
Stacktrace:
	at jz.b(SourceFile:421)
	at hm.a(SourceFile:90)
	at bkz.b(SourceFile:73)
	at net.minecraft.server.MinecraftServer.t(SourceFile:488)
	at net.minecraft.server.MinecraftServer.s(SourceFile:405)
	at bkw.s(SourceFile:124)
	at net.minecraft.server.MinecraftServer.run(SourceFile:339)
	at hh.run(SourceFile:582)

-- System Details --
Details:
	Minecraft Version: 1.6.2
	Operating System: Windows 7 (x86) version 6.1
	Java Version: 1.7.0_25, Oracle Corporation
	Java VM Version: Java HotSpot(TM) Client VM (mixed mode, sharing), Oracle Corporation
	Memory: 268789928 bytes (256 MB) / 453558272 bytes (432 MB) up to 518979584 bytes (494 MB)
	JVM Flags: 2 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx512M
	AABB Pool Size: 4337 (242872 bytes; 0 MB) allocated, 4337 (242872 bytes; 0 MB) used
	Suspicious classes: No suspicious classes found.
	IntCache: cache: 2, tcache: 0, allocated: 1, tallocated: 63
	Profiler Position: N/A (disabled)
	Vec3 Pool Size: 2024 (113344 bytes; 0 MB) allocated, 2024 (113344 bytes; 0 MB) used
	Player Count: 1 / 8; [ju['Thrine1234'/3608492, l='Rich world', x=130.05, y=64.00, z=300.09]]
	Type: Integrated Server (map_client.txt)
	Is Modded: Probably not. Jar signature remains and both client + server brands are untouched.