OpenRA / OpenRA/OpenRA

Lock/customize server setting when running a server using the AppImage file

Open
#19,151 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Idea/Wishlist
Dominant language
C#
Stars
17.4k
Forks
3k
Avg merge
1d 12h
Merged PRs (30d)
14

Description

Motivation

Running an OpenRA server using the AppImages file (link) is ridiculously simple and requires almost zero setup.
The basic parameters are all exposed and can be customized as in the sample script (link). However, it's not possible to specify custom server settings (link).

Proposed solution

It would be great to allow specifying those setting somehow.
One idea would be adding another parameter to provide a folder where the server can read the custom rules. E.g Server.SettingsOverrideFolder="/tmp/customOraSettings/"

./OpenRA-Red-Alert-x86_64.AppImage --server Server.Name="My Server" Server.ListenPort=1234 Server.SettingsOverrideFolder="/tmp/customOraSettings/"

Side effects

The server should read and apply the rules stored in the yaml files in the target folder.

Alternatives

Any other solution along these lines is fine -- I don't know the code enough to understand if the suggested solution is reasonably simple or not 😁

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 with launch-dedicated.sh and the AppImage server invocation documented in the linked wiki pages, then trace how the --server arguments are handled. Determine how custom YAML rules in a supplied folder should be discovered and applied, and define tests or a documented server run that demonstrates the settings are locked and active.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.