PuppyClicker for Minecraft connects Minecraft 1.21.1 to your PuppyClicker account.

Send a self-click using a configurable keybind, or craft multiple Puppy Clicker items and bind each one to a different accepted PuppyClicker friend or "pet". Carry individually named clickers in your hotbar and choose exactly who receives each click.

Every outgoing action requires deliberate player input.

Features

Send a self-click with a configurable keybind, set to P by default.
Enter and validate your PuppyClicker API key through the in-game Mods configuration screen.
Retrieve the accepted friends associated with your PuppyClicker account.
Craft multiple Puppy Clicker items.
Bind each clicker to a different friend or "pet".
Rebind an existing clicker by sneaking while using it.
Display success, credential, rate-limit, HTTP and network feedback above the hotbar.
Send API requests asynchronously without blocking Minecraft's render thread.
Prevent overlapping requests and apply a local cooldown.
Honour PuppyClicker's Retry-After response when rate limited.

Configure your account

Open:

Mods → PuppyClicker for Minecraft → Config

Enter your PuppyClicker API key into the masked field and select Validate & Save. The mod validates the credential with PuppyClicker before saving it.

The self-click key can be changed under:

Options → Controls → Key Binds → PuppyClicker

Friend-bound clickers

Craft a Puppy Clicker using:

One stone button
One iron nugget
One piece of redstone

The ingredients can be placed in any arrangement.

Interaction	Result
Right-click an unbound clicker	Open the accepted-friend picker
Right-click a bound clicker	Send a click to the selected friend
Sneak and right-click a bound clicker	Choose a different friend

Each clicker stores the selected friend's display name and public PuppyClicker identifier. This lets several clickers coexist in the same inventory, each targeting a different person.

Confirmation and feedback

Successful clicks produce concise action-bar feedback in Minecraft.

PuppyClicker will record the resulting action in the recipient's activity history:

Depending on the recipient's PuppyClicker settings, the service can also display its own notification:

Requirements and compatibility

Minecraft 1.21.1 exactly
NeoForge 21.1.243 or newer within the 21.1.x release line
Java 21
A PuppyClicker account
A personal PuppyClicker API key beginning with pak_
The mod installed on both the Minecraft client and server

This release is not compatible with Minecraft 1.21.2 or later. Those Minecraft versions require separately compiled and tested releases.

The server installation is required for the custom item and its synchronised per-stack binding data. The Minecraft server does not receive your PuppyClicker API key and does not connect to the PuppyClicker API.

Installation

Install Minecraft 1.21.1 and a compatible NeoForge 21.1.x release.
Download the PuppyClicker mod JAR.
Place the JAR in the mods directory on both the Minecraft client and server.
Start Minecraft and open the mod's Config screen.
Enter and validate your PuppyClicker API key.
Use the P keybind for self-clicks or craft clickers for individual friends.

Privacy and informed consent

The mod makes HTTPS requests to puppyclicker-api.boundfire.com for the following purposes:

Validate the supplied API key.
Retrieve the account's accepted friends.
Send deliberate self-clicks.
Send deliberate direct clicks to a selected friend.

The API key:

Remains in the client configuration.
Is sent only to the PuppyClicker API.
Is not sent to the Minecraft server.
Is not stored in clicker items.
Is not embedded in the mod.
Is not intentionally written to logs.
Is masked in the configuration screen and omitted from screen-reader narration.

The key is stored as plain text in the local Minecraft configuration file:

config/puppyclicker-client.toml

Treat this file as a credential. Do not share it, upload it or commit it to source control.

A bound clicker contains the selected friend's public PuppyClicker identifier and display name. Because Minecraft synchronises item data, that binding information is visible to the Minecraft server.

No damage, death, combat or other automatic gameplay event sends a click. The mod does not perform OpenShock or other physical-device integration actions. Every outgoing PuppyClicker action requires an explicit keypress or clicker-item interaction.