#510 Auto Away after X Minutes

Murmur (113)

Description: An option for a server admin to set an amount of time that after not inputting for this length the user is then marked as AFK. The admin can then select to perform a variety of options on an away player such as moving to an Away channel, muting/deafening.

The idea has been proposed before I'd like to request it once again for the following reasons:
1) Saves server resources if you deafen/mute players
2) Allows others to see that you have not performed input for X minutes.

Now from my understanding this has not been implemented because someone may be watching a movie and be "unfairly" marked as AFK. However, I don't see this as a problem(and am sure many others would agree). If someone has been watching a movie without giving input for longer than allowed by the server, then they probably won't mind being temporarily deafened/muted. After all, they can still be reached by using text messages. Servers with infinite bandwidth allocation may have no problem with not deafening the users but for the rest of us its a waste of a precious resource. I believe its something that should be automated by mumble to allow admins this option(even if its off by default).


  • Senve

    Senve - 2009-11-16

    This would be a very good feature. Theres a lot of idle users on big channels on my server eating my bandwidth.

    Some ACLs added to this feature would be nice too. For example an @away group and ability to choose from which channels you get auto-moved etc etc

  • Stefan H.

    Stefan H. - 2009-11-30

    There's a client-side feature that allows this. But I guess you want it to be controllable server-side?

    It should be pretty straight forward to use our RPC interface (Ice) to implement such a thing. The user structure contains a value idlesec which can be used to determine how long the user has been idle. A bot could poll this in regular intervals and just mute& deafen users over a certain threshold.

  • Brentmeister

    Brentmeister - 2009-11-30

    I'll take a look at Ice and let you know what I think. However, it might be clearer and easier for your average server admin to simply set a time and channel in the .ini file.

  • Comment has been marked as spam. 

    You can see all pending comments posted by this user  here

    Anonymous - 2010-01-18

    I was searching for this feature and I was actually surprised that it hasn't been added to Murmur already. I would definitely like to be able to see if someone is AFK or not. Whether it is by the user having some sort of AFK icon, or being moved to an AFK channel (that's how they do it at ventrilo and I simply love that feature). I am hoping for this feature to be added to Mumble. But until that time, I'll be forced to ask everyone to go to the AFK channel themselves.

    Don't get me wrong, I love Mumble, and I am extremely grateful to everyone involved in this project. Thanks =)

  • Stefan H.

    Stefan H. - 2010-02-03

    As stated before we don't think such functionality belongs into the core of Murmur as we want to keep it as simple as possible.

    However it is possible to do this over our Ice RPC interface. We currently have two sample scripts which are able to perform such a task:
    Mumble moderator (http://gitorious.org/mumble-scripts/mumble-scripts/trees/master/Bots/mumo) and idle.php (http://mumble.git.sourceforge.net/git/gitweb.cgi?p=mumble/mumble;a=blob_plain;f=scripts/idle.php).

    Since we only recently made changes to the idle counter these scripts will work best when using a Murmur version > 1.2.1 and might show erratic behaviour otherwise.

  • Comment has been marked as spam. 

    You can see all pending comments posted by this user  here

    Anonymous - 2011-08-22

    You can not do this with an ICE server. I've tried. The clients actual idle time is not exposed to the server in any way I can find. "idlesec" only shows how long someone has last interacted with the murmur server, not their actual desktop idle time.

    All you can do is move/mute anyone that hasnt said anything or moved channels in X amount of minutes. They could be sitting at their computer just waiting for someone to talk, or possibly only there to listen due to not having a working mic. They'll get moved.

    What people want is to auto-mute and move people that are actually afk-- As in, hasn't moved their mouse or touched their keyboard in a long enough period.

    I think the best way to do this would be to just have a server setting of what to do after a user has been idle for $x minutes, with the options of mute/deafen, kick, move to specified channel.

    Failing that, at least update mumble to pull actual idle time via GetLastInputInfo() (http://msdn.microsoft.com/en-us/library/ms646302.aspx) and the other platforms equivalents so that I can write an ICE script to do actual afk management.

    Last edit: Anonymous 2016-01-28
  • VDV

    VDV - 2014-08-26

    I'm still following all tickets related to this feature.
    It has been requested by many users over many years (since 2008), in many tickets (1035, 634, 998, 932, 870, 702, 531, 243).

    I gave numerous examples regarding how community managers can implement neat features based on idle time. This is not limited to AFK stuff.
    It will also be fair to people without mics (or physically mute...), fair to server hosting (no bandwidth consumption from people leaving their computer with mumble running), and could enable great features for ICE developpers (I have a php/ICE script to reward people connecting with others (hours/week) and monitoring how long someone wait for another user to join, but it's nearly useless without a proper idle timer).

    The feature is so important to me that I wrote a personnal email to mumble's developpers (and I was so sorry about this invasion and was so ashamed after their answer that I didn't even replied...).
    I'm still desperatly hoping for this, reading feature requests to bring my humble "+1" (I'm not creating new tickets anymore).



Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks