Hearty Shank - yeelp/Scaling-Feast GitHub Wiki

The Hearty Shank is an edible item added by Scaling Feast used to increase a player's maximum hunger.

Obtaining

Crafting

Name	Ingredients	Recipe	Notes
Hearty Shank	Bone + Cooked Porkchop + Clownfish + Beetroot Soup + Rabbit Stew + Cake + Iron Apple		Can be mirrored

Generated Loot

Loot	Structure	Container	Quantity	Chance	Average Yield
Hearty Shank	Stronghold	Crossing Chest	1	20%	0.2

Usage

Food

Eating the Hearty Shank restores 4 () hunger and 6.4 () saturation (both are configurable). Upon consumption by the player, it increases that player's overall maximum hunger by a configurable amount (default 2 () hunger). The increase is applied on Scaling Feast's Max Hunger Attribute as an Attribute Modifier. The bonus to max hunger is first used to remove Death Penalty and Starvation Penalty modifiers first before being applied as a separate modifier, which is used to count towards configurable total Hearty Shank usage limit.

Crafting

Name	Ingredients	Recipe	Notes
Hearty Feast	6 Wheat + 2 Egg + Hearty Shank		—

Brewing

Name	Ingredients	Recipe	Potency	Duration
Metabolic Potion	Hearty Shank + Thick Potion		I	2:00

Details

The Hearty Shank has an item id of scalingfeast:heartyshank.

History

Version	Notes
1.0.0	Added
1.1.0	Hearty Shanks now have the ability to reset the Starvation Tracker independently of other food items
1.1.2	Hearty Shanks now respect Scaling Feast's global max hunger cap
1.2.0	With the introduction of Modules, the Hearty Shank can no have its max hunger increasing abilities disabled in the config
1.4.0	Hearty Shanks now show the amount of max hunger they give in the HUD when using the ADVANCED info overlay
1.7.0	Added the Hearty Shank Usage Ticker which tracks the amount of times a Hearty Shank was used increase max hunger, used in tandem with a configurable cap for how many times Hearty Shanks can increase max hunger
1.8.0	Switching to using just Attributes instead of Capabilities means the Hearty Shank Usage Ticker is obsolete. Hearty Shanks now apply a separate Attribute Modifier instead