Plugins stopped working

Posted by Shabby on Thu 22 Nov 2012 04:04 AM — 8 posts, 26,812 views.

Shabby Thu 22 Nov 2012 04:04 AM #0

New to mudding, as well as scripting, so please be patient. Had several plugins up and running, modified to work with my mud. Also had a home brew that worked as well. Three times now they have all quit running for no identifiable reason. Reinstalling client fixes the problem, but only for a day or so. Restarting client fixes nothing, uninstalling and reinstalling plugins does nothing, rebooting computer nothing.

Using most recent version of mush, running on windows 7.

Fiendish USA Global Moderator Thu 22 Nov 2012 04:21 AM #1

I'm sure the whole experience is quite difficult for you, but this is not a very useful report.

Nick Gammon Australia Forum Administrator Thu 22 Nov 2012 07:35 AM #2

Shabby said:

Had several plugins up and running,

Which plugins?

Shabby said:

Also had a home brew that worked as well.

What does that mean?

Shabby said:

Using most recent version of mush, running on windows 7.

Which version?

Shabby Thu 22 Nov 2012 01:16 PM #3

Heh, sorry for the lack of info, was a late night when posting.
Details:
MUSHclient v 4.84
Plugins:
Health_Bar_Miniwindow (as is, changed server prompt to match scripting)
Chat_Redirector (modified to match my MUDs chat info)
Omit_Blank_Lines (as is)

Plus plugin I modified from Chat_Redirector to capture group information in secondary window.

I'm very grateful for any help, and again I apologize for the lack of information in my original post.

Fiendish USA Global Moderator Thu 22 Nov 2012 05:26 PM #4

Quote:
Reinstalling client fixes the problem, but only for a day or so. Restarting client fixes nothing, uninstalling and reinstalling plugins does nothing, rebooting computer nothing.

Would seem to indicate a state variable issue.

Please post the actual plugins. And further describe the scenario: "they have all quit running for no identifiable reason". You need to give us surrounding details. What are you doing when the problem happens. What is the game doing when the problem happens. What do you see when the problem happens. What things do continue to work. Etc.

Quote:
The first aim of a bug report is to let the programmer see the failure with their own eyes. If you can't be with them to make it fail in front of them, give them detailed instructions so that they can make it fail for themselves.

In case the first aim doesn't succeed, and the programmer can't see it failing themselves, the second aim of a bug report is to describe what went wrong. Describe everything in detail. State what you saw, and also state what you expected to see. Write down the error messages, especially if they have numbers in.

-- How to Report Bugs Effectively by Simon Tatham

Nick Gammon Australia Forum Administrator Thu 22 Nov 2012 07:02 PM #5

Shabby said:

Three times now they have all quit running for no identifiable reason.

Do you mean there's an error message? If so, what is it? Or do they just stop doing their stuff? Like, does "omit blank lines" stop omitting lines? Or do they do something unexpected? If so, what?

Do all of them fail, or just one?

Shabby Thu 22 Nov 2012 07:37 PM #6

There are no error messages to report, they just stop responding completely, stopped "doing they're stuff". As for the plugins, did you want the script copied over for review?

Nick Gammon Australia Forum Administrator Fri 23 Nov 2012 04:31 AM #7

Well, starting with "omit blank lines". You say that is unmodified. And now blank lines are not omitted?

They are omitted for a while, and then, for no obvious reason, they are not?

Are the plugins enabled in the plugins dialog box? (File -> Plugins)

Are triggers enabled? Configuration -> Appearance -> Triggers.

I assume you get blank lines from the MUD fairly often. Can you turn on Trace (Game menu -> Trace) and do something that sends a blank line. Then report what the trace tells you.