Top Mud Sites Forum - View Single Post

shadowfyr · 06-21-2008, 10:59 PM

Wrong! Why? Because, as someone pointed out on the "first" page of this thread, the moment you create a protocol and someone decides they want the client to do something it won't, they are going to try to figure out how to talk to your server **without** your client. You still end up having people using broken code to talk to your system, and if any of those protocols involve "anything" that could effect game play in any way...

Your better off with an open protocol, not just because it means having good specs to follow, but because they will find bugs you miss, and come up with ideas you won't.

Mind you, the appeal is there, its just, imho, its short term, limited and mostly illusionary.

06-21-2008, 10:59 PM	#41
shadowfyr Senior Member Join Date: Oct 2002 Posts: 310	Re: custom clients. Good or bad? Wrong! Why? Because, as someone pointed out on the "first" page of this thread, the moment you create a protocol and someone decides they want the client to do something it won't, they are going to try to figure out how to talk to your server without your client. You still end up having people using broken code to talk to your system, and if any of those protocols involve "anything" that could effect game play in any way... Your better off with an open protocol, not just because it means having good specs to follow, but because they will find bugs you miss, and come up with ideas you won't. Mind you, the appeal is there, its just, imho, its short term, limited and mostly illusionary.