Register forum user name Search FAQ

Gammon Forum

Notice: Any messages purporting to come from this site telling you that your password has expired, or that you need to verify your details, confirm your email, resolve issues, making threats, or asking for money, are spam. We do not email users with any such messages. If you have lost your password you can obtain a new one by using the password reset link.

Due to spam on this forum, all posts now need moderator approval.

 Entire forum ➜ MUSHclient ➜ General ➜ Omit From Output
Omit From Output

It is now over 60 days since the last post. This thread is closed.     Refresh page

Pages: 1  2 

Posted by DariRyu   (12 posts)  Bio
Date Reply #15 on Fri 06 Jan 2017 01:40 PM (UTC)
Message
Seems so, yeah. It's always three lines, and they always both start and end with ##.

Also, I added another one to my previous post, an unbearably stupid one.
Top
Posted by Nick Gammon   Australia  (23,158 posts)  Bio   Forum Administrator
Date Reply #16 on Sat 07 Jan 2017 12:21 AM (UTC)
Message
Are these the only messages that start with "##(space)"? Or are there other ones?

Are the messages in any particular colour (assuming the MUD colours its output)?
- Nick Gammon

www.gammon.com.au, www.mushclient.com
Top
Posted by Fiendish   USA  (2,537 posts)  Bio   Global Moderator
Date Reply #17 on Sat 07 Jan 2017 01:38 AM (UTC)
Message
Quote:
Are these the only messages that start with "##(space)"? Or are there other ones?

And if there are others, are there others that come in batches of three?
https://github.com/fiendish/aardwolfclientpackage
Top
Posted by DariRyu   (12 posts)  Bio
Date Reply #18 on Sat 07 Jan 2017 07:05 AM (UTC)

Amended on Sat 07 Jan 2017 07:23 AM (UTC) by DariRyu

Message
These are not the only messages. As I said, there are others, at least one that I can think of. One details a failed ice cream-procuring trip because another anime character has an ice cream cone with several scoops on it.

I don't have a list of them though, because I'm fairly certain if I asked the staff on the place for behind-the-scenes information like a list of them, I'd probably get laughed at. And then oh-so gently denied.

This is, however, the format all these messages follow -- three messages, all ringed with ## and a space. Because the three messages represent the three stages of database saving -- "preparing to save", "saving", and "save finished". None of the messages are colored, to my knowledge, just normal dull white text on black background.
Top
Posted by Nick Gammon   Australia  (23,158 posts)  Bio   Forum Administrator
Date Reply #19 on Sat 07 Jan 2017 08:46 PM (UTC)
Message
Well, the most reliable way would be to build a list of the known ones, and then omit them when you see them. I presume there is a reasonably finite number of them.
- Nick Gammon

www.gammon.com.au, www.mushclient.com
Top
Posted by Nick Gammon   Australia  (23,158 posts)  Bio   Forum Administrator
Date Reply #20 on Sun 08 Jan 2017 12:27 AM (UTC)
Message
The simple solution, assuming that the server sends a single line, is to make a trigger like this:


<triggers>
  <trigger
   enabled="y"
   match="## * ##"
   omit_from_log="y"
   omit_from_output="y"
   sequence="100"
  >
  </trigger>
</triggers>


Template:pasting For advice on how to copy the above, and paste it into MUSHclient, please see Pasting XML.


That omits all lines starting with ## and ending with ##. It also omits them from the log file.

That seemed to work on your test data. Now if you get the occasional line that is omitted that shouldn't be, you could make an "exception" trigger with a lower sequence number. That would match first, and stop this trigger from reaching it.
- Nick Gammon

www.gammon.com.au, www.mushclient.com
Top
Posted by DariRyu   (12 posts)  Bio
Date Reply #21 on Sun 08 Jan 2017 05:27 PM (UTC)

Amended on Sun 08 Jan 2017 06:55 PM (UTC) by DariRyu

Message
And as it turns out, general MU* announcements, watchfor (this is connection alerts of friends on a list), and shouts are all ringed with ## as well. Thus it's been strongly suggested by staff there that I don't use the trigger. However, staff has also stated outright that they are completely and utterly unwilling to even consider trimming these save messages, let alone removing them entirely, because "they've always been a thing". Nor will anyone attached to staff give me a full list of these messages so that I may block them individually, because it's too much trouble to dig through the database. So I'm rather stuck.

I don't really think there's anything else I can do in this situation. But I thank everyone here for their cooperation and willingness to help, even though I don't have the brainpower to understand most of the higher functions of MUSHClient.
Top
Posted by Fiendish   USA  (2,537 posts)  Bio   Global Moderator
Date Reply #22 on Sun 08 Jan 2017 07:13 PM (UTC)

Amended on Sun 08 Jan 2017 07:18 PM (UTC) by Fiendish

