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


This topic is now archived and is closed to further replies.


So you want to make an MMORPG?

51 posts in this topic

Just wanted to add onto this topic because it hits near and dear. I''m not a programmer, nor a professional game developer. I was considering as a hobby working on my own MMORPG. I''m still debating; However, While I do believe making an MMORPG is a very daunting task - I would hardly call it impossible. Making a "good" mmorpg that can compete and be successful is another story altogether.

Now to actually contribute something useful to this thread:

Regarding UDP and NAT, technically speaking UDP can work with NAT with no issue whatsoever. NAT or network address translation is typically used to describe what we in the industry call "Static NAT", "One-to-One NAT" or simply NAT. If your IP address is and you are "static NAT''d" to, you will have no issues using Unreliable Datagram Protocol.

However and this may be where Thona got confused, if the users edge router is using PAT (Port Address Translation) or "many-to-one address translation" or "hide NAT", your users may have issues connecting.

PAT = you are your neighbor is you both are PAT''d as behind the router/firewall. The router/firewall/whatever rewrites the source port address so when it gets a response back it can differentiate traffic destined for different internal clients i.e. "oh, this source port is 10001. Source Port 10001 = I will send this to". This allows you to both show as IP address yet still receive reply traffic.

Again, in PAT the router or firewall rewrites the source port strictly to distinguish traffic between the internal clients and an outside server/resource.

What defines whether a game will have problem with PAT''d users?

Very simple. If the client (user) must use a specific source port address, typically the edge router will use the one the client requested but if another client has already been assigned that source port the router/firewall will assign the new client a different source port. If your program requires a specific source port address you will have problems when multiple clients try to connect:

A. because one client has that source port already
B. because even if the server did you the same source port for both internal clients, how would it know which traffic was destined for which client?

Situations in which UDP fails is most prevalent (identifiable) in IPSEC communications with older VPN software in which the client must always use source port 500 . As soon as that port is used by someone else (or another session) no other user will be able to use it.

The solution is to use public IP''s on the inside network (which is not always feasible/affordable) or to assign static NAT to the machines which will be going to that server OR TO SIMPLY BUILD A GAME WHICH DOES NOT REQUIRE A PARTICULAR SOURCE PORT ADDRESS FROM THE CLIENT.

Summary: If youre programming a network game don''t be an idiot and define the client source port, just define the port the client needs to connect to (destination port) and NAT or PAT clients will work fine.

UDP is a fast protocol and works great where speed/lag is an issue... and UDP can be load balanced and reliable (at higher layers) as well. If I ever make a MMORPG I guarantee it will use UDP.

It''s late but I hope that made sense and helps clear up some confusion.

J. Ross

Share this post

Link to post
Share on other sites
Original post by Anonymous Poster
It''s late but I hope that made sense and helps clear up some confusion.

Yes it was late - almost 2 years late in fact.

The general rule with thread necromancy is: if it''s really old (ie more than a month or so) it''s better to start a new thread but include a link to any previous discussion you want to reference than to dig up an ancient 4+ page thread full of posters half of whom don''t post here any more.

Share this post

Link to post
Share on other sites
This topic is now closed to further replies.