Ok, so this may be a dumb question, but I can't seem to get a variable I need to change and save it. Basically I want a variable to go up by one with each shiftclick until it reaches a max value, after which it goes back to the base value of zero. I've initialized the variable as "int mode = 0;" and within an if statement

if(entityplayer.isSneaking()){
			if(mode < MAX){
				mode = mode + 1;
				System.out.println("Current Mode: " + mode);
				mode = mode + 1;
			}
			if(mode == MAX){
				mode = mode - mode;
				System.out.println("Current Mode: " + mode);
			}
		}
		else if(!entityplayer.isSneaking()){
			modes(mode, world, x,y,z, entityplayer);
		}

 

I am probably missing something simple...

Ok, so how would I go about doing that exactly? This is for an item that can change modes to be specific.

 

 

 

ItemStack#stackTagCompound is an NBTagCompound attached to the ItemStacks. store your stuff in there.

Umm.... Ok, but how do I use that?

Currently I have "NBTTagCompound mode = itemstack.stackTagCompound;" is that the right idea, or am I wrong?

Ok, first that field can be null, in that case you'll have to initialize it with a new compound. Then yes, it is the right idea. Store your data in that NBT.

Ok, I'm confused... How is it done,

Like how do I initialize it with a new compound, like do I do this

@Override
 public boolean onItemUse(ItemStack itemstack, EntityPlayer entityplayer, World world, int x, int y, int z, int par7, float par8, float par9, float par10)
    {
	Block block = world.getBlock(x, y, z);
	int meta = world.getBlockMetadata(x, y, z);
	int mode = 0;
	int MAX = 3;
	NBTTagCompound test = itemstack.stackTagCompound;
	test.setInteger("mode", mode);

Either way it makes little sense

Ok, thank you, now it works, but now I have a small issue, when it reaches the MAX variable it's supposed to reset mode to zero, which it does, but it seems to make it skip the mode I have set for the MAX. Full code needed:

@Override
 public boolean onItemUse(ItemStack itemstack, EntityPlayer entityplayer, World world, int x, int y, int z, int par7, float par8, float par9, float par10)
    {

	Block block = world.getBlock(x, y, z);
	int meta = world.getBlockMetadata(x, y, z);
	final int MAX = 3;
	if(itemstack.stackTagCompound == null){
		itemstack.stackTagCompound = new NBTTagCompound();
	}
	int mode = itemstack.stackTagCompound.getInteger("plantmo.mode");

	if (!world.isRemote)
	{
		if(entityplayer.isSneaking()){
			if(mode < MAX){
				mode = mode + 1;
				System.out.println("Current Mode: " + mode);

			}
			if(mode == MAX){
				mode = 0;
				System.out.println("Current Mode: " + mode);

			}

		}
		else if(!entityplayer.isSneaking()){
			modes(mode, world, x,y,z, entityplayer);
		}
	}
	itemstack.stackTagCompound.setInteger("plantmo.mode", mode);

		return false;
	}

 public void modes(int mode, World world, int x, int y, int z, EntityPlayer entityplayer) {
	Block block = world.getBlock(x, y, z);
	String blockname = block.getUnlocalizedName();
	int blockID = block.getIdFromBlock(block);
	int metadata = world.getBlockMetadata(x, y, z);

	switch(mode){
		case 0:
			System.out.println(blockname + " " + blockID + ":" + metadata);
			break;
		case 1:
			System.out.println("test");
			break;
		case 2:
			System.out.println("test2");
			break;
		case 3:
			System.out.println("test3");
			break;
		default:
			break;
	}

}

Ok, now I have changed it to check if mode > MAX, and now it doesn't seem to set mode = 0.

Ok.... That simplifies it greatly, why'd I have to forget that. Well, better than the long code I had before, though I did have to make it check if it was equal, instead of greater. Think it was because I had some code I didn't need.

mode = (mode + 1) % max

 

has the same effect, but is much shorter and more readable IMO. It's just a modulo (remainder) operation, which wraps around.