- Community Discord
- A C# Server Program, that responds to client requests for NHL 10 clients
- A C# Server Program, that responds to client requests for NHL 11 clients
- A C# Server Program, that responds to client requests for NHL 12-Legacy clients
- Subproject implementing ultimate team features
- Subproject implementing NHL specific components
- A Separate redirector instance.
- Redirecting clients to the right servers
- Needed because games listen on the same redirector port
- SDK (a Framework) made by @Aim4kill
- Used by Zamboni to respond to client using a said protocol
- Minor changes made to it to make it compatible
- A QoS Server made by @Hall of Meat Team
- A server responding to client with minimal QoS data, which is needed by the client
- Minor changes made to it to make it compatible
- Game patches in PowerPC assembly, in rpcs3 patching format.
- Game patches need to be applied for the game to be played online
- Needed for the time being, because the server is not a perfect 1:1 to original
- Displays server status and statistics about played games
- Created/Maintained by @dtzdev
- Visualizes currently ongoing league teams/statistics/results
- Repository Created/Maintained by @jfmartineau45
- A polling bot displaying server status
- A protocol that messages between relays and a matchmaking server
- Rosters/Tuners: Implement sending rosters and tuners with the server. Since we currently rely on a gamepatch to skip that functionality to even play.
- This step will bring us closer to RPCS3 vs PS3 or and PS3 functionality on the sever.
- This can make matchmaking more consistent since players don't have to match rosters outside of the game, only inside of the game.
- Client will hapilly download anything with octet stream from an URL we provide, But the question is more on what we will have to input to client.
- Invites (NHL 11–15): Fix and restore invite functionality. Note that behavior changed significantly starting from NHL 11 and up.
- OTP (6v6s): Investigate and fix the desync issue that occurs at the start of the match.
- EASHL: Look into EASHL implementation (will likely require the OTP desync fix to even play games).
- GM Connected: Investigate implementation.
- Cross-Title Porting: Implement HUT functionality across all other supported titles.
- Refactor Packs: Packs and their loot needs a big refactor.
- Online Tournaments: Implement online tournament functionality.
- Leaderboards: Menu is not implemented, it relays on StatsComponent which we have currently stubbed.
- Mobile App: Nah we wont probably actually do this :D
- Implement and display more graphs from played games.
- Find meaning behind all fields from reports gathered from played games.
- BlazeSDK & SceNetNp & ProtoSSL Bug By @Aim4kill
- ME3PSE By @WarrantyVoider @Erik-JS
- BFP4FToolsWV & BFP4FToolsWV Wiki By @WarrantyVoider
- PocketRelay & jacobtread/tdf By @jacobtread
- Hall of Meat By @Hall of Meat Team
- BlazeServer By @Perdo Martins
- BlazeSharkExtended By @Tratos
- recap_server By @vitor251093 and @dalkon
- openBlase By @openBlase
- BF4BlazeEmulator By @buchacho
- Skate3BlazeServer By @Wispp
- @the1Domo
