Go
back to previous topic |
Forum Name |
Gameplay | Topic subject | TinTin++ Script Compilation | Topic
URL | https://forums.carrionfields.com/dcboard.php?az=show_topic&forum=6&topic_id=31504 |
31504, TinTin++ Script Compilation
Posted by HomingTorpedo on Wed 31-Dec-69 07:00 PM
Recently I've been looking into more powerful MUD software that can work on both windows and linux systems. Out of all the ones I've tried (mostly been looking through the linux perspective since Wine on my comp sucks), I favored Tintin++ So I'd like to start this thread on suggestions of TinTin Scripts and commands in case others are interested in using TinTin as well.
Personally, Some scripts that would be greatly appreciated: Logging (Setting up date and logfile location) Highlights Macros (especially how to set the keypad to register the directions and not affect the regular numbers or arrow keys)
|
31507, RE: TinTin++ Script Compilation
Posted by sorlag on Wed 31-Dec-69 07:00 PM
Logging is pretty straightforward. You set a variable using the #format command and then use it in your output filename for #log. For example:
#ALIAS {logmychar} { #format {logfile} {%t.txt} {%Y%m%d-%H%M%S}; #log append $logfile } {5}
There is a more complex example on the Tintin++ site at http://tintin.sourceforge.net/scripts/logging.php.
To highlight stuff, use #highlight. Example:
#HIGHLIGHT {(WANTED)} {light green} {5} #HIGHLIGHT {The power of your {.*} spell unravels.} {blue} {5}
For more info on highlight, regular expressions, and color options, read http://tintin.sourceforge.net/manual/highlight.php.
You can create macros with #alias (and a few other commands) which are documented on the Tintin++ site. As far as the keypad itself, it depends on OS / terminal emulation type. Start here, http://tintin.sourceforge.net/manual/keypad.php. There is also some forum chatter both on Tintin++ boards and Qhcf about this.
My "stock" script file contains some auto-logging stuff, my preferences for #config, and a few highlights that still aren't handled in game (by "color affects", etc). Beyond that, I've never found a need for all the fancy crap other people use. A dead simple targeting script is pretty easy to write, but I prefer on the fly "#alias 1 bash simon". I also use the keypad on the rare occasion I'm playing a conjurer and then I use it for familiar movement. I also keep class-specific scripts handy for quick casting, etc.
|
31509, RE: TinTin++ Script Compilation
Posted by HomingTorpedo on Wed 31-Dec-69 07:00 PM
T.Y.4.R
>There is a more complex example on the Tintin++ site at >http://tintin.sourceforge.net/scripts/logging.php. > >To highlight stuff, use #highlight. Example: > >#HIGHLIGHT {(WANTED)} {light green} {5} >#HIGHLIGHT {The power of your {.*} spell unravels.} > {blue} {5} > >For more info on highlight, regular expressions, and color >options, read >http://tintin.sourceforge.net/manual/highlight.php.
Currently I am using the logging and highlighting functions tool on the TinTin website, Its just can't figure out how can I tell tintin to save in a specific folder for logs and class specific arrangements
>You can create macros with #alias (and a few other commands) >which are documented on the Tintin++ site. As far as the >keypad itself, it depends on OS / terminal emulation type. >Start here, http://tintin.sourceforge.net/manual/keypad.php. >There is also some forum chatter both on Tintin++ boards and >Qhcf about this.
I've founda few targetting and highlighting scripts (THX for all who posted those) but Lately the QHCF boards have developed the case of the overactive smacktards and I'm fairly certain i'm not gonna get much outta there.
|
31520, RE: TinTin++ Script Compilation
Posted by sorlag on Wed 31-Dec-69 07:00 PM
The logging example I posted specified the folder the log should end up in, and you can add a variable or sub-folder for character name to make the logs even easier to glance through.
As far targeting, it sounds like you've got the basics. Doing triggers and stuff isn't hard, but it's kinda lame (IMHO) so I've never written anything beyond the most basic stuff just to learn how.
If there is something specific you want to figure out, post it here or on the script board of Qhcf.
| |