coilyco-flight-deck/infrastructure
2
0
Fork 0
Code Issues 118 Pull requests Projects Releases Packages Wiki Activity Actions 2

Host Vintage Story dedicated server (Eco-style community accretion experiment) #82

New issue
Closed
opened 2026-05-23 20:54:39 +00:00 by coilysiren · 1 comment
coilysiren commented 2026-05-23 20:54:39 +00:00
Owner
Copy link

Originally filed by @coilysiren on 2026-05-01T08:24:15Z - https://github.com/coilysiren/infrastructure/issues/78

Why

Closest analogue to Eco's community-accretion dynamic in any other game: small adult player base, official server list that people actually browse, multiplayer-first community on the official Discord, modded-server culture is alive. The plan is to recreate "host a server, randos show up, ~10% are cool and stick around, after a year you have a community."

Not on Steam. $20 direct from vintagestory.at.

What

Stand up a Vintage Story dedicated server somewhere on the homelab. Curate it with a clear theme (mod loadout + ruleset) so it stands out from vanilla servers. Post once on the official Discord and let it sit for a year.

Acceptance

  • Buy Vintage Story account ($20)
  • Container or systemd unit picked (official server is Mono-based, runs on Linux natively)
  • Persistent volume for world + mods
  • Mod loadout decided (Wildcraft, Medieval Expansion, XSkills, etc.)
  • Server theme + ruleset documented (PvE? RP? Hardcore? Tech-focused?)
  • Auto-restart + backup strategy
  • Tailscale or public IP exposure (probably public for the accretion play)
  • Listed on official server list
  • Discord posted in the official VS Discord with a server-info channel
  • Plan to revisit after 3 months and after 1 year

Open questions

  • Public IP vs. behind Tailscale (Eco-style requires public)
  • Whitelist vs. open (open is the accretion play)
  • Mod loadout direction: closer to vanilla (lower bar to entry) or themed-heavy (filters for the right players)
_Originally filed by @coilysiren on 2026-05-01T08:24:15Z - [https://github.com/coilysiren/infrastructure/issues/78](https://github.com/coilysiren/infrastructure/issues/78)_ ## Why Closest analogue to Eco's community-accretion dynamic in any other game: small adult player base, official server list that people actually browse, multiplayer-first community on the official Discord, modded-server culture is alive. The plan is to recreate "host a server, randos show up, ~10% are cool and stick around, after a year you have a community." Not on Steam. $20 direct from vintagestory.at. ## What Stand up a Vintage Story dedicated server somewhere on the homelab. Curate it with a clear theme (mod loadout + ruleset) so it stands out from vanilla servers. Post once on the official Discord and let it sit for a year. ## Acceptance - [ ] Buy Vintage Story account ($20) - [ ] Container or systemd unit picked (official server is Mono-based, runs on Linux natively) - [ ] Persistent volume for world + mods - [ ] Mod loadout decided (Wildcraft, Medieval Expansion, XSkills, etc.) - [ ] Server theme + ruleset documented (PvE? RP? Hardcore? Tech-focused?) - [ ] Auto-restart + backup strategy - [ ] Tailscale or public IP exposure (probably public for the accretion play) - [ ] Listed on official server list - [ ] Discord posted in the official VS Discord with a server-info channel - [ ] Plan to revisit after 3 months and after 1 year ## Open questions - Public IP vs. behind Tailscale (Eco-style requires public) - Whitelist vs. open (open is the accretion play) - Mod loadout direction: closer to vanilla (lower bar to entry) or themed-heavy (filters for the right players)
coilysiren commented 2026-05-30 05:43:20 +00:00
Author
Owner
Copy link

Iceboxed in the 2026-05-29 backlog burn-down: Vintage Story server community experiment. Reopen anytime if it becomes real.

Iceboxed in the 2026-05-29 backlog burn-down: Vintage Story server community experiment. Reopen anytime if it becomes real.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
issue-515
issue-486
issue-529
issue-500
issue-483
No results found.
Labels
Clear labels   
burndown-2026-06
Backlog burndown June 2026

  
coherence-core
Core review set for the warded control plane coherence milestone. These issues form the release spine; adjacent milestone issues are stretch or supporting work.

  
consult
A human decision, design, or external action must happen first. Fail-closed default for unlabeled/low-confidence.

  
headless
Agent can take it from open issue to merged change with no human in the loop. The auto-burndown queue.

  
interactive
Agent does the work but pauses at a human checkpoint mid-flight (design choice, destructive step, human-only verification).

  
P0
now / blocking / urgent

  
P1
next / important

  
P2
backlog / will do

  
P3
someday / low

  
P4
icebox / frozen / reopen if it becomes real

No labels
burndown-2026-06
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
coilyco-flight-deck/infrastructure#82
No description provided.