My next focus is the NPC battles. As I found a month or so ago, the client contains no information regarding the rival drivers. Only the rival team name and member names are stored in the client. This is only used for the “Data” dialog to see the rival statuses. Read more…
Now that the test server has been running for some days I wanted to get battling implemented so that players have more to do other than using SBOL as a chat room. The option to battle other players wasn’t appearing. So began reversing the function that displays the opponents handle Read more…
Now I can handle other players I implemented a course array to the server much like you would do for lobbies for other games. Players in courses can only talk and see players in the same course. at the moment there is a limit technically of 100 players in a Read more…
Along with parts, players can also obtain Items. Items can be exchanged for many things like cars, parts, boosts and warps. Most items were obtained from winning races. But some can be purchased from a shop. While working on shops I started on Items next. As I had the p.dat Read more…
Working on the shops for SBOL I found that half used data from local data files and others expected the server to provide the costs and items. For example; parts shops retrieve their costs from the parts file p.dat. However the car shop expects the server to provide this. Starting Read more…
So, I took a break from the project. I left the project being able to spawn a player/npc but not able to see them on the course. I generated binaries of my server code and shared a copy with a client so that people could test out the code. Not Read more…
I’ve made a start on the packets required to display other players and NPC’s in game. It appears that the server is responsible for the AI of the NPC. An archived page from the MPS website (the system that SBOL runs on) indicates that Genki used Server+ and AI. I Read more…
A player of the game got in contact and provided me with a later client (2.03.00) to what I was using for the project (2.00.03). Some packets were changed and the new client required an additional 2 packets to login. 0x1500 and 0x1600. The data in the response 0x1580 packet Read more…