• 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
ate50eggs

Working on my first game, advice needed with Web Service

3 posts in this topic

So I am working on my first game and would like some advice as this is new to me. The game will be a CCG and will have the following features

 

1) Matchmaking based on player ranking

2) Tournaments

3) In app purchases

4) Trading

5) Deck building

 

The game will start off on iOS, but would like the flexibility to handle other platforms as well (Android, Web, etc), so Game Center is out. I have some experience with .net, so could probably roll my own service to handle some of these features but was wondering it anyone had any suggestions on how to proceed? 

0

Share this post


Link to post
Share on other sites

Firstly, decide if you want to use REST or SOAP for your Web Service requests and responses. The first one is simpler and lightweight, the second one is a bit more complex as it involves RPC process via sending commands in XML format over HTTP. If you are just starting, I would recommend REST.

 

Secondly, think about your server architecture. For example you may want to have a single "gate" server and the rest of the servers to which player will actually make calls. It is needed for decreasing latency and single-server load.

 

C# and .NET are capable of providing mechanisms for doing all of that. If you have the knowledge of .NET, it is enough.

0

Share this post


Link to post
Share on other sites

Firstly, decide if you want to use REST or SOAP for your Web Service requests and responses. The first one is simpler and lightweight, the second one is a bit more complex as it involves RPC process via sending commands in XML format over HTTP. If you are just starting, I would recommend REST.

 

Secondly, think about your server architecture. For example you may want to have a single "gate" server and the rest of the servers to which player will actually make calls. It is needed for decreasing latency and single-server load.

 

C# and .NET are capable of providing mechanisms for doing all of that. If you have the knowledge of .NET, it is enough.

 

I would definitely go with a REST based solution and if I were to write my own C# service, there is a cool framework called ServiceStack that makes rest based services easy. I am wondering if I should use a service like Parse as they offer a lot of cool features that I would otherwise have to write myself. The only crappy part is that their custom code has to be written in JavaScript.

0

Share this post


Link to post
Share on other sites

There are many services that offer application hosting for custom applications. Examples include Heroku, and Google App Engine.

 

The main thing that is hard with these services for games is that the "matchmaking" part typically needs to be integrated with the "game servers" part, which often makes it a lot harder, as the application servers typically are request/response, HTTP based, rather than permanent-connection, state based.

 

Btw: I would recommend against RPC for anything that goes across the public internet (this includes XMLRPC and SOAP and others,) and typically recommend against it for anything internal as well. Trying to pretend a remote endpoint is local (which is the intent of RPC) just never works out right. Much better to explicitly design for remote services, make the amount of data transferred per request be large, and make the number of requests small.

0

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