IntellectualSites / IntellectualSites/PlotSquared

Player names should be case-insensitive

Open
#3,448 8 comments 9 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Enhancement
Dominant language
Java
Stars
653
Forks
975
Avg merge
2m
Merged PRs (30d)
6

Description

What feature do you want to see added?

When a player writes /p v Notch then it should give the same result as /p v notch or /p v nOtCh (when you are quite adventurous).
But now only /p v Notch would work.

Are there any alternatives?

Write the user names in case-sensitive.

Anything else?

Even though this is not the most important thing (as autocomplete exists) it can be sometimes quite annoying when the player names are case sensitive in commands like /plot visit <Name>.
Then it says that the player does not exist even though the user is typing the "correct" name.

Many other plugins are very generous on how they are treating their names in the commands (sometimes even so much that you can write Notc and it would still find Notch) and so it can be sometimes very confusing for users that these things are quite different.

And Minecraft does not allow multiple names that are basically the same, but only the casing is different.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing how the /p v and /plot visit commands resolve player names. Check the lookup behavior for exact casing and compare it with Minecraft's restriction against names differing only by case. Done means valid player names return the same result regardless of casing, with appropriate tests covering Notch, notch, and nOtCh.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
game-dev
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.