Crash due to "entity 569"

Home Forums JinGames Forums Bug Reports Crash due to "entity 569"

Viewing 2 reply threads
^ Advertisement ^
  • Author
    Posts
    • #35610
      Mitchell Garrett
      Participant

      This has been happening for a very long time in my worlds. I start a new world, play for a bit,
      then a crash from doing something (don’t know exact cause) that consists of:

      A detailed walkthrough of the error, its code path and all known details is as follows:
      ---------------------------------------------------------------------------------------
      
      -- Head --
      Stacktrace:
      	at JinRyuu.JRMCore.entity.RenderEnergyAtt.renderEnergy(RenderEnergyAtt.java:73)
      	at JinRyuu.JRMCore.entity.RenderEnergyAtt.func_76986_a(RenderEnergyAtt.java:438)
      
      -- Entity being rendered --
      Details:
      	Entity Type: jinryuudragonblockc.EnergyAttack (JinRyuu.JRMCore.entity.EntityEnergyAtt)
      	Entity ID: 569
      	Entity Name: entity.jinryuudragonblockc.EnergyAttack.name
      	Entity's Exact location: 134.18, 70.93, 14.39
      	Entity's Block location: World: (134,70,14), Chunk: (at 6,4,14 in 8,0; contains blocks 128,0,0 to 143,255,15), Region: (0,0; contains chunks 0,0 to 31,31, blocks 0,0,0 to 511,255,511)
      	Entity's Momentum: -0.04, -0.01, -1.21
      
      -- Renderer details --
      Details:
      	Assigned renderer: JinRyuu.JRMCore.entity.RenderEnergyAtt@9d7c04
      	Location: -0.14,9.24,-31.10 - World: (-1,9,-32), Chunk: (at 15,0,0 in -1,-2; contains blocks -16,0,-32 to -1,255,-17), Region: (-1,-1; contains chunks -32,-32 to -1,-1, blocks -512,0,-512 to -1,255,-1)
      	Rotation: -178.29912
      	Delta: 0.24437904
      Stacktrace:
      	at net.minecraft.client.renderer.entity.RenderManager.func_147939_a(RenderManager.java:313)
      	at net.minecraft.client.renderer.entity.RenderManager.func_147936_a(RenderManager.java:291)
      	at net.minecraft.client.renderer.entity.RenderManager.func_147937_a(RenderManager.java:264)
      	at net.minecraft.client.renderer.RenderGlobal.func_147589_a(RenderGlobal.java:737)
      	at net.minecraft.client.renderer.EntityRenderer.func_78471_a(EntityRenderer.java:1712)
      	at JinRyuu.JBRA.JBRAEnRen.func_78471_a(JBRAEnRen.java:23)
      	at net.minecraft.client.renderer.EntityRenderer.func_78480_b(EntityRenderer.java:1392)

      This was also somewhere else in the crashlog underneath the one above

      Forced entities: 14 total; [EntityClientPlayerMP['TheHunterManX'/555, l='MpServer', x=134.35, y=61.70, z=46.40], EntityPig['Pig'/565, l='MpServer', x=109.31, y=68.00, z=2.50], EntityPig['Pig'/566, l='MpServer', x=108.50, y=71.00, z=20.69], EntityPig['Pig'/567, l='MpServer', x=111.97, y=68.00, z=24.66], EntityPig['Pig'/568, l='MpServer', x=114.22, y=63.00, z=28.34], EntityEnergyAtt['entity.jinryuudragonblockc.EnergyAttack.name'/569, l='MpServer', x=134.18, y=70.93, z=14.39], EntityXPOrb['Experience Orb'/570, l='MpServer', x=141.38, y=51.10, z=52.06], EntityXPOrb['Experience Orb'/506, l='MpServer', x=114.10, y=55.10, z=74.25], EntityXPOrb['Experience Orb'/571, l='MpServer', x=142.85, y=52.10, z=50.34], EntityEnergyAtt['entity.jinryuudragonblockc.EnergyAttack.name'/572, l='MpServer', x=145.71, y=70.67, z=14.07], EntityXPOrb['Experience Orb'/573, l='MpServer', x=146.22, y=47.10, z=43.93], EntityXPOrb['Experience Orb'/509, l='MpServer', x=156.88, y=53.10, z=66.78], EntityXPOrb['Experience Orb'/574, l='MpServer', x=152.38, y=48.10, z=36.93], EntityXPOrb['Experience Orb'/510, l='MpServer', x=156.22, y=53.10, z=68.25]]

      I am in my own singleplayer worlds usually when this happens. Does anyone have a solution for this or is there one already or is this just me?

      Mods used:
      DBC 1.4.40
      JRMCCore 1.2.47
      JBRA Client 1.6.25
      NarutoC 0.6.4

      This has also happened in most if not all of the other versions.

    • #35616
      Aegous
      Participant

      Probably best to use pastebin or something as it is pretty hard to read errors on a single line.

    • #35746
      Mitchell Garrett
      Participant

      Heres the link to the full crash report:
      https://pastebin.com/k8j7g3Ri
      Hopefully the bug can be easily fixed.

Viewing 2 reply threads
  • You must be logged in to reply to this topic.

Comments are closed.