Instance setup warns that everyone is blocked when whitelist is disabled
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 74/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- frontend
Research direction
Search the dashboard source for the two literal strings quoted in the issue ("Whitelist inactive" and "Anyone will be blocked until added to the whitelist") to find the World Settings step component that renders both. Read how the whitelist-enabled flag and the empty player list are combined there, then make the empty-list wording conditional on the whitelist being enabled. Done means the panel reproduces correctly at 1280×800 with the whitelist disabled, and the copy only warns about blocking when the whitelist is on.
Written by the indexing model from the issue text.
Description
Steps to reproduce
- Open Add Instance, enter a name, and select Next.
- In World Settings, leave the Server Whitelist disabled and the player list empty.
- Read the status and empty-list message.
Actual
The panel says “Whitelist inactive” but also says “Anyone will be blocked until added to the whitelist.”
Expected
Explain that the empty list blocks players only while the whitelist is enabled; when disabled, it does not restrict access.
Observed in the isolated v0.5.0 dashboard at 1280×800.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 0
- Avg merge
- 13h 12m
- Merged PRs (30d)
- 57
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Isopod-Project/Isopod
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Isopod-Project/Isopod#220 ·
Maintainers usually reply within 1 day
-
Dashboard drives high GPU usage while a server starts or restartsPossibly taken @tacoz234 claimed this 12 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Isopod-Project/Isopod#191 · 1 comment ·
Maintainers usually reply within 1 day
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Isopod-Project/Isopod#134 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Isopod-Project/Isopod#113 ·
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Isopod-Project/Isopod#110 ·
Maintainers usually reply within 1 day
All issues in Isopod-Project/Isopod
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
hemilabs/ui-monorepo#2711 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
code-yeongyu/senpi#6929 ·
Maintainers usually reply within 1 day
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 72/100
lingdojo/kana-dojo#34261 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
embedpdf/embed-pdf-viewer#1116 ·
Maintainers usually reply within 1 day
-
current task
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Sunday-School-Software/Sunday-School-Scheduler#87 ·
Maintainers usually reply within 1 day