Common Problems

From Galacticraft Wiki
Jump to: navigation, search

Galacticraft mob seen on Overworld

When your game is working properly, there will not be any Galacticraft mobs spawning naturally on the Overworld.

Occasionally, players report issues like this:

I'm having this problem with the Evolved Creeper Boss spawning in overworld with its health bar constantly at the top of the screen. I'm using the latest version of Galacticraft with Forge 1.7.10.

It could be the Evolved Creeper Boss seen on the Overworld as there, it could be some other Galacticraft mob.

This phenomenon happens when the player is on a server and the server has different mods (or different mod versions), or maybe just different configs for something connected with Entity IDs. It's not Galacticraft causing this. One of your other mods is different.

The Galacticraft mob is not really there - it just looks that way, in reality it's a chicken or a sheep or something. It won't attack you.

How to fix:

This can be fixed simply by updating to the latest Galacticraft (versions or later) on the server and on the client, note both need to update together. However, this fix might just transfer the problem to some other mod instead, in which case read on.

If that doesn't solve it - if you need to stick with an older Galacticraft version for some reason, or now the same problem is happening for a different mod's mobs - then:

  • Carefully check that the player does not have a mod which is missing on the server - this is the most likely reason. (Except: mods like Optifine or mapping mods are client-side only, so don't worry about those ones.)
  • Carefully check the whole modlist to make sure every mod has exactly matching versions between server and client
  • If all the mod versions exactly match and the issue still happens, now check that all the configs exactly match
  • If there's still a problem then most likely you did not check those things carefully enough. Either that, or it's a bug in one of the other mods (very unlikely as any bug like this would have been spotted within minutes)

Crash involving GCEntityClientPlayerMP

People sometimes report crashes involving GCEntityClientPlayerMP or GCPlayerBaseSP. In 99% of cases, these are not Galacticraft crashes, it's another mod crashing.

Explanation: Galacticraft changes the internal name of the vanilla player in Minecraft from EntityClientPlayerMP to GCEntityClientPlayerMP. Because of this change, whenever there is any mod crash involving the player, it will look like the Galacticraft version of the player, "GCEntityClientPlayerMP", is maybe involved. It's not really involved at all. Galacticraft is not the cause of these types of crashes, the same way that vanilla Minecraft is not the cause.

We request people who are smart enough to read the crash report and see GCEntityClientPlayerMP in it, also stop and think about this. As with any other crash report, it's whatever is at the top of the crash report which is causing the problem - not what's in the middle.

Here are some examples:

NoSuchMethodError on world load

---- Minecraft Crash Report ----
// My bad.
Time: 19/04/15 12:52 PM
Description: Unexpected error
java.lang.NoSuchMethodError: com.mojang.authlib.minecraft.MinecraftProfileTexture.<init>(Ljava/lang/String;)V
        at net.minecraft.client.entity.AbstractClientPlayer.downloadCape(
        at net.minecraft.client.entity.AbstractClientPlayer.<init>(
        at net.minecraft.client.entity.EntityPlayerSP.<init>(
        at net.minecraft.client.entity.EntityClientPlayerMP.<init>(SourceFile:36)
        at micdoodle8.mods.galacticraft.core.entities.player.GCEntityClientPlayerMP.<init>(
        at net.minecraft.client.multiplayer.PlayerControllerMP.func_147493_a(

This crash is caused by Optifine combined with the 'security' changes made by Mojang in April 2015. Optifine changelog for this

Ticking entity error

---- Minecraft Crash Report ----
// Why did you do that?
Time: 4/10/15 2:08 AM
Description: Ticking entity
java.lang.NullPointerException: Ticking entity
        at com.flashoverride.heartdrop.HeartDropEventHandler.onEvent(
        at cpw.mods.fml.common.eventhandler.ASMEventHandler_1070_HeartDropEventHandler_onEvent_LivingAttackEvent.invoke(.dynamic)
        at cpw.mods.fml.common.eventhandler.ASMEventHandler.invoke(
        at net.minecraftforge.common.ForgeHooks.onLivingAttack(
        at net.minecraft.entity.player.EntityPlayer.func_70097_a(
        at net.minecraft.entity.player.EntityPlayerMP.func_70097_a(
        at micdoodle8.mods.galacticraft.core.entities.player.GCEntityPlayerMP.func_70097_a(

Explanation: This is a crash in the HeartDrop mod, as shown by the top line of the crash report.

Potion effect error

[21:40:12] [Client thread/ERROR] [FML/]: ---- Minecraft Crash Report ----
// There are four lights!

Time: 6/30/15 9:40 PM
Description: Ticking entity

java.lang.NullPointerException: Ticking entity
at net.minecraft.potion.PotionEffect.func_76455_a(
at net.minecraft.entity.EntityLivingBase.func_70679_bo(
at net.minecraft.entity.EntityLivingBase.func_70030_z(
at net.minecraft.entity.Entity.func_70071_h_(
at net.minecraft.entity.EntityLivingBase.func_70071_h_(
at net.minecraft.entity.player.EntityPlayer.func_70071_h_(
at net.minecraft.client.entity.EntityClientPlayerMP.func_70071_h_(SourceFile:63)
at micdoodle8.mods.galacticraft.core.entities.player.GCEntityClientPlayerMP.func_70071_h_(

Explanation: this is a crash caused by another mod not registering a potion effect properly. A "potion effect" can be any bad stuff that happens when you take damage from a mob, like poison, dizziness etc. To find the cause, take a look at your mods which have mobs which do extra damage effects like that.

Mod conflicts: Binary Seach method

So you have this huge modlist of 50 or more mods, and one of them is conflicting with Galacticraft, but it's not obvious which one. How do you figure that out, without restarting the game 50 times?

A binary search method can find which mod is conflicting in just 6 restarts of the game.

The concept is you divide your modlist in half - remove half of the mods - then see if the game still has the issue. If the game still has the issue, then you know the problem is in the half of the mods you kept. If the issue stopped happening, then you know the problem is in the half of the mods you removed.


  • Step 1. create a new folder /mods_removed and move half the mods from the /mods folder to it (keep together mods which have to go together, for example some mods have to be paired with core mods or libraries like Mantle)
  • Step 2. make a note or screenshot of the mods you just moved, because you will need to know later which is which - or maybe make subfolders in the /mods_removed folder so you know which group is which;
  • Step 3. start the game, create a new world, see if you stil have the issue or not;
  • Step 4A. if the issue was fixed, look at the mods you just removed, pick half of them and move that half back into the /mods folder, keeping a careful note of which mods these are, then go to Step 3;
  • Step 4B. if the issue was not fixed, pick half of the remaining mods (or half of the ones most recently added back in at Step 4A) for removal, and go to Step 1

Obviously you must not use an existing world before doing these tests, because changing mods around will damage any existing world. If you have to have an existing world because you need a complex build, keep a full backup.

External Links

See also

Unless stated otherwise, all information contained on this wiki should be considered outdated and might not reflect in-game experiences