You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Let's say someone pings @first-respondR, the bot would check if the channel is occupied. If it's not, it will consider the channel to be occupied by the user that pinged @first-respondR. We'll make the occupied channel state last, let's say, 30 minutes. After that time, the channel will be freed. If a user pings @first-respondR while the channel is still occupied, it will pop up and say: "Sorry, this channel is currently occupied. Try another channel." or something of the sort.
The text was updated successfully, but these errors were encountered:
Thanks for opening @eshom. I was thinking something like this:
Have two separate Discord categories.
-- General R Help: Available
-- General R Help: Occupied
For the channels that are in General R Help: Available, a user can claim that particular channel by typing their question. After the question is posted, the channel is then moved to General R Help: Occupied.
The channel(s) in General R Help: Occupied will remain there until a certain threshold of inactivity is met, OR by invoking a command like $close or $end sending the channel back to the General R Help: Available category and also posting a message saying the is now available and perhaps a brief blurb on asking a proper question...
Let's say someone pings @first-respondR, the bot would check if the channel is occupied. If it's not, it will consider the channel to be occupied by the user that pinged @first-respondR. We'll make the occupied channel state last, let's say, 30 minutes. After that time, the channel will be freed. If a user pings @first-respondR while the channel is still occupied, it will pop up and say: "Sorry, this channel is currently occupied. Try another channel." or something of the sort.
The text was updated successfully, but these errors were encountered: