.getStacksize() seems to always return maxStacksize, rather than the actual size of the measured stack.

nobotious · Oct 28th 2016

holding stone and running the following:

player.getEquippedItem().getStacksize();

returns 64 (stone max stack size)

also, with a torch in hand, it will return 8 (torch max stack size)

seems to be returning what the max stacksize is I.E. what .getMaxStacksize() should be.

red51 · Oct 29th 2016

That's a bug, thanks for letting us know, it will be fixed with the next update (in a few days)

nobotious · Oct 29th 2016

thanks red!

nobotious · Nov 3rd 2016

not sure its an error on my end now, but it seems to still be returning max stack size. (done after the 11/2/2016 bugfix)

method i made up to get a total count of an item in a players inventory:

Code

public static int itemCount(Player player, int itemid){
		int count = 0;
		Item[] items = player.getInventory().getItems(SlotType.Inventory);
		for(int i = 0; i < items.length; i++) {
			if(items[i] != null) {
				if(items[i].getTypeID() == itemid) {
				count = count + items[i].getStacksize();
				//player.sendTextMessage("Count is: " + count);
				}
			}
		}
		return count;
	}

Display More

red51 · Nov 3rd 2016

Well, this is a perfect example of how not to do it: Apparently the bug isn't fixed I mean, I swear it was fixed, but somehow this minor change was reverted accidentally with the latest bugfix X/
Are you developing your plugin in singleplayer or on a multiplayer server? Are you planning to release your plugin shortly? This change requires an update of the server, we want to avoid that (or at least wait if there might be another update necessary in the next days), however, we can release an updated client (and if you're working with the server, an updated server as well), but it would be an optional update (so if you release your plugin before the next update is available, it might not work for everybody)

zfoxfire · Nov 3rd 2016

Red,
Check your local copy. Did you push after the commit? ;-p

red51 · Nov 3rd 2016

There was neither a push nor a commit between the main update and the small bugfix shortly afterwards (usually I do these things after the updates, after responding in the forums etc., once there is enough time). However, it was my fault that the change was reverted.

nobotious · Nov 3rd 2016

i'm in no rush to release my plugin, just wanted to make sure the bug was still on the board :P. just been doing testing in singleplayer.
appreciate all your hard work!

honestly for now, its not an issue with the rest of my development lol, would just introduce an exploit if i were to release it (at this moment).

red51 · Nov 3rd 2016

Okay, I released a small clientside update in Steam (maybe you have to restart Steam in order to get the update), it should work properly now

zfoxfire · Nov 3rd 2016

oh ok, I was just meaning that as a joke regardless. I do that too on occasion myself.

Miwarre · Nov 3rd 2016

Who didn't forget a push or even a commit some time? Let him be the first to cast a byte...

(cast to what?)

zfoxfire · Nov 4th 2016

What would Jesus the Mexican programmer do? Cast the bytes to wine.

Participate now!