tkuraczyk/BanHammer
1
0
Fork 0
Code Issues 3 Pull requests Projects Releases 1 Packages Wiki Activity Actions

Current kick player after ban logic is invalid #6

New issue
Closed
opened 2026-02-26 19:21:44 +01:00 by tkuraczyk · 4 comments
tkuraczyk commented 2026-02-26 19:21:44 +01:00 (Migrated from gitlab.kuraczyk.net)
Copy link

When player banned from server A when admin is on server B, which shall be supported by this plugin, Player would not get kicked as plugin instance on server B is currently trying to do so instead of instance A. What i suggest is registered async job which would run every 1 second which checks if in postgresql table called kick_jobs is active scheduled job for current server instance.

OFC if anyone has better solution, don't hesitate to share it in comments to this issue.

When player banned from server A when admin is on server B, which shall be supported by this plugin, Player would not get kicked as plugin instance on server B is currently trying to do so instead of instance A. What i suggest is registered async job which would run every 1 second which checks if in postgresql table called `kick_jobs` is active scheduled job for current server instance. OFC if anyone has better solution, don't hesitate to share it in comments to this issue.
tkuraczyk commented 2026-03-11 09:30:59 +01:00 (Migrated from gitlab.kuraczyk.net)
Copy link

There is something in postgresql called "LISTEN". Probably using that for sending json containing proper ban info would be the wisest course of action.

There is something in postgresql called "LISTEN". Probably using that for sending json containing proper ban info would be the wisest course of action.
tkuraczyk commented 2026-03-17 20:32:31 +01:00 (Migrated from gitlab.kuraczyk.net)
Copy link

mentioned in commit 18cf76ae7f

mentioned in commit 18cf76ae7fde2b859b7fd540243392f3080632f6
tkuraczyk (Migrated from gitlab.kuraczyk.net) closed this issue 2026-03-17 20:33:10 +01:00
tkuraczyk commented 2026-03-17 20:33:12 +01:00 (Migrated from gitlab.kuraczyk.net)
Copy link

Resolved in commit 18cf76ae

Resolved in commit 18cf76ae
tkuraczyk commented 2026-03-17 20:35:27 +01:00 (Migrated from gitlab.kuraczyk.net)
Copy link

mentioned in merge request !2

mentioned in merge request !2
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
stable
dev
1.0
Labels
Clear labels   
Urgent
No labels
Urgent
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: tkuraczyk/BanHammer#6
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?