I don't know if anyone has ever mentioned this but sometimes on a game you get idiots who send you super huge txt messages in private over and over again so they can try to disrupt or annoy you while playing the game. It would be really great if Blizzard made a /squelch *69 command so that you could squelch the last person who sent you a message.
Some people would ask, "Why don't you just type their name in" that only works when they have a name that can be typed in that isn't too long, if they use all capital I's and lower case L's then you will never get the combination right.
I hope someone from Blizzard actually does something about that problem. The command I just mentioned wouldn't even need a new dialogue box or anything though it would mean the software has to store the name of the people messaging you each time you receive a message.
They could put a selection in chat options, "enable *69 squelching" maybe even shorten it to just /s *69.
What do you think ? And yes I know they don't like to use * in chat commands... could probably do it without it but with its so much easier to remember.
Internally the game stores a record for each individual row of text; the name preallocated a static size of 16 to accomodate for the longest character name; this is why longer names are truncated and newlines break formatting flags. It would be a trivial fix, then again, alot of the issues with Diablo II are and we have yet to see them.
Indeed, differentiating glyphs of Diablo II's font has always been troublesome. One possible solution would be to simply change the font the game uses to something more easily discernable such as ... Courier (you can accomplish this quite easily, the game font is stored in d2_data.mpq/data/local somewhere iirc)
The last-sender based squelching is a good idea; I hope it's implemented.
Hehehe you know what the funny thing is. I was playing Warcraft 3 when I first had this happen, and everyone just assumed I was talking about the Diablo series. Still the problem is the same, people with incredibly long names that change them in random ways, and you aren't going to type in a squelch command and get it right, in the middle of a game even if you could distinguish the characters.
and though it doesn't make anything impossible, you wouldn't think it was primitive if someone was doing it to you filling up your screen....
Hehehe you know what the funny thing is. I was playing Warcraft 3 when I first had this happen, and everyone just assumed I was talking about the Diablo series. Still the problem is the same, people with incredibly long names that change them in random ways, and you aren't going to type in a squelch command and get it right, in the middle of a game even if you could distinguish the characters.
and though it doesn't make anything impossible, you wouldn't think it was primitive if someone was doing it to you filling up your screen....
Quote from "luc1027" »
???? Do you think Battle.net 2.0 will be unergonomic ???
....................
Like SFJake said, we're in 2010...
Is that the best answer you have ? It won't be now, then, so don't worry about it ? I don't know how I can respond to someone so lazy that they only made one sentence.
Less more discussion. See what I did there ? Creativity and elaboration, try it.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Some people would ask, "Why don't you just type their name in" that only works when they have a name that can be typed in that isn't too long, if they use all capital I's and lower case L's then you will never get the combination right.
I hope someone from Blizzard actually does something about that problem. The command I just mentioned wouldn't even need a new dialogue box or anything though it would mean the software has to store the name of the people messaging you each time you receive a message.
They could put a selection in chat options, "enable *69 squelching" maybe even shorten it to just /s *69.
What do you think ? And yes I know they don't like to use * in chat commands... could probably do it without it but with its so much easier to remember.
Indeed, differentiating glyphs of Diablo II's font has always been troublesome. One possible solution would be to simply change the font the game uses to something more easily discernable such as ... Courier (you can accomplish this quite easily, the game font is stored in d2_data.mpq/data/local somewhere iirc)
The last-sender based squelching is a good idea; I hope it's implemented.
Maybe realize that its 2010 and D3 will not include such... "primitive?" issues.
and though it doesn't make anything impossible, you wouldn't think it was primitive if someone was doing it to you filling up your screen....
....................
Like SFJake said, we're in 2010...
Less more discussion. See what I did there ? Creativity and elaboration, try it.