/**
* Register the mod entity type with FML
* @param entityClass The entity class
* @param entityName A unique name for the entity
* @param id A mod specific ID for the entity
* @param mod The mod
* @param trackingRange The range at which MC will send tracking updates
* @param updateFrequency The frequency of tracking updates
* @param sendsVelocityUpdates Whether to send velocity information packets as well
*/
public static void registerModEntity(Class<? extends Entity> entityClass, String entityName, int id, Object mod, int trackingRange, int updateFrequency, boolean sendsVelocityUpdates)
{
instance().doModEntityRegistration(entityClass, entityName, id, mod, trackingRange, updateFrequency, sendsVelocityUpdates);
}
Humm humm yes that is SOOOOOO FUCKING CONFUSING!!!!!
Note what it says about the id:MOD SPECIFIC ID
Cuz you know.. id conflicts between mods are stupid and shouldnt happen. Hence Mod specific...
Either way, don't be a fucking cunt. The id issue isnt OUR issue. It's a Minecraft issue that we have had resolved for ages.
The ONLY reason the global ID BS is there is for MODLOADER compatibility and it's going aweay in 1.7