For Developers
Respite publishes a stable integration surface under com.rfizzle.respite.api, per the suite API standard: read-only static accessors, array-backed Fabric events, server-authoritative.
Accessors
| Accessor | Returns |
|---|---|
getTimeLapseRate(ServerLevel) | Effective time-lapse rate for the level; 1 when inactive |
isTimeLapseActive(ServerLevel) | True while extra ticks are running |
getTicksSinceRest(ServerPlayer) | The player's time-since-rest in ticks |
isWeary(ServerPlayer) | True if the player currently has the Weary effect |
isExhausted(ServerPlayer) | True if the player currently has the Exhausted effect |
isWellRested(ServerPlayer) | True if the player currently has the Well-Rested effect |
getChronometerSignal(Level) | The Chronometer signal (1–15) for the level's day time; 0 in fixed-time dimensions |
Events
RespiteTimeLapseCallback— fires on every effective-rate change, including start and end, with sleeper counts.RespiteRestCallback— fires when a player wakes at dawn having slept, with ticks slept and health restored.
Consumption is the suite pattern: compile against the jar with modCompileOnly and guard every call site with FabricLoader.getInstance().isModLoaded("respite"). Respite ships no HUD element and therefore no HUD accessors.
Item IDs for integrations
Respite is a provider in every current suite integration — sibling mods reference these stable IDs from their own datapacks: respite:chronometer, respite:caffeinated_brew, respite:unsteeped_brew.