X-Git-Url: http://dxcluster.net/gitweb/gitweb.cgi?a=blobdiff_plain;f=html%2Fconnect.html;h=cb4da94134a9c4b334aa60d3c12ddd7908fdd613;hb=e78bbb17a141401c9d3da2d5268201e64e004261;hp=485dda50b13a553e966716162439bd5ad18718a8;hpb=b870b63342a1b7c2cab0123b79942c7dda109d08;p=spider.git diff --git a/html/connect.html b/html/connect.html index 485dda50..cb4da941 100644 --- a/html/connect.html +++ b/html/connect.html @@ -86,7 +86,7 @@ Last modified: Sun Sep 2 22:02:36 BST 2001 for the final "connect" string from the BPQ node that directly connects you to the cluster node itself.

-

A AGW Engine example would be very similar and look like this:-

+

An AGW Engine example would be very similar and look like this:-

     timeout 60
@@ -177,8 +177,8 @@ Last modified: Sun Sep  2 22:02:36 BST 2001
 	particular strings) and then performs some "action" (usually some kind of connect command
 	for the type of system you are trying to navigate). When one
-	"state" "fires"
-	(detects the string are looking for), it sends the command
+	"state" "fires"
+	(detects the string are looking for), it sends the command
 	associated with that state and then moves onto the next "state", in our case: the next line.

@@ -244,7 +244,7 @@ Last modified: Sun Sep 2 22:02:36 BST 2001

This process is repeated for every line of chat script.

-

  • client starts the connection, put the arguments +
  • client starts the connection, put the arguments you would want here if you were starting the client program manually. You only need this if the script has a different name to the callsign you are trying to connect to (i.e. you