/hunger command treats second argument as both player and value.

[James103]

It appears that when the /hunger command is used with two arguments, the second argument is treated as both the player and the value. This causes the command to break if used with two arguments, effectively preventing it from being used this way. The wiki lists the command syntax to be /hunger [player] <value>, but /hunger <value> works and sets the hunger value for the executor.

This behavior is caused by the following code:

AppleCore/java/squeek/applecore/commands/CommandHunger.java

Lines 43 to 45 in 2dbabf1

	EntityPlayerMP playerToActOn = args.length >= 2 ? getPlayer(server, commandSender, args[1]) : getCommandSenderAsPlayer(commandSender);
	int maxHunger = AppleCoreAPI.accessor.getMaxHunger(playerToActOn);
	int newHunger = args.length >= 2 ? parseInt(args[1], 0, maxHunger) : parseInt(args[0], 0, maxHunger);

The fix is as simple as changing the first args[1] on line 43 of the above code to args[0].