Tintin++ is a very flexible mud client, but the documentation on how to get started is a little limited. Here is a quick way of getting up and running on 3k.
Take the script below, save it to a new file called "3k.tin" (changing it where appropriate). Then start up tintin with the command "tt++ 3k.tin".
#EVENT {SESSION CONNECTED}
{
#VAR {session[name]} {%0};
};
#SESSION {3k} {3k.org} {3000};user_name_here;password_here;
#CONFIG {packet patch} {0.5};
#CONFIG {command echo} {off};
#FORMAT {session[ScreenRows]} {%R};
#FORMAT {session[ScreenCols]} {%C};
#NOP #READ ${session[name]}_Variables.tin;
#NOP #READ General.tin;
#SPLIT 4 1;
Ok, this script needs a little more explanation, so you know what it does and why.
#EVENT:
This captures the name of the session as it is created, which is useful because you can use the session name within scripts to identify if you are currently in 3k or 3s (or elsewhere, gasp!) to customise how they work (see the example of loading the variables file, below).
#SESSION {session name} {host} {port}:
This opens the connection with 3k. Change the username and password entries to your own.
#CONFIG {packet patch}:
This puts a slight pause on data coming from the mud, to ensure that all data has been received in any chunk before trying to show it on the screen. Mostly this is not noticeable on the mud, apart from it showing less breakup on rapidly updating text, but it can cause a short delay displaying the mud prompt. To get around this you can set the mud prompt to have a newline within it "prompt >$nl$" which will force the mud prompt to appear immediately. (or if you don't like it and have a good connection, remove this line).
#CONFIG {command echo}:
Echo any typed commands into the mud output.
#FORMAT:
screen rows and columns… save the current screen height and width to variables for use elsewhere if you need them.
#READ {filename}:
read will load in scripts from other files. In the case of "#READ ${session[name]}_Variables.tin" this will look for a filename that is dependant on the name of the session currently running (E.G. if you were in 3k, it would try to open 3k_Variables.tin). See Tintin Saving Variables.
#NOP:
As you are just starting out, you will probably not have a General.tin or a 3k_Variables.tin. Therefore I have commented out the #READ lines with a #NOP at the front (No Operation). To put them back remove the #NOP at the front.
#SPLIT 4 1 … This command splits the screen into 4 sections. The first parameter sets the number of lines reserved at the top of the screen, the second reserves lines at the bottom (and puts the command line beneath that). Reserved lines are not used to output normal mud text, so can be used to write information to that you want to stay on the screen, such as chatline text, HP bar information etc etc. See the Tintin HP Bar for an example of how this can be used.
