---- Minecraft Crash Report ----
// Don't be sad. I'll do better next time, I promise!

Time: 27/09/13 5:16 PM
Description: Sending packet

java.lang.NullPointerException
	at cn.b(SourceFile:116)
	at cn.a(SourceFile:41)
	at ka.b(SourceFile:423)
	at hn.b(SourceFile:648)
	at hn.a(SourceFile:82)
	at blc.b(SourceFile:73)
	at net.minecraft.server.MinecraftServer.t(SourceFile:489)
	at net.minecraft.server.MinecraftServer.s(SourceFile:406)
	at bkz.s(SourceFile:124)
	at net.minecraft.server.MinecraftServer.run(SourceFile:340)
	at hi.run(SourceFile:583)


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

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

-- Packet being sent --
Details:
	Packet ID: 4
	Packet class: fx
Stacktrace:
	at ka.b(SourceFile:423)
	at hn.b(SourceFile:648)
	at hn.a(SourceFile:82)
	at blc.b(SourceFile:73)
	at net.minecraft.server.MinecraftServer.t(SourceFile:489)
	at net.minecraft.server.MinecraftServer.s(SourceFile:406)
	at bkz.s(SourceFile:124)
	at net.minecraft.server.MinecraftServer.run(SourceFile:340)
	at hi.run(SourceFile:583)

-- System Details --
Details:
	Minecraft Version: 1.6.4
	Operating System: Windows 7 (amd64) version 6.1
	Java Version: 1.7.0_25, Oracle Corporation
	Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
	Memory: 43029224 bytes (41 MB) / 257425408 bytes (245 MB) up to 954466304 bytes (910 MB)
	JVM Flags: 2 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx1G
	AABB Pool Size: 1113 (62328 bytes; 0 MB) allocated, 1113 (62328 bytes; 0 MB) used
	Suspicious classes: No suspicious classes found.
	IntCache: cache: 0, tcache: 0, allocated: 1, tallocated: 63
	Profiler Position: N/A (disabled)
	Vec3 Pool Size: 133 (7448 bytes; 0 MB) allocated, 133 (7448 bytes; 0 MB) used
	Player Count: 0 / 8; []
	Type: Integrated Server (map_client.txt)
	Is Modded: Probably not. Jar signature remains and both client + server brands are untouched.