Latest restricted WACUP beta release is build #19516 (June 27th 2024) (x86 & x64 changelogs) | Latest WACUP public preview is build #19516 (June 27th 2024) (x86 only)

NOTE: Beta testers are added in a limited & subjective manner as I can only support so many people as part of the beta test program to keep it useful for my needs.

Unless I think you're going to be helpful, not all requests will be accepted but might still be later on. Remember that beta testing is to help me & the limitations currently works for my needs for this project.

Author Topic: Discord RPC Plugin [rich presence]  (Read 856 times)


  • Newbie
  • *
  • Posts: 1
    • View Profile
Discord RPC Plugin [rich presence]
« on: May 24, 2024, 02:46:21 AM »
Wacup blocks the discord rpc plugin from winamp, if you would make it a feature into wacup would be awesome since is very comfy to use, also for adding some kind of detection like creating a button in the rpc with the link in case we loading music from a link, this would make people switch over wacup and give it more spread if people see you using wacup.

Or if is to much problem just add a button for not blocking specific plugins plz

Here is the repo:

Btw ty for bringing back this awesome music player, even tho I'm not from your gen I rly enjoy it over the new alternatives.

Eris Lund

  • The Skin Guy, Official Modern Skin tech support
  • Beta Tester
  • Hero Member
  • *****
  • Posts: 290
    • View Profile
    • Eris Lund's Github
Re: Discord RPC Plugin [rich presence]
« Reply #1 on: May 24, 2024, 07:10:39 AM »

The plugin is most likely being blocked because the Discord RPC support already exists
Maker of Plugins, I suppose.
(I know, creative names)


  • Admin / WACUP Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 4615
    • View Profile
    • WACUP (Winamp Community Update Project)
Re: Discord RPC Plugin [rich presence]
« Reply #2 on: May 24, 2024, 09:55:27 AM »
It's being blocked by filename as there were a number of cases of it crashing & users not updating to newer builds of it that fixed it iirc or there was conflict between the 2 plug-ins (mine & theirs) being enabled at the same time. So to avoid me being spammed / getting complaints when the issue was not on my side, it was added to the block list.

As I'm offering the feature natively (was part of WACUP before I was ever aware of the other plug-in) & it does everything afaict that plug-in was doing plus more (i.e. it has albumart support along with none of the faff in having to setup your own app id, etc), not allowing the other plug-in by filename in this instance doesn't seem like a bad thing to be doing.