This document will hopefully answer most questions regarding tintin++ (tt++).

I'll refer to this version as tintin++ 2.0. Due to heavy modifications, over
50% of the source code, all questions and requests should be addressed on
the forum at http://tintin.sf.net/bb since I doubt previous tintin++ authors
would know how to go about this version without reading up on over 5000 lines
of code.

Last updated: 03/10/2004

Q00) I'm new to tintin, how do I get started?

A00) Quite easy, start tintin using ./tt++, to connect to a mud type:

     #session <name> <mud address> <mud port>

     The name can be whatever you want it to be. If you start up 2 or more
     sessions you can switch between the sessions using #<name> or use
     #<name> [command] to have that session execute a command keeping the
     session in the background.

     Type #help for a list of help subjects, #help <subject> for more
     information.

Q01) What machines does tintin work on?

A01) Pretty much any UNIX machine with a modern compiler as well as Windows
     and OS X.


Q02) What version should I use 1.50 or 1.86 or 1.90+ ?

A02) 1.90+ but realise 1.90 is not 100% compatible with scripts from previous
     tintin versions. 1.86 uses readline which might give trouble installing.
     1.50 should run on most unix machines.

     Version 1.90 has many extra features and various bug fixes.


Q06) I can't get tintin compiled still.  Where can I get more help?

A06) You can get help from a couple of places.  The first place to start
     is to take a look at the message board, there should be a link to this
     message board on the tintin++ website.

     Check to see if your problem has been asked before and if there is a
     solution.  If you don't see anything that looks like your problem, post
     a message and ask.  Please provide as much information as possible
     such as the OS, compiler, error messages, etc.


Q07) I can't get tintin compiled, can't you send me a binary of tintin?

A07) There are precompiled versions for Slackware (works on various linux
     distros), OS X and Win32 available on the website.

Q08) I would like to help, how can I contribute to tintin?

A08) You can assist people on the message board and give bug reports or
     suggestions.

     Currently there is no development team, just a few individuals
     working on seperate versions of tintin++, if you feel the urge to write
     code for tintin++ try to get in touch with one of these individuals or
     write your own version.

Q09) Tintin is so awesome, how can I thank you guys for spending all that time
     to write tintin for free?? :)

A09) Fan mail is always welcomed :)


Q11) Can I use code from tintin?

A11) Yes, provided that you follow the terms of the license.  The license
     used for tintin 1.90 and higher is GPL. Older tintin versions are public
     domain which means there are no restrictions.

Q12) I contributed code X, why isn't my name listed in the CREDITS file?

A12) Most likely your name slipped by before Davin Chan started
     maintaining tintin and adding people to the CREDITS file. If you
     believe you have contributed code to tintin, please email me and
     let me know. Make sure to see if your code is still existant in this
     version.


Q14) I've seen some nifty code and would like to use it in a different program.

A14) If you read the COPYING file you will see you are allowed to modify and
     redistribute this version as long as you make it clear you made changes,
     and what those changes are. If you want to use tintin code in another
     program not licensed under GPL you need to get permission from the author.
     Make sure to see if the exact code you want to use isn't existant in older
     tintin++ versions before contacting me, because I obviously cannot give
     permission for code I didn't write :) Also notice that older tintin++
     versions are not licensed under GPL.

Q15) My old script files do not work, is this a bug?

A15) Possibly, more likely your old script files do not work because a lot has
     changed in this version. Try reading #help <command> about the subject.
     Also the new script parser resembles the working of common scripting
     languages. Also try to look through the examples, they are supposed to
     work, and you might find out what you are doing wrong. Feel free to
     ask for help on the forum.

Q16) #prompt {string} does not work

A16) That's because the new syntax is: #prompt {string} {substitution}
     Read the help for the substitute command for more information.

Q17) I want to make an ALIAS that creates an ACTION, but both use %0, how to
     go about this?

A17) Use %%90 %%91 %%92. When the alias is parsed %9 will be replaced with the
     9th argument which mostly isn't given, this leaves %0 %1 %2.

     Another way to go about it is using classes which you can read from file
     and are easy to delete when you want them removed.

Q18) How to enable support for chinese muds?

A18  Try: ./configure --enable-big5 to use the big5 encoding. You may however
     want to use the last readline enabled version of tintin++ which would
     be tintin++ 1.96.4.

Q19) I use OS X and am totally friggin confused...I ran tintin a few times,
     and now every time I open a terminal window, it runs tintin automatically.
     What the hell has this program done to my computer?


A19) You did "use settings as default" while running tintin. There's a few
     ways out of this, but the easiest is locating your terminal preference 
     (home : library : com.apple.Terminal.plist) and deleting it. You'll have
     to redo anyting custom you set up (screen size, colors, etc.), but it
     will get the terminal back to the default of loading into your home
     directory.