'echo' as a log-able function
 

Can the function 'echo' be placed in the /listscriptlogfunctions as a log-able function? As a result of poor organization, there's an annoying echo of 1 or 0 that I can't seem to trace. :cry: Since era has alot of scripts using echo, it figured it would be simple and nice thing to add since sendtorc and sendtonc are already log-able functions. Ofcourse this would only be used to see where this anoying echo is coming from, then disabled afterwards when there is no use for it.

I support you

+1, tracking down this kind of stuff is practically impossible.

+2 I been trying to trace this echo down for weeks -_-

Nice support
Would it be hard to implement stefan?

yes very hard for stefan he is special

I was bored yesterday, downloaded every level, script, weapon and traced down every echo in a text file, I may or may not have gotten rid of it. Only time will tell.

Ive done the same thing @Tim, I've rounded it down to 200-250 echos, meaning un-commented, which I have looked, but can't seem to find anything that matches. This is why I created this thread, I shouldn't have needed to download every script to search for an echo...

Oh, I 100% agree with you. Have you noticed the echo happening lately?

I won't be online much during the week, so I won't be able to tell you

Update: Stefan said its on his todo list.

Also big this are coming apparently. :O

Wouldn't it be just as easy, and maybe offer more flexibility, if you made your own function to do echo's and make it also log (if conditions are true). Meaning certain things could log while others don't necessarily have to rather then just logging it all?

The problem here is that some scripter have added echos in some level or class and display some annoying output on server start, a simple scriptfunctionlog thing could help a lot for finding that.

This would not be to use 24/7 for every echo, it would be purely for debugging.
Lets say someone is echo'ing a boolean from a random test script in a random level then that staff member forgets it and decides to go on vacation for a week. That leaves us with one annoying echo we cannot find.

As Blue said, we'd only be using it if we actually needed it. Could be enabled/disabled through serverops.

Why not something like this?