Message
I still suggest looking for batches of three of these lines and deleting them on that condition.

Ignore Nick's suggestion to omit on each. What you actually need is two triggers. One for the pattern and one for everything else. I'll call them A and B. A should have a lower sequence number so that it fires first. You also need a variable that counts the number of times A has fired before B fires.

When A fires, increment the counter. If the counter hits three, reset the counter, call DeleteLines(3), and then StopEvaluatingTriggers().
When B fires, reset the counter.
https://github.com/fiendish/aardwolfclientpackage
Top
Posted by DariRyu   (12 posts)  Bio
Date Reply #23 on Sun 08 Jan 2017 07:16 PM (UTC)

Amended on Sun 08 Jan 2017 07:22 PM (UTC) by DariRyu

Message
I've decided to use Nick Gammon's trigger. The staff there were rude when telling me the lay of the land as far as their opinions on the save messages. Since they're unwilling to work with me in any way, shape, form, or fashion, I don't feel it's unreasonable to emit a small portion from my output buffer, as it does not change the way the service works or is accessed for anyone else, and does not affect anyone but me. In my opinion, if anyone is being unreasonable it's them.

Additionally I've decided to go with Nick's trigger because I honestly have no idea what you just said, Fiendish. As I mentioned a couple posts back, I have no capability to code, and I don't understand any of the explanations given in the help files for coding. This is not something I can help, I just do not have the intelligence to figure these things out.
Top
Posted by Fiendish   USA  (2,537 posts)  Bio   Global Moderator
Date Reply #24 on Sun 08 Jan 2017 07:22 PM (UTC)

Amended on Sun 08 Jan 2017 07:24 PM (UTC) by Fiendish

Message
DariRyu said:

The staff there were rude when telling me the lay of the land as far as their opinions on the save messages.

It's possible that they were rude when they told you no, but complaining about game owners not wanting to change _their_ game for you is backwards. There are a thousand other MUDs out there for you to try that won't have this weird problem. You've just gone into someone else's home and told them you don't like their carpet.
https://github.com/fiendish/aardwolfclientpackage
Top
Posted by DariRyu   (12 posts)  Bio
Date Reply #25 on Sun 08 Jan 2017 07:29 PM (UTC)

Amended on Sun 08 Jan 2017 07:46 PM (UTC) by DariRyu

Message
That analogy doesn't quite work, because I'd assume you don't publicly invite people you've never met into your house to play a game with you. This is, then, a public venue. By the same token, if the people setting up a public venue make said venue in a way that I find unpleasant in some way, I feel that I should be free to alter my perception of said venue in any way that I choose, so long as it does not affect anyone else's perception of, or access to, said venue. This is, in fact, what I am doing.

And I'm also not the only one of their players to complain about this; additionally it's only a SINGLE staffer who refuses to change the messages, when several of the other staffers AND players have asked him numerous times to do so.

However, I now have an adequate solution to the problem. Thank you all very much for your assistance.
Top
Posted by Nick Gammon   Australia  (23,158 posts)  Bio   Forum Administrator
Date Reply #26 on Sun 08 Jan 2017 11:45 PM (UTC)
Message
DariRyu said:

And as it turns out, general MU* announcements, watchfor (this is connection alerts of friends on a list), and shouts are all ringed with ## as well.


If there is some pattern to these announcements (eg. "Peter shouts xxx") then it may well be possible to catch those first and those save them from being omitted. In other words:


  • Trigger sequence 90 (evaluated first) looks for:

    "## * shouts * ##"

    If found it does nothing (however by merely matching it stops other triggers from being evaluated).

  • Trigger sequence 100 (evaluated later) looks for:

    "## * ##"

    This omits from output and from the log file, so that messages that don't match the first trigger are not omitted.
- Nick Gammon

www.gammon.com.au, www.mushclient.com
Top
Posted by Fiendish   USA  (2,537 posts)  Bio   Global Moderator
Date Reply #27 on Mon 09 Jan 2017 11:49 AM (UTC)
Message
Nick Gammon said:

If there is some pattern to these announcements (eg. "Peter shouts xxx") then it may well be possible to catch those first and those save them from being omitted. In other words:

So far it sounds like the only pattern we know of is that the bad messages come in groups of three and the others don't.
https://github.com/fiendish/aardwolfclientpackage
Top

The dates and times for posts above are shown in Universal Co-ordinated Time (UTC).

To show them in your local time you can join the forum, and then set the 'time correction' field in your profile to the number of hours difference between your location and UTC time.

68,959 views.

This is page 2, subject is 2 pages long:  [Previous page]  1  2 

It is now over 60 days since the last post. This thread is closed.     Refresh page

Go to topic:           Search the forum

[Go to top] top

Information and images on this site are licensed under the Creative Commons Attribution 3.0 Australia License unless stated otherwise.

Home