[Feature]: Assetto server instancing for ./serverfiles/cfg/entry_list.ini
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- bash
- Domain
- cli
Research direction
The issue identifies serverfiles/cfg/entry_list.ini and serverfiles/cfg/acserver.cfg, but says the relevant implementation location was not found. Start by tracing how LinuxGSM locates and instances acserver.cfg, then check the Assetto Corsa start flow and related tests. Done when each instance loads its matching suffixed entry list, with coverage for multiple instance numbers.
Written by the indexing model from the issue text.
Description
Priority
priority: high
User story
i want instanced entry_list.ini (ex: entry_list-6.ini) so i can host servers with different car layouts
Game
Assetto Corsa
Linux distro
Other
Command
command: start
Problem statement
entry_list.ini defines the cars used, and in which spawn positions. this file is required for server config, but shared between instances. half the config is done in acserver.cfg, the other half is in entry_list.ini. currently acserver.cfg is instanced, but entry_list.ini is not instanced, and thus acserver-6 will reference the same entry_list.ini as acserver-3, meaning you are unable to host servers with different car selections. This causes issues if you want to host different performance brackets, or different server types like drift vs track racing. Additionally, it causes issues in some maps where there is only 2 or 4 spawn points, so a server can then spawn you inside walls and break the game.
Scope and impact
scope: single game
Further information
making ./serverfiles/cfg/entry_list.ini have instancing similar/identical to ./serverfiles/cfg/acserver.cfg where it appends -2 -3 -4 etc to the filename, and loads its respective matching number suffix would resolve this entirely.
Alternatives considered
I would write the PR myself, but i was unable to find a location where the edit should be made. I searched with find -type f -exec grep -lr "entry_list" {} \; | grep -v "log" and only found the elf binary or exe files.
- Dominant language
- Shell
- Stars
- 4.9k
- Forks
- 866
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 100
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No 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 GameServerManagers/LinuxGSM
-
command: update-lgsm distro: Debian engine: source2 game: Counter-Strike 2 regression: yes reproducible: always severity: low type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
GameServerManagers/LinuxGSM#5242 ·
Maintainers usually reply within 1 day
-
distro: Debian distro: Ubuntu engine: spark game: Natural Selection 2 priority: high scope: single game type: feature
Difficulty 4/5 3-5 days Newbie friendliness 45/100
GameServerManagers/LinuxGSM#5241 ·
Maintainers usually reply within 1 day
-
command: send distro: Ubuntu engine: spark game: Natural Selection 2 priority: high scope: single game type: feature
Difficulty 4/5 3-5 days Newbie friendliness 48/100
GameServerManagers/LinuxGSM#5240 ·
Maintainers usually reply within 1 day
-
command: monitor distro: Ubuntu engine: spark game: Natural Selection 2 info: query reproducible: unable severity: critical type: bug
Difficulty 3/5 1-2 days Newbie friendliness 35/100
GameServerManagers/LinuxGSM#5238 ·
Maintainers usually reply within 1 day
-
engine: null game: Teamspeak 3
Difficulty 3/5 Half a day Newbie friendliness 66/100
GameServerManagers/LinuxGSM#5237 ·
Maintainers usually reply within 1 day
All issues in GameServerManagers/LinuxGSM
Similar issues
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
varnish/helm-varnish#173 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
📦 Update Request
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
cdnjs/packages#2225 · 1 comment ·
Maintainers usually reply within 3 days
-
good first issue help wanted testing
Difficulty 1/5 Under an hour Newbie friendliness 78/100