Report when live player permission changes fail to apply

Open
#224 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
docker, typescript
Domain
backend, databases

Research direction

Start by reading the related issues #135, #90, and #102, then trace the backend paths that send live permission commands to Java and Bedrock servers and inspect how their results are handled. Define saved, applied, pending, and failed states while preserving persisted permissions; add coverage for success, failure, timeout, recovery, and operator removal after restart on both server types. Update the wiki with pending states and recovery steps.

Written by the indexing model from the issue text.

Description

enhancement

What to build

Distinguish saved player permissions from permissions actually applied to a running Java or Bedrock server. Failed operator/allowlist synchronization must not be presented as fully applied.

Context

Follow-up to #135 and #90. Closed #102 fixed several frontend request errors, but not backend live permission-command results. This ticket does not assume an observed stale-operator incident.

This follows the November 17 source audit. Treat it as a hardening/validation task, not a confirmed exploit report. Detailed audit evidence and validation limitations remain in the local audit report; report any confirmed vulnerability privately under SECURITY.md.

Acceptance criteria

  • Check live RCON/Bedrock command results and return an actionable pending/failed state when synchronization fails.
  • Tell the user whether permissions were saved, applied live or still need retry/restart; preserve the intended persisted state.
  • Provide a safe retry/reconciliation path, and verify managed operator removal remains removed after restart.
  • Test successful application, command failure, timeout and recovery for both Java and Bedrock.
  • Update the wiki with pending permission states and recovery steps.

Blocked by

None (can start independently). Coordinate with related issues without expanding their scope.

Dominant language
TypeScript
Stars
1
Forks
0
Avg merge
13h 12m
Merged PRs (30d)
57

Getting set up

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.

More from Isopod-Project/Isopod

All issues in Isopod-Project/Isopod

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.