Heroic Games Launcher•3y ago

Discord RPC not working

I have it enabled but even though it is enabled it doesn't show up on Discord when I launch a game. I am running Mint with KDE.

54 Replies

wise-whiteOP•3y ago

PS: please ping me if you decide to reply, it'll make sure I will be able to be here ASAP

fascinating-indigo•3y ago

Please provide general logs of this process. Read the pinned message to know how to provide general logs

wise-whiteOP•3y ago

hi, thanks for replying. I am now having 2 issues, bioshock refuses to boot and the RPC still doesn't show even though it shows up in the logs? https://paste.ee/p/ZtWwR

Paste.ee

View Paste ZtWwR

Paste.ee - View Paste ZtWwR

wise-whiteOP•3y ago

I have fixed the crashing issue, by changing some stuff related to my drivers however the discord RPC is still not showing up, here is the log:

message.txt

afraid-scarlet•3y ago

this can be due to flatpak permissions

wise-whiteOP•3y ago

how would I be able to check it and or fix it?

afraid-scarlet•3y ago

also if you are using Discord from flatpak the socket is created in different place https://github.com/flathub/com.discordapp.Discord/wiki/Rich-Precense-(discord-rpc)

GitHub

Rich Precense (discord rpc)

Contribute to flathub/com.discordapp.Discord development by creating an account on GitHub.

wise-whiteOP•3y ago

is there any way to check if I have it from flatpak

afraid-scarlet•3y ago

$ flatpak list | grep Discord

wise-whiteOP•3y ago

fascinating-indigo•3y ago

I tested here on main branhc It seems that either the client id we use got incorrect or the discord-rich-presence-typescript npm pacakge stopped working

wise-whiteOP•3y ago

ah so it's currently a problem for everyone?

fascinating-indigo•3y ago

Probably for evveryone that is using this npm package But i am not sure. The guy who insert it is not part of heroic anymore Don't know how to get the correct client id

wise-whiteOP•3y ago

client id on discord dev panel? or what exactly do you mean

fascinating-indigo•3y ago

No clue

wise-whiteOP•3y ago

cause for a client id in discord's dev panel you need to make an app and stuff

afraid-scarlet•3y ago

just create a app on discord dev portal

wise-whiteOP•3y ago

yeah that

fascinating-indigo•3y ago

So could be that the client id is invalid Can someone create a new one. I have no experience eith discord

wise-whiteOP•3y ago

idk if it counts but I could if you want 💀

fascinating-indigo•3y ago

Where is our heroic discord app stored? ok found it Id is still the same. So i would argue that the npm package is broken.

wise-whiteOP•3y ago

you can test it by making a test app theoretically

fascinating-indigo•3y ago

The test app is heroic. If it does not work with heroic i would say it does not work with another app aswell There is not alot of code for this feature

function constructAndUpdateRPC(gameName: string): RpcClient {
  const client = makeClient('852942976564723722')
  client.updatePresence({
    details: gameName,
    instance: true,
    largeImageKey: 'icon',
    large_text: gameName,
    startTimestamp: Date.now(),
    state: 'via Heroic on ' + getFormattedOsName()
  })
  return client
}

function constructAndUpdateRPC(gameName: string): RpcClient {
  const client = makeClient('852942976564723722')
  client.updatePresence({
    details: gameName,
    instance: true,
    largeImageKey: 'icon',
    large_text: gameName,
    startTimestamp: Date.now(),
    state: 'via Heroic on ' + getFormattedOsName()
  })
  return client
}

Thats all

wise-whiteOP•3y ago

it indeed is an issue with your package I'm able to use that ID to create an RPC with a python script

fascinating-indigo•3y ago

The package was not updateded for 2 years ...

wise-whiteOP•3y ago

then that's why

fascinating-indigo•3y ago

I will try something tomorrow Updating the dependencies of this package might help

wise-whiteOP•3y ago

what about using another package with the same functions

