#status disappearing
21 messages · Page 1 of 1 (latest)
do you show any data that needs to be anyhow updated?
no one really looks therr anyway, if you update it every hour it's going to be absolutely enough
not to sure why this is happening, i have a setInterval for every 10000ms and i have no clue when it stops but it does, has anyone else had this issue? i am using pm2 so i cant really look back at the console to see if there is an error
Thats spamming the API too quickly. If you left your presence alone it'd be far less likely to disappear honestly
alright
you can absolutely look back at the logs with pm2
by default pm2 saves both stdout and stderr to log files. you can just do pm2 logs <process>, eventually adding --lines <number> to change how many it shows. or you can use pm2 info <process> to see where are the logs located and go from there
@hollow hawk ping for visibility
p sure pm2 automatically stores log files in ~/.pm2 as well
that is what i said
This has been happening to mine as well (and it updates every 15 minutes). I set a "default" value on the ClientOptions#presence when instatiating it so that it falls back to it when this happens and doesn't just get unset. On the next loop's cycle it sets the presence again
I set a "default" value on the ClientOptions#presence when instatiating it so that it falls back to it when this happens and doesn't just get unset.
i don't think that's how that works, chief
Okay, how does it work?
Mhm, then I am confused as to why it's working for me
well, aren't you setting it every 15 minutes?
Yes, but sometimes it does not get updated (I'm not sure why) and sets the status used in the ClientOptions#presence
Then on the next loop it updates it again properly
I'm not saying that ClientOptions#presence is meant to be used as a "fall back" in this way but that is what's working out for me