Super Battle Shock

Super Battle Shock connects local Super Battle Golf hits, knockouts, timeouts, and eliminations to supported shock devices such as PiShock and OpenShock.

Only your local player can trigger the mod. Other players do not need it installed.

Features

• Supports PiShock V3 and OpenShock.
• Configurable trigger mode for every supported hit-event.
• Separate intensity and duration groups for clubs, weapons, explosions, and vehicles.
• Optional timeout, unmapped knockout, water, and fog shocks.
• Local overlay, local chat-feed, or log-only notifications.
• Configurable cooldown and lobby protection to prevent unwanted shock spam.

Requirements

• Super Battle Golf.
• BepInExPack 5.4.2305 or newer. A mod manager installs this dependency automatically.
• A configured PiShock V3 or OpenShock device is required only when sending physical shocks.

Quick Start

1. Install Super Battle Shock with Gale, r2modman, or another Thunderstore-compatible mod manager.
2. Launch Super Battle Golf once to create BepInEx/config/com.github.addzeey.SbgShock.cfg in the active profile.
3. Open the config through your mod manager or a text editor.
4. Set Shock Provider to PiShock or OpenShock.
5. Add the credentials for that provider.
6. Start with low intensity and short duration values.

Provider Setup

Shock Provider defaults to PiShock. Change it to OpenShock when using an OpenShock device.

PiShock

IMPORTANT PiShock support uses https://api.pishock.com. PiShock hardware must be flashed to V3 for this API path to work.

Configure these values under [PiShock]:

The old ShareCode setup is not supported. PiShock users need an ApiKey and ShockerId.

• PiShock V3 documentation
• Shocker ID lookup

OpenShock

Configure these values under [OpenShock]:

Create an API token and copy the appropriate device or share ID from your OpenShock account.

Hit Trigger Modes

Every supported hit-event family has a HitMode setting. Related variants share the same setting.

Orbital laser center, thunderstorm direct-hit, and railgun direct-hit eliminations also use their matching hit-mode settings.

Hit Events

All listed hit modes default to KnockoutOnly.

Deflected pistol and elephant-gun shots use their matching weapon settings. Reflected rockets use RocketHitMode. Protected and giant-form railgun, orbital-laser, and thunderstorm variants use their matching settings.

GolfBallHitMode covers balls launched at players by a club and balls redirected by an Electromagnet shield. It does not include harmless slow ball contact or a player's own returned ball.

Electromagnet shield explosions are received through the game's knockout path and use ElectromagnetExplosionHitMode.

Configured intensity is sent exactly after clamping to 1-100. Hit force and distance do not increase it.

Timeout, Knockout, And Elimination Events

Water and fog elimination shocks fire when the same local player enters Respawn, before any configured delay and before teleport. Other elimination causes are ignored unless they have a dedicated hit setting.

Lobby Protection And Cooldown

• EnableShocksInLobby=false suppresses all shock triggers in the multiplayer Driving Range waiting lobby. Set it to true only if lobby hits should trigger shocks.
• ShockCooldownSeconds sets the minimum delay between outgoing requests, defaults to 2 seconds, and accepts 0-60. Set it to 0 to disable the cooldown.
• Most dispatcher and configuration skips are written to BepInEx/LogOutput.log.
• ShowSkippedNotifications defaults to false. Set it to true to show supported skip notifications in-game.

Notifications

Notifications.DisplayMode accepts:

Detailed provider, request, cooldown, and HTTP diagnostics remain in BepInEx/LogOutput.log.

Notifications.DurationSeconds controls how long overlay notifications remain visible. It defaults to 4 seconds and accepts 1-15. This setting does not affect chat-feed messages.

Request Safeguards

• Repeated triggers for the same event are deduplicated for 750 milliseconds.
• Only one provider request can be outstanding. New requests are skipped instead of building a stale backlog.
• Provider HTTP requests time out after 10 seconds.
• Missing credentials use dry-run behavior and do not enter the provider request queue or cooldown.

Safety And Privacy

Super Battle Shock controls physical hardware. Use it responsibly, follow the device manufacturer's safety guidance, start with low intensity and short duration, and stop immediately if you feel uncomfortable.

• Use only with the informed consent of everyone involved.
• The mod clamps intensity to 1-100 and duration to 1-15 seconds, but device or share limits may be lower.
• Do not share your config file. It contains private API credentials that can control your device.
• Super Battle Shock is provided as-is. You are responsible for your device configuration and use.