New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Enhanced Idle Disconnects #701

Closed
Antrare opened this Issue Mar 11, 2015 · 5 comments

Comments

4 participants
@Antrare

Antrare commented Mar 11, 2015

Idle Disconnects currently appear to disconnect all connected characters over time x (specified in settings file)

We should expand this functionality to include the following:

  • Bots (such as IRC-Bot) should never be idle disconnected
  • Respect Locks i.e. Immortals shouldn't be disconnected, players should get y time, builders x...
@Pinacolada64

This comment has been minimized.

Show comment
Hide comment
@Pinacolada64

Pinacolada64 Aug 13, 2017

I am staff, and our 5h idle timeout shouldn't affect me. Our IRC bot keeps being affected by this. We have to restart it manually each time.

Pinacolada64 commented Aug 13, 2017

I am staff, and our 5h idle timeout shouldn't affect me. Our IRC bot keeps being affected by this. We have to restart it manually each time.

@tricuspa

This comment has been minimized.

Show comment
Hide comment
@tricuspa

tricuspa Aug 15, 2017

What is the challenge behind getting this particular issue resolved? Could it be resolved with another class or flag (no_idle_Timeout)?

tricuspa commented Aug 15, 2017

What is the challenge behind getting this particular issue resolved? Could it be resolved with another class or flag (no_idle_Timeout)?

@Griatch

This comment has been minimized.

Show comment
Hide comment
@Griatch

Griatch Aug 16, 2017

Member

The fix needs to go into the core maintenance task of Evennia, which is responsible for the timeout. It's not difficult (implementation has just been put back for more pressing matters a few times), but it requires some design desicions. The most likely implementation would be to have the task check a lock on the object to determine if it should time out or not.

Member

Griatch commented Aug 16, 2017

The fix needs to go into the core maintenance task of Evennia, which is responsible for the timeout. It's not difficult (implementation has just been put back for more pressing matters a few times), but it requires some design desicions. The most likely implementation would be to have the task check a lock on the object to determine if it should time out or not.

@Griatch Griatch added this to In progress on devel branch in Evennia 0.7 Aug 20, 2017

@Griatch Griatch moved this from In progress on devel branch to Done on devel branch in Evennia 0.7 Aug 20, 2017

@Griatch Griatch added the implemented label Aug 20, 2017

@Griatch

This comment has been minimized.

Show comment
Hide comment
@Griatch

Griatch Aug 20, 2017

Member

This was implemented in devel branch and will merge with Evennia 0.7.

Member

Griatch commented Aug 20, 2017

This was implemented in devel branch and will merge with Evennia 0.7.

@tricuspa

This comment has been minimized.

Show comment
Hide comment
@tricuspa

tricuspa Sep 3, 2017

Thank you so much, the additions should be very helpful!

tricuspa commented Sep 3, 2017

Thank you so much, the additions should be very helpful!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment