'echo' as a log-able function

[BlueMelon]

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. 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.

[Fidel Castro]

I support you

[cbk1994]

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

[MysticalDragon]

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

[Tim_Rocks]

Originally Posted by MysticalDragon

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

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.

[BlueMelon]

Nice support
Would it be hard to implement stefan?

[Hezzy002]

yes very hard for stefan he is special

[BlueMelon]

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...

[Tim_Rocks]

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

[BlueMelon]

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

[BlueMelon]

Update: Stefan said its on his todo list.

Also big this are coming apparently. :O

[scriptless]

Originally Posted by BlueMelon

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?

[BlueMelon]

Originally Posted by scriptless

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?

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.

[scriptless]

Originally Posted by BlueMelon

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.

PHP Code:

function NewEcho() {
  echo();
  log();
} 


And just logging the level the npc is in and the message it sends? You could even do npc id's or just about any other way.. you at least narrow it down to the level this way. And you don't have to wait for the Graal Engine to be updated just to save a few lines of script?

The 1 thing I notice is using something similar you could also alternatively pass a string to NewEcho() that would let you make it not log so that you don't eat up the disk space.. Which might be pretty cool. Because if there was an edit to make it optional it would probably be best to allow such flexibility rather then log everything.

Sorry if I am just horrible misunderstanding the problem I never had this that issue yet, knock on wood.

[Crow]

It'd be impossible to enforce usage of such a function. Point is: some scripter has debug output anywhere using echo(), nobody knows where, it constantly echoes to RC.