Hi, either please PM or email me so I can check this in the old ACK!MUD code and my continued AckFUSS work both. It's not nearly as popular a base as ROM, Smaug, or Circle, but is still part of the Diku/Merc family.
10 Jan, 2009, Hades_Kane wrote in the 30th comment:
You mean bugs never used to display on the MUD?
In ROM, they display in the shell.
That about says it. By default, the bug calls are saved in the logs, and if you don't check your logs often, there's no telling what you could miss.
I don't make a habit of checking my logs regularly, so having the bug call display to immortals who choose to see it has been a wonderful, if not obvious, addition.
There are things like that I run across and have trouble understanding why none of the authors of the codebase had thought of it as well. But then again, I run across so much bloat in the codebase too, that I have trouble understanding why so much of it is in there when it serves no purpose :p
Seeing it in the logfiles (or even if you set that to appear in wiznet) is not enough to stop this, especially if you have a player (as we had) who refused to do it while an imm was logged on.
I actually first saw this bug in the logfiles when it first came up (it DOES display as a BUG in logfiles), which first happened when this player first started playing (no other players in our mud's history have used it, as it is not a particularly well known bug, so let's keep it that way). I wasn't sure why it was displaying, and actually thought that it was my fault, as I had set some variables incorrectly in a number of commands that I had written myself, which, I imagined, could lead to the same BUG message. I actually thought that this bug message was incorrect, that there was no bug at all.
After I fixed up my own commands and was still getting the BUG messages, I was a bit annoyed, and assumed that I still had something somewhere that I had missed (as you would think).
Then I wrote a new command that accidentally gave an enemy double hits when you used the command. When I created Temari's fan skill Fusajin no Jutsu: Scythe Whirlwind technique, it gave the enemy double hits, at least when you used it wrong. I wasn't sure why, but some players helped me to figure out the bug. I had set up some of the variables wrong. As it turned out, I had done the exact same thing that the people who made the buggy stock Merc (or possibly stock Diku) command had done, but in reverse. I didn't mean to, of course, and it had taken all of 1 hour for one of our players to notice it and to work out how to fix it.
Then we were having unexplained crashes, 10 per day, which were really bothering me. Some of them were found to have been caused by one of our new features (I won't say which one, as that would hint as to what this bug is), and putting in various variations of them. I had to put in dozens of exceptions to get them to work. Rather than thinking that it was the stock code that was causing the problems, I thought that it was my code.
I eventually found the explanation for our crashes - I had put in END IF twice in a couple of mob programs. An insidious error, at the building stage rather than at the coding stage. Took me ages to find it.
But by the time that I had found that, I had already seen this weird stuff in the stock code, and thought that it might be the cause. When I finally got rid of the mob program problems, I saw that this could be quite a serious bug.
I tested it, saw that it was true, and conspired to spy on this player. As I had seen in the log files, they never abused it with someone there, so I went invis (wizinvis) to spy on them, then snooped them when they logged on. This caught them in the act, and saw it in physical form.
Finding a fix was tricky, as I had to get my head around it. If I fixed it, then it would disable the command, and it was a useful command. Finally I worked out a rather tricky if statement that would work. Worked perfectly. I was quite impressed with myself.
Seeing that it was known since 2002 does not surprise me. Also seeing that they couldn't work out a fix does not surprise me.
Please be aware that my 1-line fix does not stop any legitimate function of this command. You can still use it as it was intended. You just can't abuse it.
I'm the same way Ssol. I never log off. I'm usually just Invis. And even after two years of working on MW, people still don't realize that. :P I really should step things up a notch and actually work on game content instead of rewriting things, I should have an open mud after two years… Hmm..
10 Jan, 2009, Ssolvarain wrote in the 38th comment:
There was also the infamous newbie riot of 08, where I had to rename 12 belligerent newbies at once. Oh lord, to have had the global silence command then. Botters I can smite or smack or beat or… whatever. I'll stop here, because the things that occurred that day were either an extreme freak of nature or karma seeking revenge for catching that donkey show while I was down in TJ.