Must all entities have a constructor that only takes net.minecraft.world.World as a parameter?

[Keheck]

While I was working on my mod my IDE complained that "All entities must have a constructor that takes one net.minecraft.world.World constructor"

//A constructor like this:
public Entity(net.minecraft.world.World world)
{
  //do stuff
}

I was wondering why, especially because the mod builds and the entity registers just fine without this constructor.

I dug around in my code inspection settings and it turns out that it belongs to the MCP inspection group.

Using a breakpoint to find it's usage didn't help since at no point during mod setup and testing (testing as in summoning the entity via the /summon command; the entity is a throwable and would use another constructor when thrown anyway).

 

When is this constructor used, if at all, and is that constructor important?

[Animefan8888]

  On 4/5/2020 at 11:40 AM, Keheck said:

While I was working on my mod my IDE complained that "All entities must have a constructor that takes one net.minecraft.world.World constructor"

Expand  

That constructor makes me think you are using 1.12 or an earlier version. Which are not supported on this forum. Please update to a modern version of Minecraft to receive support. For more information read the LTS at the top of the page.

[_Cruelar_]

If you aren't using 1.12 (which I agree with Animefan seems like you do): The Plugin in IntelliJ which I think you're using isn't working for 1.14 and needs to be manually redownloaded with a newer version to work with newer Forge versions

[Draco18s]

Oh, and for reference, that constructor is used to load the entity from disk.