TinTin++ Mud Client
TinTin++
Download
FAQ
Features
Forum
Install
Starting
Links
Manual
Scripts
Changes
Make a donation to the TinTin++ Mud Client developerDownload the TinTin++ Mud ClientJoin the TinTin++ Mud Client Discord channel
 

Installing the WinTin++ Mud client on Windows

While you can install TinTin++ on Cygwin and WSL the easiest route is to use the WinTin++ installer from the download page.
 
Check the install section for installation instructions for specific Windows platforms.
 
 

Creating a start up script for WinTin++

When starting up WinTin++ it tries to read the file 'main.tin' by default, this feature will be used in the following walkthrough example:
 
  • After starting WinTin++ you should check out the #config command. For example, if you want speedwalk disabled per default you would want to type: #config speedwalk off, if you type #config without an argument you will get a list of things you can configure. Set the configurations to your liking and type: #write main.tin, this will save your changes.

  • If you want to edit main.tin directly you can do so by opening the file with wordpad (don't use notepad) in the WinTin++ directory. You can configure Windows to automatically open .tin files with Wordpad.

  • If you want WinTin++ to automatically connect and login to your favorite mud upon startup create a PROGRAM START event, for example:
    #event {PROGRAM START} {#ses bla mymud.com 1234;MyName;MyPassword}
    This would make you connect to that address (which is a made up address). It sets the session name to 'bla' and also passses along the name and password of your character, assuming that's what your mud asks for first.

  • To save the event once again enter: #write main.tin, if you later change your mind and don't want to auto-connect type: #unevent PROGRAM START, and #write main.tin to save the changes.
 

Input bar

A useful thing to have is an input bar. You can create one on WinTin++ by using: #split. See #help split for more information. This will prevent the prompt from overwriting what you are typing.
 
If you are using the Windows Console (for example because you use a screen reader) keep in mind you need to use #split 1 1 because of a bug in the Windows console.