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.

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] Add /ban and /banip as built-in commands #43

Open
wu-vincent opened this issue Sep 1, 2024 · 1 comment
Open

[feature] Add /ban and /banip as built-in commands #43

wu-vincent opened this issue Sep 1, 2024 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@wu-vincent
Copy link
Member

Is your feature request related to a problem? Please describe.
Currently, the /ban and /banip commands are missing from the default command set in BDS.

Describe the solution you'd like

  1. Implement the /ban and /banip commands to ban online players.
  2. Add the ability to ban offline players who have previously joined the server.

Additional context
BDS stores player data using their UUID as the key in leveldb with the prefix player_. To be able to ban offline players by name, we need to maintain a mapping between player names and their UUIDs. This mapping should be stored in a separate file, which should be updated each time a player joins the server. In Bukkit, a similar file called usercache.json exists so we could potentially use a similar format.

Once we have access to player data from leveldb using the username, we will also need to store additional data (e.g., last seen IP address). This could be stored in an additional compound tag, possibly named endstone.

@wu-vincent wu-vincent added the enhancement New feature or request label Sep 1, 2024
@wu-vincent wu-vincent added this to the v0.5.3 milestone Sep 1, 2024
@wu-vincent wu-vincent self-assigned this Sep 1, 2024
@EndstoneMC EndstoneMC deleted a comment Sep 1, 2024
@wu-vincent wu-vincent modified the milestones: v0.5.3, v0.5.4 Sep 11, 2024
@wu-vincent wu-vincent removed this from the v0.5.4 milestone Sep 19, 2024
Copy link
Contributor

This issue has been automatically marked as stale because it did not have recent activity. It will be closed in 7 days if no further activity occurs. If you wish not to mark it as stale, please leave a comment in this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant