• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0

Opinions on client architecture in client/server game

4 posts in this topic

Any suggestions / best practices in regards to client architecture in a networked game?


Two server types, lobby/game.

The lobby handles:
- registration of new users
- retrieval of list of game servers
- retrieval of the users current game server

The game server handles
- registering to a game
- all gameplay

Flow for a new client and player:

Connect to lobby
1. register new user
2. retrieve servers

(user selects server)

Connect to game
1. Register to game
2. Game server sends gamestate
3. Game progresses

Now in the example above, we could drive it from the server, i.e.

1. Register new user -> server responds with server list + client state change to "select server"

(user selects server and client logs in to game server)

1. Client sends user credentials -> server responds by registering player, returning game state and request client state "in game"


It could be more flexible and less streamlined:

1. Client sends register, receives ok + server list.
2. Client determines that it should change to the "select server" state (it has a server list, and just registered)

(user selects server, client opens game server.

1. Client sends "join game" request
2. Server registers client and sends game state
3. Client determines it should go into the "in game" state, since it has game state and just did a join game request.

Contrived example perhaps, but the point is:
Should the server explicitly drive the state changes, or is there an informal protocol when the state should change?

When server drives state, problems may occur where the client has a more finely grained state than the server.
When the client drives state change, then a) the state changes become informal b) client might need to assemble lots of information to reconstruct what state it should be in.

Which choice leads to a simpler client architecture?

Share this post

Link to post
Share on other sites
[quote name='hplus0603' timestamp='1333074955' post='4926534']
The FAQ for the forum is full of just this thing!

Where? I don't see anything in particular on tradeoffs in client protocol design?

In-game is rather much simpler, since one tends to have an overarching game<->client synchronization mechanism there and we just keep an open socket and synchronize models.

The lobby/login design is a bit trickier, especially when it *almost* could be stateless (and the client basically just could use a chain of HTTP/HTTPS requests).

Stateless transfers is attractive in some ways since the client is going to run on cellphones as well. However, since the game needs a live open socket, this problem needs to be handled anyway. It's better to handle it uniformly I think.

Share this post

Link to post
Share on other sites
In general, it depends on the genre of game. RPGs typically end up having a different structure than FPSs. TBGs have a different structure than RTSs. Asynchronous games have a different structure than real-time head-to-head.

So, there is not "one single solution." For an RTS, you probably want to go "input synchronous." For an action game, that can work great, too, but you probably want to speculate forward for the player simulation, and accept corrections from the server. For an RPG, you probably want to worry more about replicating triggering events, rather than specific property changes. For a TBG, you typically want full states out, but perhaps only actions in. The list goes on -- the FAQ has a lot of links to different ways of doing this.

Share this post

Link to post
Share on other sites
If you look at examples like counter strike etc. there is not really a game state change for the first scenario you describe. You are polling the server list, get a response (or not) and then display the servers.

If the user then selects to join a server, you could switch to a loading state, where first a connection is established the game content is loaded, game state recieved, etc.

Then if everything is all right you switch to the ingame state.

I dont know why you would want the server to switch the game states of the client, does not make sense to me. In a finite state machine you switch the state automatically when you receive a certain input.

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  
Followers 0