HTTPS SSH

SteveTech1

Complete open source multiplayer FPS Engine for Java

SteveTech1 is a 3D multiplayer FPS framework and engine, designed to help you create games such as Team Fortress 2, Overwatch, PUBG etc.. in Java. It includes almost all the code you'll need to create your own multiplayer FPS, and uses JMonkeyEngine for the 3D. It is designed to be easily modifiable and extendable (as the example games will show). It is intended to be the Java equivalent of something like the Source engine. You will need to provide your own assets of course.

CURRENT STATUS

All the basic features are complete but not thoroughly stress-tested yet. All aspects are subject to change.

FEATURES:

  • Client prediction & Lag-compensation
  • TCP and UDP for networking
  • Simple physics
  • Projectile and hitscan weapons
  • Open source

GETTING STARTED

TECHNICAL OVERVIEW

  • To create the server, extend AbstractGameServer. Various methods require overriding that will define how your game works.
  • To create the client, extend AbstractGameClient. Various methods require overriding that will define how your client works. The client needs access to all the same data as the server; it currently doesn't download anything from the server.
  • The game primarily works around "entities", which can be anything, e.g. a player, a wall etc... Entities are defined mainly by implementing interfaces. For example, implement the IRemoveOnContact to force an entity to be removed automatically when it touches anything (e.g. a bullet hitting a wall).
  • You will need to obtain your own 3D models of course!
  • The code is designed so that as much identical code as possible is run on both the client and the server. The client handles its own collision as far as preventing physical entities from moving inside each other, but only the server handles collision effects, e.g. players getting killed, doors being opened.
  • Have a look in the /docs folder for various notes on specific aspects of the game.
  • Network communication (which uses Kryonet) works on Messages, which are serialized classes (POJOs) containing the required information. One of the parameters in the constructor the messages is whether to use TCP or UDP. Use TCP for any message that needs to guarantee delivery (e.g. a Game Over message), and UDP for any messages where speed is most important, e.g. An entities updated position.

DEBUGGING

  • The file Globals.java contains lots of boolean for helping to debug certain aspects of the game.
  • On the server command console, you can send the command "mb", which will make the client draw an outline of all the entities as the server sees them. This can be useful, since otherwise there is no easy way of knowing what the world looks like on the server.
  • Enter "help" on the server console for a list of other commands.

CREDITS

  • Designed and developed by Stephen Carlyle-Smith (http://twitter.com/stephencsmith, stephen.carlylesmith@googlemail.com)
  • Uses JMonkeyEngine for the 3D
  • Uses Kryonet for networking.

LICENCES