java.lang.NullPointerException
	at ea.b(SourceFile:116)
	at ea.a(SourceFile:41)

---- Minecraft Crash Report ----
// My bad.

Time: 19/09/13 19:02
Description: Sending packet

java.lang.NullPointerException
	at ea.b(SourceFile:116)
	at ea.a(SourceFile:41)
	at ku.b(SourceFile:432)
	at ln.b(SourceFile:170)
	at jg.a(SourceFile:86)
	at bou.b(SourceFile:73)
	at net.minecraft.server.MinecraftServer.u(SourceFile:487)
	at net.minecraft.server.MinecraftServer.t(SourceFile:404)
	at bor.t(SourceFile:124)
	at net.minecraft.server.MinecraftServer.run(SourceFile:338)
	at jb.run(SourceFile:581)


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

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

-- Packet being sent --
Details:
	Packet ID: 200
	Packet class: fc
Stacktrace:
	at ku.b(SourceFile:432)
	at ln.b(SourceFile:170)
	at jg.a(SourceFile:86)
	at bou.b(SourceFile:73)
	at net.minecraft.server.MinecraftServer.u(SourceFile:487)
	at net.minecraft.server.MinecraftServer.t(SourceFile:404)
	at bor.t(SourceFile:124)
	at net.minecraft.server.MinecraftServer.run(SourceFile:338)
	at jb.run(SourceFile:581)

-- System Details --
Details:
	Minecraft Version: 13w38a
	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: 193593000 bytes (184 MB) / 471240704 bytes (449 MB) up to 518979584 bytes (494 MB)
	JVM Flags: 2 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx512M
	AABB Pool Size: 27895 (1562120 bytes; 1 MB) allocated, 27895 (1562120 bytes; 1 MB) used
	IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0
	Profiler Position: N/A (disabled)
	Vec3 Pool Size: 7313 (409528 bytes; 0 MB) allocated, 7313 (409528 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.