Choosing a Stamina Store

SHS does not invent its own stamina bar. It spends and restores one store at a time:

Store	Install	Owns max / native regen
MMOCore	MMOCore + MythicLib	Class stats (MAX_STAMINA, STA_REGEN)
MythicRPG	MythicRPG (+ Mythic if required)	Pack reagent (default name Stamina)

Hard depend: SoapsCommon only. You need at least one store enabled or SHS stays red.

Who owns what

Owns	Plugin
Current and max stamina	MMOCore or MythicRPG
When play spends or restores that bar	SHS
Weight, hunger, HUD, abilities	SHS

SHS changes the current value. It does not replace max, classes, reagents, or skill systems.

	MMOCore	MythicRPG
Bar	MMOCore stamina	Configured Mythic reagent
Pause native regen while busy?	Yes (optional)	No
RPG combat tag for SHS?	Yes (optional)	No

Full setup: MMOCore Setup · MythicRPG Setup

Pick the provider

When both stores are installed, set integration.stamina-provider:

Value	Behavior
auto	MMOCore if enabled, else MythicRPG
mmocore	Always MMOCore
mythicrpg	Always MythicRPG

Changing the provider needs a full server restart. Reagent name changes apply on /shs reload.

Method	Example
GUI	/shs gui → Features → Integrations → Stamina provider
Toggle	/shs toggle stamina-provider
Config	/shs config set integration stamina-provider mythicrpg

Soft dependencies

Plugin	Role
PlaceholderAPI	%shs_*% placeholders
MMOItems	Weights and attack costs (MMOCore provider)
ExecutableItems / EcoItems	Custom weights
MythicCrucible	Weights and attack costs
WorldGuard	Region flag soaps-stamina

Integration keys

integration:
  stamina-provider: auto
  mmocore:
    use-combat-state: true
    activity-regen-scale: 0.9
    block-native-regen-while-active: true
  mythicrpg:
    reagent: Stamina
  worldguard:
    enabled: true

Full file: Default config.yml

Verify

Check	Passes when
Startup	Console shows stamina=mmocore or stamina=mythicrpg
/stamina	Non-zero max after join
Sprint	Number goes down
Skill / profession cost (if used)	Same /stamina number goes down
Empty bar	Sprint lock / cast fail feel on together

See also: Getting Started · Upgrading to 1.1.6