Forums Bug Reports /////command bug?

If you use 5 or more / before a command.

e.g. /////say Hello. You'll retrieve an error message in the status window.

I noticed that ages ago but assumed it was intended.

The number of times things evaluate doesn't go up after more than 2 slashes so it's kinda pointless to support anymore.

%a %b
%b %c

//echo -a -> %a
Output: -> %b
///echo -a -> %b
Output: -> %b

Confirmed, happens also in 5.91 and 6.16

/////echo -a hello

Its interesting that if u have a custom SAY or ECHO etc alias, they well be triggered no mater how many /'s

Confirmed.

I have scripted a /say alias so i don't get that problem.

sure about that?

Now add 2 more forward slashes to that.

Meant to be ///echo -a %a :tongue:

This is an undocumented feature, not a bug ^_^