Zaplink V2 (Beta) All About the Update

🚀 Background

Zaplink started as a quick personal script connecting Ko-fi tips to PiShock. No website, no accounts, no backend, just one user and one goal.

As interest grew, so did the project. A simple web app and basic config system followed, but the original setup wasn’t built to handle scale.

Zaplink V2 is a complete rebuild with user accounts, structured configs, and a real backend. It is designed for growth, security, and customization while staying fast and easy to use.

Whether you're just starting or coming back, V2 brings a cleaner UI, more safety, advanced config settings, and a stable experience built to grow with you.

🆕 What’s New

🔐 Authentication

In Zaplink V1, users were identified solely by a user ID provided at first configuration. This was intentionally simple— no login, no passwords, just configure your devices and start receiving shocks. While fast and frictionless, this approach came with long-term limitations:

  • No secure way to verify ownership: Anyone with your user ID could access or alter your configuration.
  • User IDs were unmemorable: Users often lost access and created new configs instead of recovering their existing one.
  • Duplicate configs flooded the database, making management difficult.

With V2, we've introduced traditional authentication. You can now register with an email and password, then log in with either your email or username to manage your settings securely.

🧾 Legacy User Upgrades

If you previously used Zaplink V1 and still have your user ID, you can upgrade your setup into a full V2 account by verifying your PiShock username and ID. All your config data will transfer over seamlessly.

🌐 Public Profiles

Every V2 user can optionally enable a public profile, showing your username, bio, social links, and tipping thresholds. Built for easy sharing and ideal for creators and users on Ko-fi, VRChat, Twitch or anywhere else.

⚡Tipping Thresholds (Rebuilt)

We know that having just one or two tipping thresholds was pretty limiting for a while, so with V2, you can now set up to 10 custom thresholds*, each with:

  • Custom labels
  • Shocker codes
  • Duration and intensities, or randomized ranges
  • Minimum and maximum tip amounts

Everything is fully editable at any time, with import and export support for quick changes.

🎲 Randomization

To make shocks more interesting, you can now define a range for durations and intensities. Zaplink then randomly selects a duration and intensity within that range for each shock, making every zap unique and unpredictable. Great for creators and users who want to surprise themselves and their audience. (This feature is strictly subject to Section 3 of our Terms of Service)

🧠 UI/UX Improvements

  • Cleaner layout with consistent styling
  • Responsive across mobile, tablet, and desktop
  • Smarter form validation & feedback
  • Improved modals and animations
  • Token/API key visibility toggles

🛠 Quality of Life Improvements

  • Zap Key Regeneration: You can now regenerate your Zap Key directly from your account page. This is especially useful if your old Key was ever exposed.
  • Shocker Config Import/Export: You can now export your shocker configurations in JSON format or import them back anytime. Perfect for backups or sharing setups.
  • Tip Fallback System: A new fallback feature ensures that tips exceeding your highest configured range still trigger the top threshold.
  • New Navbar: V2 introduces a brand new dynamic navbar with context-aware links. It shows or hides elements depending on whether you're logged in and includes direct access to your dashboard, account, and public profile.
  • STOP Button: A bright red STOP button is now part of the navbar. It lets you instantly cancel any queued shock with a single click. It also deactivates the integration to prevent any further shocks until re-enabled.

⚠️ What to Expect

Zaplink V2 is fully functional but still marked as beta. That means everything should work, though you might still run into weird edge cases, broken links, or hiccups as we roll things out and collect feedback.

If you hit a bug or something doesn’t behave right, please report it by contacting us at contact@zaplink.cloud. We’re actively improving the platform based on your feedback. Thanks for helping us make Zaplink even better.

Here are a few known or possible edge cases to keep in mind:

  • Multiple Ko-fi donations in quick succession may occasionally result in missed shocks
  • Minor delays in shock delivery may occur as the new scheduling system continues to be fine-tuned
  • Rare frontend glitches may appear due to uncaught UI exceptions, though they won’t affect core functionality