Flan's Mod: Legacy

Flan's Mod: Legacy

2M Downloads

[Crash-Report] java.lang.NullPointerException - TeamsManager

Sir-Will opened this issue ยท 5 comments

commented

Minecraft: 1.6.4 Flans Mod: 4.1.1

java.lang.NullPointerException
    at co.uk.flansmods.common.teams.TeamsManager.tick(TeamsManager.java:136)
    at co.uk.flansmods.common.CommonTickHandler.sTick(CommonTickHandler.java:32)
    at co.uk.flansmods.common.CommonTickHandler.tickEnd(CommonTickHandler.java:25)
    at cpw.mods.fml.common.SingleIntervalHandler.tickEnd(SingleIntervalHandler.java:34)
    at cpw.mods.fml.common.FMLCommonHandler.tickEnd(FMLCommonHandler.java:141)
    at cpw.mods.fml.common.FMLCommonHandler.onPostServerTick(FMLCommonHandler.java:274)
    at net.minecraft.server.MinecraftServer.func_71217_p(MinecraftServer.java:813)
    at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:659)
    at net.minecraft.server.ThreadMinecraftServer.run(ThreadMinecraftServer.java:16)
commented

According to guy on IRC "there is no point in making your own PlayerData and maintain a map about it. that just screams for memory leaks and bugs. Use IExtendedEntityProperties."

commented

i've got the Error in version 4.3.0 my Crashreport:

java.lang.NullPointerException: Exception in server tick loop
at com.flansmod.common.teams.TeamsManager.tick(TeamsManager.java:148)
at com.flansmod.common.CommonTickHandler.tick(CommonTickHandler.java:47)
at >cpw.mods.fml.common.eventhandler.ASMEventHandler_16_CommonTickHandler_tick_ServerTickEven>t.invoke(.dynamic)
at cpw.mods.fml.common.eventhandler.ASMEventHandler.invoke(ASMEventHandler.java:51)
at cpw.mods.fml.common.eventhandler.EventBus.post(EventBus.java:122)
at cpw.mods.fml.common.FMLCommonHandler.onPostServerTick(FMLCommonHandler.java:247)
at net.minecraft.server.MinecraftServer.func_71217_p(MinecraftServer.java:828)
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:640)
at java.lang.Thread.run(Unknown Source)

commented

Why you closed is it fixed?

commented

It's already fixed for the next version.

commented

This crash is still present in 4.2.3 for 1.7.2.