TCP Billing FAQ - Revision history

Hakaku: /* Are there any TCP billers available for public download? */ +sius

2010-05-24T23:04:58Z

‎Are there any TCP billers available for public download?: +sius

Hakaku: /* Are there things I should be wary about when using the protocol? */

2009-10-18T03:55:36Z

‎Are there things I should be wary about when using the protocol?

Hakaku: /* Are there things I should be wary about when using the protocol? */

2009-10-18T03:41:36Z

‎Are there things I should be wary about when using the protocol?

Hakaku: Adding some notes and precautions

2009-10-18T03:39:35Z

Adding some notes and precautions

Hakaku at 19:12, 24 September 2009

2009-09-24T19:12:01Z

CypherJF: added bit about accede; removed playsubspace.com link SkyBill - broken URL

2007-09-29T03:34:07Z

added bit about accede; removed playsubspace.com link SkyBill - broken URL

BDwinsAlt: /* Are there any TCP billers available for public download? */

2007-08-06T17:38:57Z

‎Are there any TCP billers available for public download?

Smong: added two new questions, deleted old unanswered question

2007-02-11T15:14:29Z

added two new questions, deleted old unanswered question

Smong: /* Are there any TCP billers available for public download? */ grammar

2007-02-11T15:07:47Z

‎Are there any TCP billers available for public download?: grammar

Smong: /* Are there any TCP billers available for public download? */ ew, cleaned this up.

2007-02-11T15:07:20Z

‎Are there any TCP billers available for public download?: ew, cleaned this up.

