Bug #597

User mode removal

Added by Lingerance over 7 years ago. Updated about 7 years ago.

Status:RejectedStart date:03/06/2009
Priority:NormalDue date:
Assignee:EgS% Done:


Category:Quassel Core
Target version:0.4.0
Version:0.4.0 OS:Any


User modes are removed when connecting to a server.

*** Mode Lingerance +xz by Lingerance
*** Mode Lingerance -x by Lingerance

The first line is actually the server setting the user mode, the second is Quassel removing +x (cloaking on SlashNet).


#1 Updated by EgS over 7 years ago

  • Status changed from New to Feedback
  • Assignee set to EgS

Quassel restores your old user modes during session restore. So unless you explicitly issued a mode -x in your last session, this is most likely due to upgrading from an older version that didnt have this feature.

Just set mode +x and everything will be fine in the future (even after core restarts).

Let me know if the issue still occurs.

#2 Updated by Lingerance over 7 years ago

Oh, that explains it, I did upgrade the core recently. So far I've been disconnected from SlashNet a few times since then (I had manually added the +x again) and haven't had the issue.

#3 Updated by EgS over 7 years ago

  • Status changed from Feedback to Rejected

thanks for the feedback.
In this case I think I can close the BR.

#4 Updated by Lingerance about 7 years ago

Actually, it did this again when I created a new server. This was from a recent git version (shortly after styling was merged).

#5 Updated by Lingerance about 7 years ago

Quassel will also remove +o after I've issued /oper for the same reason. I had the /oper statement in the "commands to execute on connect" box.

Also available in: Atom PDF