Problem Statement
Hi! First of all, thank you for open-sourcing this project — the documentation and tooling are excellent, and the SRE/sentinel work is genuinely impressive.
I'm a self-hoster trying to run the full stack locally, and I've hit a wall on the database side.
What I have / what works
- All 5 server executables (Center/Login/Game/Channel/Global) running locally with the repo's Lua/scripts layer applied
- Client connects and logs in fine (auto-login via launcher args)
database/*.sql patches from the repo apply cleanly on top of the schema
What's missing
The repository does not include the SQL Server backup files referenced by scripts/restore_db_tcp.py / restore-databases-native.ps1:
database/Account.bak
database/ES_BILLING.bak
database/Game01.bak
database/Statistics.bak
They are excluded via .gitignore (*.bak), and the only public release channel (manifest.onjoysword.top / the web portal /api/downloads) exposes just the client and launcher artifacts. I understand the "Code Overlay" design keeps the bulk workspace out of git — but without the database backups, self-hosters can't get the full experience (the CashShop economy, VIP/BattlePass systems, item catalogs, etc.), and the repo's own install-*.sql patches assume the shipped schema.
Proposed Solution
Would you be willing to share the database backups (or any other distribution channel for them) with self-hosters? Options that would work:
- Upload the 4
.bak files to the existing R2/manifest bucket (even as a separate "server" artifact)
- A link to a private/hosted copy (Dropbox/Google Drive/MEGA etc.)
- Any other distribution method you're comfortable with
Alternatives Considered
If sharing the full backups isn't possible, even a schema-only SQL dump (tables + stored procedures, no player data) would be a huge help — the biggest blocker right now is the item/cashshop data (e.g. EB_Product only has 96 rows vs. the 17,042+ mentioned in the README).
Problem Statement
Hi! First of all, thank you for open-sourcing this project — the documentation and tooling are excellent, and the SRE/sentinel work is genuinely impressive.
I'm a self-hoster trying to run the full stack locally, and I've hit a wall on the database side.
What I have / what works
database/*.sqlpatches from the repo apply cleanly on top of the schemaWhat's missing
The repository does not include the SQL Server backup files referenced by
scripts/restore_db_tcp.py/restore-databases-native.ps1:database/Account.bakdatabase/ES_BILLING.bakdatabase/Game01.bakdatabase/Statistics.bakThey are excluded via
.gitignore(*.bak), and the only public release channel (manifest.onjoysword.top/ the web portal/api/downloads) exposes just the client and launcher artifacts. I understand the "Code Overlay" design keeps the bulk workspace out of git — but without the database backups, self-hosters can't get the full experience (the CashShop economy, VIP/BattlePass systems, item catalogs, etc.), and the repo's owninstall-*.sqlpatches assume the shipped schema.Proposed Solution
Would you be willing to share the database backups (or any other distribution channel for them) with self-hosters? Options that would work:
.bakfiles to the existing R2/manifest bucket (even as a separate "server" artifact)Alternatives Considered
If sharing the full backups isn't possible, even a schema-only SQL dump (tables + stored procedures, no player data) would be a huge help — the biggest blocker right now is the item/cashshop data (e.g.
EB_Productonly has 96 rows vs. the 17,042+ mentioned in the README).