1.4.2 item slot already occupied

[pitman-87]

Forge: 6.0.1.339

 

When I'm using config files, all my itemIDs are over 31000, but I didn't give them such high values. This causes that many Items of my mods have the same ID from the config files, while I actually was using different IDs.

 

Code:

public static int itemIDSentryRed = 2820;
public static int itemIDSentryBlue = 2824;
public static int itemIDSentryBase = 2825;
public static int itemIDSentryHead = 2826;
public static int itemIDMonitor = 2821;
public static int itemIDWrench = 2822;
public static int itemIDGoldenWrench = 2823;

.....

@PreInit
public void preInit(FMLPreInitializationEvent event)
{
	proxy.preInit();

	Configuration configuration = new Configuration(event.getSuggestedConfigurationFile());
	try
	{
		configuration.load();
		Property prop;
		prop = configuration.getItem("itemIDSentryRed", 2820);
		itemIDSentryRed = prop.getInt(2820);
		prop = configuration.getItem("itemIDSentryBlue", 2824);
		itemIDSentryBlue = prop.getInt(2824);
		prop = configuration.getItem("itemIDSentryBase", 2825);
		itemIDSentryBase = prop.getInt(2825);
		prop = configuration.getItem("itemIDSentryHead",  2826);
		itemIDSentryHead = prop.getInt(2826);
		prop = configuration.getItem("itemIDMonitor",  2821);
		itemIDMonitor = prop.getInt(2821);
		prop = configuration.getItem("itemIDWrench", 2822);
		itemIDWrench = prop.getInt(2822);
		prop = configuration.getItem("itemIDGoldenWrench",  2823);
		itemIDGoldenWrench = prop.getInt(2823);
		prop = configuration.get( configuration.CATEGORY_GENERAL,"shootVolume", "0.2");
		prop.comment = "min: 0.0	max 1.0";
		shootVolume = Float.valueOf(prop.value).floatValue();
		prop = configuration.get(configuration.CATEGORY_GENERAL, "spotVolume", "0.2");
		prop.comment = "min: 0.0	max 1.0";
		spotVolume = Float.valueOf(prop.value).floatValue();
		prop = configuration.get(configuration.CATEGORY_GENERAL, "explosionVolume", "0.5");
		prop.comment = "min: 0.0	max 1.0";
		explosionVolume = Float.valueOf(prop.value).floatValue();
		prop = configuration.get(configuration.CATEGORY_GENERAL,"upgradeVolume",  "0.3");
		prop.comment = "min: 0.0	max 1.0";
		upgradeVolume = Float.valueOf(prop.value).floatValue();
		prop = configuration.get(configuration.CATEGORY_GENERAL,"opsOnly",  false);
		prop.comment = "Set to true, if only OPs are allowed to change the targets!";
		opsOnly = prop.getBoolean(false);
	} catch (Exception e)
	{
		FMLLog.log(Level.SEVERE, e, "TF2 Sentry has a problem loading it's configuration");
		FMLLog.severe(e.getMessage());

	} finally
	{
		configuration.save();
	}
}

 

generated config:

# Configuration file
# Generated on 28.10.12 18:02

####################
# general 
####################

general {
   # min: 0.0	max 1.0
   explosionVolume=0.5
   # Set to true, if only OPs are allowed to change the targets!
   opsOnly=false
   # min: 0.0	max 1.0
   shootVolume=0.2
   # min: 0.0	max 1.0
   spotVolume=0.2
   # min: 0.0	max 1.0
   upgradeVolume=0.3
}

####################
# item 
####################

item {
   itemIDGoldenWrench=31706
   itemIDMonitor=31708
   itemIDSentryBase=31710
   itemIDSentryBlue=31711
   itemIDSentryHead=31709
   itemIDSentryRed=31712
   itemIDWrench=31707
}

 

Only happens on Items,but  Blocks and other values are working fine.

I'm not sure if this is a bug or I missed something 

[HMPerson1]

Modded item ids must start above 4096, otherwise they'll coincide with ItemBlock ids.

When you use configuration.getItem(), if the default below 4096, it'll auto-assign it somewhere in the 31000's.

[pitman-87]

Ok thats new thx