Skip to content

A NestJS, Domain-Driven Design reimplementation of Halo 3's web services.

Notifications You must be signed in to change notification settings

LeRutY/Sunrise-Halo3-WebServices

 
 

Repository files navigation

hero

Halo 3 Web Services Build status

This api contains a rough reimplementation of all of Halo 3's web services including support for

  • Matchmaking
  • File Share
  • Bungie Favourites
  • Bungie Pro
  • Banhammer
  • Active Transfer
  • Service Records
  • MOTDs
  • Screenshots
  • Nameplates
  • Crash Reporting
  • Webstats (needs a lot of work, see #4)

and much more :)

These web services were created for the retail version of Halo 3 for the Xbox 360. However, most builds of Halo 3 should be supported. PC builds, if they were to somehow connect, do use the same endpoints, leaked pre-release builds for the 360 however do not, though the changes are probably minor. The beta should also be supported.

This project is built for use with Sunrise-Plugin, a dashlaunch plugin which connects Xbox 360 Halo 3 to a custom webserver.

Preparing the project

  1. Install dependencies with the npm install command.
  2. Create a .env file in the project root, following this structure:
  API_PORT=8080
  MONGO_URI=
  1. Build the web service with the npm run build command.

Handling Title Storage (Playlists/MOTDs/More)

This API is setup to serve "title storage" files, however these files are not included. Back in the day, Bungie had a bunch of tooling including big ass spreadsheets and debug game builds to spit out these files, these days we have a tool to generate everything we need from JSON called Sunrise-BLFTool.

There are a few options for content.

  1. Grab my recommended title storage files from the Sunrise-Content repository.
  2. Fork the Sunrise-Content repository and roll your own.
  3. Grab Gamecheat13's backup of the OG title storage before the servers were shutdown.
  • Please note, this backup is slighlty corrupt (bad hash on network_configuration) which does cause some notable bugs, I recommend against this generally.

Once you've got the files you need, they live in public/storage/title

Running the app

# development
$ npm run start

# watch mode
$ npm run start:dev

# production mode
$ npm run start:prod

Last Updated 05/09/22 by Codie Stella 🐧

About

A NestJS, Domain-Driven Design reimplementation of Halo 3's web services.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • TypeScript 97.6%
  • PowerShell 2.0%
  • JavaScript 0.4%