fascinating-indigo•3y ago

Is there one?

wise-whiteOP•3y ago

idk, I'm not familiar with the language you guys are using for it looks like js though? maybe I'm wrong

fascinating-indigo•3y ago

Typescript

wise-whiteOP•3y ago

there seem to be a bunch

fascinating-indigo•3y ago

Ah discord-rpc has type support The package we use using discord-rpc So probably we need to update the dependecies

wise-whiteOP•3y ago

if it would fix the issue then that's the way to go xd

evolutionary-blush•3y ago

For me it never worked for the flatpak version We should try using a different package or a different system See, for me it's working fine on MACOS Flatpak is a different world, this type of thing requires more work there

wise-whiteOP•3y ago

I'm not using flatpak discord

evolutionary-blush•3y ago

Flatpak heroic I mean

wise-whiteOP•3y ago

ah right

fascinating-indigo•3y ago

i think could be a problem of the package we use. It is not updated for years Even the base npm package is 2 years old Ok the python discord-rpc was updated 3 years ago So maybe not a problem of the package

wise-whiteOP•3y ago

Hmmmm

fascinating-indigo•3y ago

Which python lib you used?

wise-whiteOP•3y ago

https://pypi.org/project/discord-rpc.py/

PyPI

discord-rpc.py

A Discord Rich Presence library for Python 2 & 3

fascinating-indigo•3y ago

Last release was 16. Dez. 2019 So might be not a pacakge problem Intresting. It seems the client instance is empty:

RP {
  _events: [Object: null prototype] {},
  _eventsCount: 0,
  _maxListeners: undefined,
  [Symbol(kCapture)]: false
}

RP {
  _events: [Object: null prototype] {},
  _eventsCount: 0,
  _maxListeners: undefined,
  [Symbol(kCapture)]: false
}

Found the error:

(node:25647) UnhandledPromiseRejectionWarning: Error: Could not connect
    at Socket.onerror (/home/niklas/Repository/discord-rich-presence/node_modules/discord-rpc/src/transports/ipc.js:32:16)
    at Object.onceWrapper (node:events:628:26)
    at Socket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:157:8)
    at emitErrorCloseNT (node:internal/streams/destroy:122:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:83:21)

(node:25647) UnhandledPromiseRejectionWarning: Error: Could not connect
    at Socket.onerror (/home/niklas/Repository/discord-rich-presence/node_modules/discord-rpc/src/transports/ipc.js:32:16)
    at Object.onceWrapper (node:events:628:26)
    at Socket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:157:8)
    at emitErrorCloseNT (node:internal/streams/destroy:122:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:83:21)

afraid-scarlet•3y ago

. probably related if the socket doesn't exist in expected location

fascinating-indigo•3y ago

OK so it sounds like that discord flatpak and heroic if flatpak needs to be adapted

fascinating-indigo•3y ago

So we need to update heroic flatpak with this: https://github.com/flathub/com.discordapp.Discord/wiki/Rich-Precense-(discord-rpc)#flatpak-applications

GitHub

Rich Precense (discord rpc)

Contribute to flathub/com.discordapp.Discord development by creating an account on GitHub.

fascinating-indigo•3y ago

For everythig else people need to fix it by thereselfs

fascinating-indigo•3y ago

https://github.com/flathub/com.discordapp.Discord/wiki/Rich-Precense-(discord-rpc)#unsandboxed-applications

GitHub

Rich Precense (discord rpc)

Contribute to flathub/com.discordapp.Discord development by creating an account on GitHub.

fascinating-indigo•3y ago

Ok yes that fixed it

wise-whiteOP•3y ago

Epic thank you!

fascinating-indigo•3y ago

Linguin already pointed it out. Just didn't saw the error the whole time 😄

wise-whiteOP•3y ago

great job on fixing it guys! it works well 🙂

Gaming

Programming

Discord RPC not working

Did you find this page helpful?