LexManos

There is no support here for 1.7.10. Update.

We do not support 1.7.10 here any more, update to 1.10+

We load both

The client side doesnt care about your custom constructor. It just gets told you have a entity on the server so it creates a new one using the World constructor. And then makes it read from NBT. So As stated, there is no real reason to use custom constructors for entities, make sure your data is stored and sent to the client.

1) Stop using 1.7.10 2) Stop using coremods.

Start by removing these files and yelling at their authors for being morons.

Do not use either CCC or NEI. They are coremods and have been replaced by better mods that do not screw with the internal code of Forge/Minecraft. Go get JEI.

.... what? You can't just run two different versions of minecraft in the same game.... how do you expect that to work?

This was a temporary bug with our cleanup of a vanilla registry issue. This has been fixed for a while. Provide logs and make sure you're on the latest version.

Stop using 1.7.10.

.... quit trying to help him. This is basic language syntax.... he needs java 101 which is not what this forum/mc are for

Your profile has to be configured to use Forge. You're launching vanilla minecraft. In your profile there is a drop down list labeled Minecraft Version. Select Forge in that list.

Depends on your mod. Mods Loaded are ALL of the mods the loader knows about. Mods Active are the ones that it actually started, mods can be known but not started for many reasons ranging from a config to disable them. To an error happened and it got disabled. You should read the logs to find out.

No, that just gets to complicated. What you SHOULD do if you want to do things properly, is use the mod_list.json and store all your mods in your libraries folder.

Logs

Yes, @Dprecated in the MC codebase can be taken as: Modders should NEVER CALL this. But as we have not moved away from it, modders MAY need to IMPLEMENT this. Mojang is working on cleaning up their code base a lot. So things are in flux just like every major project out there. The annotations are a guide. Seriously it's not a hard concept. Are you calling a deprecated function? STOP Are you implementing a deprecated function? Fine, just be weary it may change in future MC versions. {Just like everything else} Remember Minecraft IS NOT a full fledged professional modder facing API. It's a decompiled internal hack of a client. I seriously can't understand how people can't grasp this simple concept, we get FAR to many of these 'but the method is deprecated!' posts... -.- The same thing goes for things WE in Forge deprecate. Like non-stack sensitive versions of Item functions. You could still IMPLEMENT them and they would work fine{Because we are forced to be compatbile with vanilla}. But you should always CALL the non-deprecated form. The only difference between Mojang's @Deprecated and ours is that we can add comments directing you to the new stuff. Mojang can't as comments don't survive the compiling process.

You mean this?

Thread locked, and posting privileges removed for 24 hours. Don't remake the exact same thread after the first is locked. He also needs to learn the difference between a signature and post.

Update to 1.10.2.

Your axe is broken, fix it.

clean your cache and try again

Ugh I hate not having a test environment for these edge cases. Same thing, give 10 mins to build and try again.

Give it 10 mins and try again with --refresh-dependencies And let me know if it works. Tried to cleanup some code related to macs but dont have a test.

Do not mod for 1.7.10.