Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[Feature Request]: Request to add feature enabling punishments scoped to certain servers. #146

Closed
1 task done
Kiran-GC opened this issue Mar 19, 2022 · 0 comments
Closed
1 task done

[Feature Request]: Request to add feature enabling punishments scoped to certain servers. #146

Kiran-GC opened this issue Mar 19, 2022 · 0 comments
Labels
feature New feature or request
Milestone
1.1.0

Comments

@Kiran-GC
Copy link

Kiran-GC commented Mar 19, 2022 •
edited

I have confirmed that ...

  • There is no duplicate feature request.

Description

Requesting the developers to add a feature to scope punishments to a specific server when the plugin is working on proxy. It is a good feature for servers that decides to limit its punishments to a single server. Command usage can be as follows:
/ban [Reason]: (Wud be good with tabcompletion)
Thanks!

And if no server was mentioned then it will ban the player on the server the staff executed the cmd on
@Kiran-GC Kiran-GC added the feature New feature or request label Mar 19, 2022
@A248 A248 added this to the 1.1.0 milestone Mar 21, 2022
@A248 A248 mentioned this issue Jul 22, 2022
Closed
14 tasks
A248 added a commit that referenced this issue Aug 18, 2023
@A248
Implement scoped punishments with complete API (#146)
a97dcce 
* Add a default punishing scope and allow it to be used everywhere
* Punishing and listing commands now accept scope arguments
  -server=<server>, -category=<category>, and -scope=<scope>
  where <scope> is of the form 'global', 'server:<server>', or
  'category:<category>'
* Increment database revision number. Keep compatibility with
  legacy scope field for now. Previously, this scope field was
  accessible via the API only.
* Detect server name scope using plugin messaging on Bukkit and
  Sponge. Rework some of the existing plugin messaging and move
  the 'kick-via-plugin-messaging' option to a better location.
* When running on a proxy, enforce server-scoped punishments on
  the server switch event. Add flag to disable this enforcement
  for performance reasons.
* Add documentation for server scopes.
A248 added a commit that referenced this issue Aug 19, 2023
@A248
Implement scoped punishments with complete API (#146)
c8af256 
* Add a default punishing scope and allow it to be used everywhere
* Punishing and listing commands now accept scope arguments
  -server=<server>, -category=<category>, and -scope=<scope>
  where <scope> is of the form 'global', 'server:<server>', or
  'category:<category>'
* Increment database revision number. Keep compatibility with
  legacy scope field for now. Previously, this scope field was
  accessible via the API only.
* Detect server name scope using plugin messaging on Bukkit and
  Sponge. Rework some of the existing plugin messaging and move
  the 'kick-via-plugin-messaging' option to a better location.
* When running on a proxy, enforce server-scoped punishments on
  the server switch event. Add flag to disable this enforcement
  for performance reasons.
* Add documentation for server scopes.
A248 added a commit that referenced this issue Sep 11, 2023
@A248
Implement scoped punishments with complete API (#146)
f38a6ae 
* Add a default punishing scope and allow it to be used everywhere
* Punishing and listing commands now accept scope arguments
  -server=<server>, -category=<category>, and -scope=<scope>
  where <scope> is of the form 'global', 'server:<server>', or
  'category:<category>'
* Increment database revision number. Keep compatibility with
  legacy scope field for now. Previously, this scope field was
  accessible via the API only.
* Detect server name scope using plugin messaging on Bukkit and
  Sponge. Rework some of the existing plugin messaging and move
  the 'kick-via-plugin-messaging' option to a better location.
  Add a security warning if option is improperly enabled.
* When running on a proxy, enforce server-scoped punishments on
  the server switch event. Add flag to disable this enforcement
  for performance reasons.
* Add documentation for server scopes. Update documentation on
  plugin comparisons.
A248 added a commit that referenced this issue Sep 12, 2023
@A248
Implement scoped punishments with complete API (#146)
94591a8 
* Add a default punishing scope and allow it to be used everywhere
* Punishing and listing commands now accept scope arguments
  -server=<server>, -category=<category>, and -scope=<scope>
  where <scope> is of the form 'global', 'server:<server>', or
  'category:<category>'
* Increment database revision number. Keep compatibility with
  legacy scope field for now. Previously, this scope field was
  accessible via the API only.
* Detect server name scope using plugin messaging on Bukkit and
  Sponge. Rework some of the existing plugin messaging and move
  the 'kick-via-plugin-messaging' option to a better location.
  Add a security warning if option is improperly enabled.
* When running on a proxy, enforce server-scoped punishments on
  the server switch event. Add flag to disable this enforcement
  for performance reasons.
* Add documentation for server scopes. Update documentation on
  plugin comparisons.
A248 added a commit that referenced this issue Sep 12, 2023
@A248
Implement scoped punishments with complete API (#146)
d300d00 
* Add a default punishing scope and allow it to be used everywhere
* Punishing and listing commands now accept scope arguments
  -server=<server>, -category=<category>, and -scope=<scope>
  where <scope> is of the form 'global', 'server:<server>', or
  'category:<category>'
* Increment database revision number. Keep compatibility with
  legacy scope field for now. Previously, this scope field was
  accessible via the API only.
* Detect server name scope using plugin messaging on Bukkit and
  Sponge. Rework some of the existing plugin messaging and move
  the 'kick-via-plugin-messaging' option to a better location.
  Add a security warning if option is improperly enabled.
* When running on a proxy, enforce server-scoped punishments on
  the server switch event. Add flag to disable this enforcement
  for performance reasons.
* Add documentation for server scopes. Update documentation on
  plugin comparisons.
A248 added a commit that referenced this issue Sep 12, 2023
@A248
Implement scoped punishments with complete API (#146)
235dace 
* Add a default punishing scope and allow it to be used everywhere
* Punishing and listing commands now accept scope arguments
  -server=<server>, -category=<category>, and -scope=<scope>
  where <scope> is of the form 'global', 'server:<server>', or
  'category:<category>'
* Increment database revision number. Keep compatibility with
  legacy scope field for now. Previously, this scope field was
  accessible via the API only.
* Detect server name scope using plugin messaging on Bukkit and
  Sponge. Rework some of the existing plugin messaging and move
  the 'kick-via-plugin-messaging' option to a better location.
  Add a security warning if option is improperly enabled.
* When running on a proxy, enforce server-scoped punishments on
  the server switch event. Add flag to disable this enforcement
  for performance reasons.
* Add documentation for server scopes. Update documentation on
  plugin comparisons.
@A248 A248 closed this as completed Sep 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature New feature or request
Projects
None yet
Milestone
1.1.0
Development

No branches or pull requests
2 participants
@A248 @Kiran-GC