Zugg Software :: View topic

Adept Joined: 18 Jun 2019 Posts: 279

Once again, these were working without fail until today. I thought it was gmcp problem. I quit and restarted client and all worked well for a couple of ticks then nothing.

Posted: Sun Mar 28, 2021 5:33 pm

Would you drop it with complaining about Zugg already?
His life choice are not the cause of your current issue.
Your complaints and tongue-in-cheek suggestions aren't going to do anything but turn the community against you.
We get it, changes in the program would be nice.
Adding in a little dig each time you mess up your code makes me want to help you less and less.

If it was working fine, and now it isn't there is only one possible cause.
Something in your local settings has changed. Intentional or not.

Now I can help you pinpoint the mistake you made, or you can harp about how Zugg moved on to pay his own bills.

Adept Joined: 18 Jun 2019 Posts: 279

You may be right but...

I disabled all modules, then went into the main window module and started disabling other things. I reiterate that window handling in CMUD is slack and buggy and problems
one may think are not related might well be. I restarted and ended up with same problem and nothing triggering, just with client/mud communication as all I was trying to do
was a speedwalk of portal,d,e,d and every 'command' was 16.

Restarting client and all working again. However, I remain skeptical that it is not likely to occur again.

Posted: Sun Mar 28, 2021 6:25 pm

It may well reoccur, but short of being able to force it to occur, there is no way to figure out the cause of the issue.
I think I have hit that particular issue before myself even.

It's how you go about dealing with the problem.
CMUD can do almost anything you would want of a MUD client.
I would say almost all issues (95+%) in CMUD boil down to syntax error.
Meaning the end-user is at fault.

Blaming Zugg, because your code did not spit out the expected results, just makes it look like you want to play the blame game rather than actually troubleshoot the cause of the incongruency.

Adept Joined: 18 Jun 2019 Posts: 279

I think disabling every package was fairly conclusive. The main session window and the mapper were the only things left running. After disabling the one thing in the main session, which was a gmcp trigger, that could have been a factor, and the error still spamming '16' to the (as I said for a 4-step speedwalk), I deduced that the problem lies with a thing inherent in the application itself that disagreed with some unknown. The only thing left to ponder was something with the windows, especially as it is so easy to move something and have all kinds of unexpected side-effects with buttons appearing everywhere or all output disappearing, etc

The fault may well still lie with something in the scripts but, as you and I (and no one else) have no clue as to what this cryptic stuff means, or why it is generated, it will never get resolved.