The TinTin++ message board

Mac OS X has bindings for F1-F4 naturally, so if you're using Mac, that could be the reason.

My every .tin-file are like this:
#class default_aliases kill
#class default_aliases open

[ lots of code... ]

#class default_aliases close
This way, all I need to do is #read the file ...

How you would write the #regex test?

When a variable contains a string with quotes (" or '), the string-match does not work when used quote matches with quotes used in code. This goes as far as into nested variables.

#var test {t ...

I ran this kind of nasty piece, that I cannot do #unvar for nested variable, if I use another variable as the key.

Example code:
#alias {test}{
#var {test} {{1 ...

I found out, that #break doesn't work in combination of #foreach and #regex. Break gets executed, but foreach continues regardless.

As an example:
#alias {test}
{
#var tmp { ...

It's a bug.

For some odd reason, the #function replaces the #sub's %1 with #function's %1.

When line is...
Spell: berserk : modifies hp by 50 for 1 hours

Output should be:
& ...

Oh, you've changed that in 2.0.7? Either it's not in the change-list, or I've missed it totally. I gotta update then. Smile

[Edit] I updated to 2.0.7, #unalias {%%*} now says that it cannot find #alia ...

For me, calling #unalias {%%*} while there is no #alias {%*} kills all aliases. Same goes for #actions.

Why not limit #unalias {%%*} to kill only alias with %* as name, instead of wiping out all of the aliases if %* doesn't exist?

While waiting for a possible change, one option is to use variable check.

#action {%*} {#if {"$trigger" > 0} {stuff;stuff;stuff}}

And maybe t ...

NOTE: This very same works with #unaction {%%*}.

Ever run into situation where you wipe out all of your #aliases due to #unalias {%%*}, when you actually haven't (yet) created #alias {%*} in the fi ...

I had this first done with PHP, but I tried to convert it to tintin syntax. Tricky is, that variables are set as pointers to variables in the resulting #alias action instead of their values.
#alias & ...

I found several syntax errors and mixed two data. I will reform the post and reply it.

Indeed, it works without the ~ in match, at least for character A, but for character B, it doesn't work.

You see any holes in this?

#alias {_chatter_}
{
#if {$chatter = 0}
{
#delay {1} {#var chatter 0};
};
#if {$chatter < 10 ...

Originally that "nop action" was inside alias, thus sometimes it actually wasn't set. But I placed it into the initiating file, yet the loop happened regardless.

One thing I come along is that occa ...

What can be a reason for an infinite loop with these #actions...
#action {%1 tells %2 '%3'$} {#chat message comms {%0}}
#action {%1 {clan|cabal}talks '%2 ...

www.theforsakenlands.org

Only mud I've bothered playing. I've tried couple, but noone did catch me as strong as this did.

Amount of players is not the greatest (last down-peak was 3 people onlin ...

Thanks for the reply. Smile

I'll try your suggestion.

When tintin crashes, does it produce any log into /var/log/ (or similar)?

Is there a way to have two logging going on simultaneously, where one is "ordinary" log, and another contains debug info?
...

#alias {window1} {#window1 #line substitute colors #send {%0}}
If it is #send {%0} within alias, then content that window1 receives is wrapped with {}. With #send %0 this does not happen.

And with ...

I'm really loving TinTin++
You're not the only one. Wink

For a record: When Ubuntu distro is upgraded, Tintin++ is downgraded to match the version offered thru repository.

My problems were due to that.

you'd probably want to go ahead and change...
I changed all #script and #system commands then. Thanks for the notify. Smile

You might also want to consider using netcat instead of #chat for your 2nd ...

#system causes same.
I was wrong. #system doesn't cause any misbehavior, only #script. I made a double-check, and for a good reason it seems.

Yeps, it was #script. I'll test if #system produces same problem.

[Edit] #system causes same.

Up is now last command rather than North.
I would suggest using numpad for navigating, if that's possible for you. Smile

I have this setup:
8 - north
4 - east
6 - west
2 - south
7 - up
1 - down ...

Is this caused by #script, or by #run / #system ?

The terminal restore is still in place for #script.
I believe it's #script, but I'll check that out.