Zugg Software :: View topic

Posted: Tue Jun 17, 2008 11:59 pm

does 2.28 include #bringtofrontandmaximize? ;) or a name for the system menu so we can do #menu {system|Maximize} or something? I forget the exact syntax but i know there's syntax for calling menus like that!

Apprentice Joined: 05 Apr 2008 Posts: 121

BTW
This is disabled in 2.29
but it still seems to lock up cmud when you attempt to use it.

Posted: Thu Jul 03, 2008 4:48 pm

Confirmed the lockup in 2.29. Sorry I had forgotten to add that to the bug list...I got distracted by the exploit.

Posted: Thu Jul 03, 2008 5:00 pm

Easy fix, put the exploit back in and fix the bug :) things will even out and we'll forgive you :(

Wanderer Joined: 24 Jun 2008 Posts: 68 Location: Texas

I really hate seeing all the people complaining about this exploit being fixed. It makes me lose a little bit of faith in humanity. Or at least MUD players.

As a MUD admin, I agree that players should -never- have the ability to create new lines on another player's screen, no matter how 'harmless' someone thinks it might be. It doesn't matter if it's a joke, you are exploiting things you shouldn't to make players see things they really aren't. It's malicious enough just in itself that I'm glad this exploit has been fixed, not even considering all of the other even more malicious uses it was opening up, as Zugg was explaining.

I'm glad I ran across this thread. All the more reason I have to push CMud as my official client from now on. I hate the thought of players even doing like the topic creator was insinuating and creating new lines for 'joke purposes'. Said person would be banned immediately for doing such things from my own MUD, and I'm a bit surprised that Aardwolf doesn't have their own rules against this kind of thing. It doesn't matter how lighthearted the intent of the user is when the exploit opens up so much more malicious potential. Not only that but it is allowing the player to create new lines on other peoples screens in situations where the MUD normally doesn't allow or control it. If you were meant to be able to make a new line in that manner, the MUD has the ability to give you that control and they would if they wanted to. It's not something that should be client based.

Posted: Thu Jul 03, 2008 7:13 pm

Nicodareus: well said.

The bug that was causing the lockup turned out to be anything on the command line where the ; character was followed by @ or % (or at least in most cases). This was a serious parser loop and is fixed for v2.30.

Posted: Fri Jul 04, 2008 12:11 am

Just to clarify Nico, we don't allow it out on public channels where it can be harmful. I found this character a while ago and it didnt occur to me to treat it as a bug, just thought i'd found a nice little html entity. Since then we've regularly used it on clantalk to fake PKs of each other, pretend to allow disliked players into the clan, etc etc. Sure it leaked out a little further, but the imms were pretty good when it came to making sure it didn't get out of hand.

Oh, and of course, there was the flickoff and cows*** immonly socials that we could emulate.

Honestly I think it's good that it is being fixed, but enjoyed it all the same.

Next time i make a post in jest i'll wrap it in <InJest> tags for you ;)

Wanderer Joined: 24 Jun 2008 Posts: 68 Location: Texas

Noone said my post was directed solely at you. In fact, it was minimally so. The fact remains that if this behavior was to be intentionally allowed by the MUD, they could provide you with a server-controlled character sequence to do so. Abusing bugs to do it is hardly a feasible solution.