OpenRCT2 / OpenRCT2/OpenRCT2

Feature Request: More Granular Permissions

Open
#7,866 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
C++
Stars
16.2k
Forks
1.9k
Avg merge
1d 20h
Merged PRs (30d)
80

Description

I feel it would be very beneficial for all server providers if we could have finer control over permissions in game. For example, we currently only have the "Guest" and "Staff" permissions, but it would be beneficial if we could restrict groups to only having the ability to move guests/staff and hire/fire or set patrols for staff, without granting the ability to name them.

Thanks!

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

No files or tests are named. Start by locating the existing Guest and Staff permission handling and map how moving, hiring, firing, patrol-setting, and naming are currently authorized. Done would require an agreed permission model and implementation with coverage for each proposed permission.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
authorization, game-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.