Fascinated/beatsaber-overlay
Fascinated/beatsaber-overlay
Archived
1
1
Fork 0
Code Issues 1 Pull Requests 2 Actions Packages Wiki Activity
BeatSaber Overlay with real-time data from HttpSiraStatus. Can also show stats from ScoreSaber and BeatLeader! https://bs-overlay.fascinated.cc/
This repository has been archived on 2023-11-06. You can view files and clone it, but cannot push or open issues or pull requests.
699 Commits 3 Branches 0 Tags 3.4 MiB
JavaScript 66.5%
TypeScript 27.9%
CSS 4.2%
Dockerfile 1.4%
0185a9ed3e
Go to file
Liam 0185a9ed3e silly mee
2023-10-31 11:44:50 +00:00
.gitea/workflows my dick is wet 2023-10-15 04:27:37 +01:00
assets update overlay img 2023-03-27 16:23:48 +01:00
public Remove __ENV.js 2022-10-29 13:29:59 +01:00
src fix proxy 2023-10-31 11:44:27 +00:00
.env-example silly mee 2023-10-31 11:44:50 +00:00
.eslintrc.json bump depends and fix building 2023-10-11 23:30:39 +01:00
.gitignore fix nextui depends 2023-10-15 03:44:06 +01:00
CODE_OF_CONDUCT.md Create CODE_OF_CONDUCT.md 2022-10-19 18:32:50 +01:00
docker-compose.yml update image location 2023-03-27 22:03:26 +01:00
Dockerfile hahaball 2023-10-15 04:30:41 +01:00
LICENSE Create LICENSE 2022-10-19 18:31:44 +01:00
next-env.d.ts TypeScript woop 2022-10-22 12:28:24 +01:00
next.config.js changed next config 2023-03-26 17:16:07 +01:00
package.json fix depends 2023-10-15 03:59:34 +01:00
pnpm-lock.yaml fix depends 2023-10-15 03:59:34 +01:00
README.md update depends 2023-04-09 17:06:20 +01:00
renovate.json chore(deps): add renovate.json 2023-10-15 01:45:56 +00:00
tsconfig.json maybe fix 2022-10-29 14:46:17 +01:00

README.md

BeatSaber Overlay with real-time data from HttpSiraStatus

The project is on my Gitea now, but the repo will be kept in sync on GitHub.
The public url to view/use: https://bs-overlay.fascinated.cc
Need help? Feel free to message me on Discord: Fascinated#7668 or Matrix: @fascinated:matrix.fascinated.cc

Usage

Go to the Wiki

Preview

Overlay Builder Menu

Getting started with developent

  • Clone the repo
  • Move into the cloned directory
  • Run npm install
  • Rename the .env-example to .env
  • Create a redis server with a password
  • Setup the .env
  • Run npm run dev
  • Open http://localhost:3000

If you want your changes to be in the main branch, feel free to open a pull request :)