Make the Minecraft EULA an explicit checkbox when creating a server
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 57/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- docker, typescript
- Domain
- backend, full-stack
Research direction
Start in backend/main.py at create_instance, the import paths, and the config save path; then trace the create, import, and modpack forms. Check where the Bedrock terms are displayed and how existing servers load their EULA setting. Done when the required checkbox gates new server creation, accepted state is saved appropriately, config saves stop forcing acceptance, and existing servers still start as before.
Written by the indexing model from the issue text.
Description
Isopod sets EULA=TRUE on every new server without asking (create_instance and the import paths in backend/main.py, and it re-adds it on every config save). Players running a server have to agree to the Minecraft EULA themselves, so this should be an explicit choice.
Fix
- Add a required "I accept the Minecraft EULA" checkbox with a link to https://aka.ms/MinecraftEULA on the create, import, and modpack forms. Creating is disabled until it's ticked.
- Only write
EULA=TRUEwhen the user accepted it. Stop forcing it on config save. - Existing servers keep working: treat them as already accepted.
- Bedrock: show the equivalent notice for the Bedrock Dedicated Server terms.
Acceptance
- A new server can't be created without ticking the box.
- Existing servers start as before after the update.
- 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
-
Difficulty 1/5 Under an hour Newbie friendliness 74/100
Isopod-Project/Isopod#200 ·
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
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