@@ Line 14: / Line 14: @@
 * [[SkyBill]] written by [[User:Doc flabby|Doc Flabby]].
 * [[UBill]] written by [http://braddavis.info BDwinsAlt] is available at http://forums.minegoboom.com/viewtopic.php?t=7543.
 <!--
 == Are there any TCP billers online for public use? ==

@@ Line 24: / Line 24: @@
 * For starters, the protocol makes extensive use of player identification numbers rather than names. This can be a nuisance when requiring the player's name for communication between, for example, different zones and databases. Try to effectively find one or multiple solutions to store the player id along with their name for quick and efficient retrieval later on.
-* The colon (:) is used extensively in the TCP Protocol. Be wary of zone names, player names, passwords, and messages among others containing them. You will likely want to reject those zones and players from connecting, but there is no need from blocking extra colons in the final parameter. This includes namely messages. If you intend on separating the parameters into an array of some sort, make sure to join the extra parameters together (do not forget to readd a colon), otherwise player messages will be accidentally cut off (e.g. ''CHAT:0:2:0:<u>And then he said''':''' "what are you staring at?"</u>'' - The final parameter is the entire section underlined.).
+* The colon (:) is used extensively in the TCP Protocol. Be wary of zone names, player names, passwords, and messages among others containing them. You will likely want to reject those zones and players from connecting, but there is no need from blocking extra colons in the final parameter. This includes namely messages. If you intend on separating the parameters into an array of some sort, make sure to join the extra parameters together (do not forget to re-add a colon), otherwise player messages will be accidentally cut off (e.g. ''CHAT:0:2:0:<u>And then he said''':''' "what are you staring at?"</u>'' - The final parameter is the entire section underlined.).
 * Be careful about implementing "unlimited" of a certain feature. Although theoretically possible, biller hosts should still be allowed to control the limits, otherwise a mischievous player could attempt to exhaust the memory and space limits of the server and or database.
-* When using and storing player passwords, make sure to hash them to prevent player names and passwords from being easily stolen should your database ever be compromised. The popular MD5 cryptographic function is no longer recommended, instead, you will want to look up the safety and reliability of [http://en.wikipedia.org/wiki/Cryptographic_hash_function#Cryptographic_hash_algorithms other hash algorithms] such as SHA-512, RIPEMD, or WHIRLPOOL for example.
+* When using and storing player passwords, make sure to hash them to prevent player names and passwords from being easily stolen should your database ever be compromised. The popular MD5 cryptographic function is no longer recommended, instead, you will want to look up the safety and reliability of [http://en.wikipedia.org/wiki/Cryptographic_hash_function#Cryptographic_hash_algorithms other hash algorithms] such as SHA-512, RIPEMD, or WHIRLPOOL for example. Appending random salts to each password will greatly increase the odds that each password is unique, and it will ultimately make it more difficult and timely to crack (Do not use a straight-forward formula for generating the salt, e.g. ''password+username''. If this formula is known, then you have ultimately gained no more protection than the password alone).
 * ''CHA'''TT'''XT'' has a double t in it.

@@ Line 24: / Line 24: @@
 * For starters, the protocol makes extensive use of player identification numbers rather than names. This can be a nuisance when requiring the player's name for communication between, for example, different zones and databases. Try to effectively find one or multiple solutions to store the player id along with their name for quick and efficient retrieval later on.
-* The colon (:) is used extensively in the TCP Protocol. Be wary of zone names, player names, passwords, and messages among others containing them. You will likely want to reject those zones and players from connecting, but there is no need from blocking extra colons in the final parameter. This includes passwords and messages. If you intend on separating the parameters into an array of some sort, make sure to join the extra parameters together (do not forget to readd a colon), otherwise player messages will be accidentally cut off (e.g. ''CHAT:0:2:0:<u>And then he said''':''' "what are you staring at?"</u>'' - The final parameter is the entire section underlined.).
+* The colon (:) is used extensively in the TCP Protocol. Be wary of zone names, player names, passwords, and messages among others containing them. You will likely want to reject those zones and players from connecting, but there is no need from blocking extra colons in the final parameter. This includes namely messages. If you intend on separating the parameters into an array of some sort, make sure to join the extra parameters together (do not forget to readd a colon), otherwise player messages will be accidentally cut off (e.g. ''CHAT:0:2:0:<u>And then he said''':''' "what are you staring at?"</u>'' - The final parameter is the entire section underlined.).
 * Be careful about implementing "unlimited" of a certain feature. Although theoretically possible, biller hosts should still be allowed to control the limits, otherwise a mischievous player could attempt to exhaust the memory and space limits of the server and or database.

@@ Line 6: / Line 6: @@
 == Why is there no ability for the billing server to shutdown/restart a server? ==
-The ability of the billing servers to shutdown a zone server is a relic from the old system. The biller is no longer considered an administrative and control server, but simply a validation system used mainly to control passwords for player names and bans.
+The ability of the billing servers to shutdown a zone server is a relic from the old system. The biller is no longer considered an administrative and control server, but simply a validation system used mainly to control bans and passwords for player names.
 == Are there any TCP billers available for public download? ==
@@ Line 18: / Line 18: @@
 * [[Accede|Project: Accede]] written/hosted by [[User: CypherJF|CypherJF]] details are available at http://cypherjf.sscentral.com/accede/
 -->
 [[Category: FAQ]]
 [[Category: Protocol]]

@@ Line 1: / Line 1: @@
 == What's so special about TCP billers? ==
-TCP billers use a new simpler protocol compared to the original UDP billers.
+TCP billers use a new simpler protocol compared to the original UDP billers. See [[TCP Billing Protocol]] for more details.
 == Can I use subgame with a TCP biller? ==
@@ Line 6: / Line 6: @@
 == Why is there no ability for the billing server to shutdown/restart a server? ==
-The ability of the billing servers to shutdown a zone server is a relic from the old system. The biller is no longer an administrative and control server, but simply a validation system used to control passwords for player names and bans.
+The ability of the billing servers to shutdown a zone server is a relic from the old system. The biller is no longer considered an administrative and control server, but simply a validation system used mainly to control passwords for player names and bans.
 == Are there any TCP billers available for public download? ==
@@ Line 13: / Line 13: @@
 * Two different versions of [[POCoB]] written by [[User:Smong|Smong]] are available at http://toktok.sscentral.com/ss-pocob.php.
 * [[SkyBill]] written by [[User:Doc flabby|Doc Flabby]].
-* [[UBill]] written by [http://braddavis.info BDwinsAlt] is available at http://braddavis.info/UBill.zip.
+* [[UBill]] written by [http://braddavis.info BDwinsAlt] is available at http://forums.minegoboom.com/viewtopic.php?t=7543.
+<!--
 == Are there any TCP billers online for public use? ==
 * [[Accede|Project: Accede]] written/hosted by [[User: CypherJF|CypherJF]] details are available at http://cypherjf.sscentral.com/accede/
 [[Category: FAQ]]
 [[Category: Protocol]]

@@ Line 5: / Line 5: @@
 Yes, but only unfinished ones.
-* Two different versions of [[POCoB]] written by [[User:Smong|Smong]] is available at http://toktok.sscentral.com/ss-pocob.php.
+* Two different versions of [[POCoB]] written by [[User:Smong|Smong]] are available at http://toktok.sscentral.com/ss-pocob.php.
 * [[SkyBill]] written by [[User:Doc flabby|Doc Flabby]] is available at http://playsubspace.com.

@@ Line 3: / Line 3: @@
 == Are there any TCP billers available for public download? ==
-Long answer no with an if, short answer yes with a but.  A stable, public-use TCP [[biller]] does not currently exist.  If you wish to use simply a short-term biller created as a proof-of-concept TCP biller, then [[POCoB]] is for you.  [[User:Smong|Smong]] wrote it and has it available [http://toktok.sscentral.com/ss-pocob.php on his website].  The old UDP billers are available still, one with the server download, and one found at [http://catid.sscontinuum.com/ Catid Inside].
+Yes, but only unfinished ones.
 == Why should I use a TCP biller instead of something like SSC? ==