PeakShock

PeakShock is a mod for PEAK that connects supported shock devices (like PiShock and OpenShock) to in-game events. When you take damage or die in the game, your device will deliver a shock, adding a fun and challenging twist to your gameplay.

Features

• Triggers real shocks based on in-game events (player death, injury, and more)
• Supports PiShock and OpenShock platforms
• You can enable or disable specific damage types
• Highly configurable to match your preferences

PiShock Migration Notice

[!IMPORTANT] PiShock support now uses https://api.pishock.com and this is a breaking configuration change. If you use PiShock, you must update your config before the mod will work again.

[!WARNING] Old PiShock setup: ShareCode New PiShock setup: APIKey and ShockerId PiShock hardware must be flashed to V3 for the new API path to work.

[!NOTE] PiShock V3 documentation: https://docs.pishock.com/pishock/pishock-v3-documentation.html

PiShock's V3 documentation also points users to their Discord support if they need help with flashing or setup.

Getting Started

1. Install the mod using a mod manager or manually.
2. Run the game once with the mod installed. This will generate the config file: addzeey.PeakShock.cfg.
3. Configure your device and preferences:
   • You can edit the config file manually (look for addzeey.PeakShock.cfg in your config folder), or use your mod manager's config editor.
   • Make sure to set the correct shock platform (PiShock or OpenShock).
   • Enable or disable specific damage types as you like.
4. Play PEAK and enjoy the extra challenge!

Configuration File Explained

When you first run the game with PeakShock installed, a config file named addzeey.PeakShock.cfg will be generated in your config folder. This file controls how the mod interacts with your shock device and lets you customize your experience.

All available config options:

• Shock Platform

  • Provider: Choose which device to use (PiShock or OpenShock).

• PiShock Settings

  • ApiUrl: PiShock API URL (default: https://api.pishock.com).
  • APIKey: Your PiShock API Key.
  • ShockerId: Your PiShock shocker id.

• PiShock Setup Notes

  • ShareCode is no longer used by PeakShock.
  • ShockerId is now required because the PiShock API no longer accepts the old do.pishock.com share-code flow.
  • PeakShock now sends a fixed PiShock AgentName of PeakShock Mod.
  • If ShockerId is missing or wrong, PeakShock logs the lookup URL https://pishock-lookup.addzeey.com/ to help users find it.
  • If PiShock returns a V3-related error, this means you need to flash / update pishock to v3 ( check pishock discord or their docuyemantion for instructions)

• OpenShock Settings

  • ApiUrl: OpenShock API URL (default: https://api.openshock.app).
  • DeviceId: Your OpenShock Device ID.
  • ApiKey: Your OpenShock API Key.

• Shock Intensity and Timing

  • MinShock: Minimum shock intensity (1-100).
  • MaxShock: Maximum shock intensity (1-100).
  • DeathShock: Shock intensity on death (1-100).
  • DeathDuration: Shock duration on death (seconds).
  • ShockCooldownSeconds: Minimum seconds between shocks (prevents shock spam).
  • ShockWhilePassedOut: Allow enabled status types to shock while passed out (default: disabled).

• Shock Triggers

  • EnableInjuryShock: Enable shock for Injury damage.
  • EnablePoisonShock: Enable shock for Poison damage.
  • EnableColdShock: Enable shock for Cold damage.
  • EnableHotShock: Enable shock for Hot/Fire damage.
  • EnableSporesShock: Enable shock when spore infection increases.
  • EnableThornsShock: Enable shock when a thorn becomes lodged in the player.
  • EnableWebShock: Enable shock for Web/Spider web.
  • EnableArrowShock: Enable shock when an arrow becomes lodged in the player.
  • EnablePetrifyShock: Enable shock when petrification increases.
  • EnableFlyTrapShock: Enable shock when caught by a Venus fly trap.

You can edit this file manually with a text editor, or use your mod manager's config editor if available. Always save your changes before restarting the game.

If you have questions about a specific setting, check the comments in the config file or ask in the mod's support channels.

Safety Notice

Use shock devices responsibly. Start with low settings and stop if you feel uncomfortable or take breaks.

Warning

Do not share config files, as these will have your own private api keys in for the shock device platforms!

Changelog

[0.4.1] - 2026-09-23

Fixed

• Updated PiShock shock requests to the documented POST /Shockers/OperateById/{ShockerId} endpoint

[0.4.0] - 2026-08-14

Added

• Added configurable shock triggers for Arrow, Petrify, and FlyTrap status increases
• Added an missing optional Spores shock trigger
• Added requested shock while passed out, disabled by default

Fixed

• Fixed thorn shocks
• Kept small-damage accumulation separate per status type to prevent unrelated damage types combining into one shock
• Gave death shocks an independent cooldown so a recent status shock cannot suppress death punishment

[0.3.0] - 2026-04-09

Breaking Changes

• PiShock support has been migrated from the legacy https://do.pishock.com flow to https://api.pishock.com
• PiShock users must update their config from the old ShareCode setup to the new APIKey and ShockerId setup
• PiShock V3 firmware is now required for the supported API shock path

Note

• Sorry this update took so long. PiShock's API docs were not updated when the old endpoint was removed, so I had to track the migration details down through their Discord before I could ship a proper fix.

Changed

• PiShock shock requests now target POST /Shockers/{ShockerId} on api.pishock.com
• PiShock requests now send only the required X-PiShock-Api-Key header
• PiShock requests now use a fixed AgentName of PeakShock Mod
• PiShock duration values are now sent in milliseconds to match the current API
• PiShock request logging now includes clearer request context without relying on the legacy share code flow

Added

• Added the PiShock.ShockerId config option
• Added PiShock error messages for important API failure cases such as non-V3 hardware, paused shares, invalid intensity, invalid duration, and missing shocker access
• Added a temporary shocker-id lookup URL to the log when PiShock configuration is incomplete or the configured ShockerId is invalid
• Added PiShock V3 documentation guidance in the project docs so users know where to go for reflashing and Discord support

[0.2.1] - 2026-03-04

Fixed

• Fixed false shock triggers caused by Hunger/Stamina ticks accumulating and eventually crossing the damage threshold

[0.1.6] - 2025-02-07

Fixed

• Fixed compatibility with latest PEAK game update ( as of 7th February )
• Updated CharacterAfflictions.AddStatus patch to handle new bool return type
• Fixed issue where shocks weren't triggering due to method signature changes

Added

• Added support for 2 new affliction types:
  • Thorns damage (EnableThornsShock)
  • Web/Spider web (EnableWebShock)
• Added "Name" field to PiShock API requests for better logging

Note

Apologies for the delay in getting this update out - life got in the way. Thank you for your patience!

[0.1.5] - 2025-07-04

Added

• Fixed ghost shocks when lobby is using a mod that ups player limit and other players can share the players name.

[0.1.4] - 2025-07-04

Added

• Added mod source and github repo link to package

[0.1.3] - 2025-07-02

Added

• Initial release of PeakShock for PEAK.
• Connects PiShock and OpenShock devices to in-game events.
• Shocks on player death, injury, and other configurable triggers.
• Config file generation and support for manual or mod manager editing.
• Option to enable/disable specific damage types.