Skip to content

Change autoproxy latch scope from global to per-server and implement unlatch on double-backslash#18

Open
northperseids wants to merge 4 commits intoNinty9:mainfrom
northperseids:main
Open

Change autoproxy latch scope from global to per-server and implement unlatch on double-backslash#18
northperseids wants to merge 4 commits intoNinty9:mainfrom
northperseids:main

Conversation

@northperseids
Copy link

Issues


Description

If a user's mode is latch for a given server, adds the proxier ID in the user's "auto" settings (along with the existing autoproxy mode and server ID for that server). The autoproxy handling now pulls from that proxier ID entry instead of reshuffling the member list. Users with existing latch server settings but no associated proxier ID yet should just need to proxy once as usual to start the latch.

Small edit to the rk;auto latch function itself that should properly set autoproxy for groups as well as servers (the autoproxy var previously was only set if the channel type was a server text channel).

Double-backslash sets the proxier ID for the given server to None and does not change the latch mode.

Also updated README/help text wherever it mentioned the previous global latch.

@Nidoskull Nidoskull requested a review from Ninty9 February 12, 2026 20:19
@Ninty9
Copy link
Owner

Ninty9 commented Feb 13, 2026

testing this (: ty for the pr

update: nvm stoat is dying so i cant test rn

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments