aaditya / sbrw-server

SBRW server port in NodeJS.

SBRW Server

Overview

This is a compatible server implementation for Need For Speed World and borrows a lot of references from the SoapBox RaceWorld Project. It still is a work in progress and still has a lot of stuff which needs to be taken care of. So far the game loads into the login screen and can create driver (persona). Need to create the logic for other stuff as well.

This uses NoSQL DB paradigm so everything needs to be reworked from the original SBRW project accordingly.

Requirements

• NodeJS (v12+)

• MongoDB

Setup

Create a file .env in the root directory with content as follows:

NODE_ENV=development
PORT=8680
SECRET_KEY=<Token Signing Key>
MONGO_URI=<MongoDB URI>
ENABLE_UDP=false
CRYPT_KEY=<32 character string for encryption>

Installation and Running

npm i

In Development Mode npm run start-dev

In Production Mode npm start (You have to set up environment variables accordingly)

Contributing

• Fork this repository.

• Create a branch with name as per your feature/issue.

• Commit the code and raise a pull request.

• Wait for code review and further actions.

Notes

You might want to use the sister repo sbrw-capture to monitor the requests' data and appropriate response from this server or any other sbrw server.

You might want to change linting rules for line break according to your OS.

sbrw-server's Issues

Set up an integrated UDP server to capture packets.

NFS uses a UDP server along with the HTTP server to communicate between players, need to translate the packets and generate appropriate actions.

Worker Threads Implementation

Add support for experimental worker threads and test the stability of the server.

Migrate to Text based processing and not treat it as XML.

The game gives the changed XML on every car change and any of the product transaction, so need to remove the xml parser and treat the incoming xml as string and save it to db as it is.

Complete persona routes

Add account based telemetry.

For every login and logout, save the timestamps and the client data, whichever is possible to keep a track for fraudulent activity tracking.

Add oAuth Login with support to Google/FB etc.

Add a chat server.

NFSW uses an XMPP server for it's internal chat, need to incorporate it in the server.

Simplified error logging.

Add a centralized logging function for error in code and save them to db/file. (Winstrom ?)

Add Asset Rebuild Script