We all know how Diablo 1 lets you set your own statstring (sshr too i think), Well i was thinking, maybe if somebody was really bored, they could figure out a way to use the diablo statstring to chat with people in the void? ???
Seems pretty dumb, but hey, why the hell not? :P
QuoteWe all know how Diablo 1 lets you set your own statstring (sshr too i think), Well i was thinking, maybe if somebody was really bored, they could figure out a way to use the diablo statstring to chat with people in the void? ???
Seems pretty dumb, but hey, why the hell not? :P
You're a few years late, sorry!
This idea was new back in 1999 :p
You can also use it to chat in Blizzard Tech Support and other moderated channels.
damn, got the source? or the bot anywhere?
We'd just send new statstring that contained the message. When the client receives list event from user that is already in the channel, then display it as "Stat chat."
how did you locate it? like what type of key did you put, and where did you put it, to make the client say "hey this guy has a message in his statstring!"?
Stat update (0x0f event 0x09)
thats the flags event tho, that can happen anywhere at anytime, maybe not so much in the void, but its possible in blizzard tech support im sure...
So what?
Store each user's statstring, if the stats update event occurs and the statstring changes, treat it as statchat. Otherwise, don't.
Interesting, why was it stopped? did it get too pointless?
Hrmm.. I guess the same could be done with Profile string, but you would have to set a timer.
You could just set sex to "\nMessage" and be constantly checking for changes in other Sex fields.
(PS. Sex Fields would be a great name for a band!)
lol dork :p
can you still create your own profile string in 0x27?
like \profchat
?
Quotelol dork :p
can you still create your own profile string in 0x27?
like \profchat
?
No. If you attempt to set a non-default key, your whole profile will be reset.
thought so, damn
i guess the sex field would deam appropriate, but some people use it for encryption keys...
I'm not sure if its possible what im saying, being new to all this stuff but, if you could do this "stat string chatting", couldnt u use a muted key and still chat?
hmmm.....we could be onto something :o ;)
Edit add:
We could make a bot that changed statstring with a certain character in the beginning of the messages, like other bots do for hex messages. This way, the bot would read all statstring updates, and if the statstring has the character in the front, it would display it as a message. Just an idea tho...
QuoteStat update (0x0f event 0x09)
It's 0x01, 0x09 is for flags!
Bleh. Always use symbols for constants.
Quotehmmm.....we could be onto something :o ;)
Edit add:
We could make a bot that changed statstring with a certain character in the beginning of the messages, like other bots do for hex messages. This way, the bot would read all statstring updates, and if the statstring has the character in the front, it would display it as a message. Just an idea tho...
I think that you're forgetting that the only products which have statstrings set by the client are the ones which cannot join private channels.
Quotehmmm.....we could be onto something :o ;)
Edit add:
We could make a bot that changed statstring with a certain character in the beginning of the messages, like other bots do for hex messages. This way, the bot would read all statstring updates, and if the statstring has the character in the front, it would display it as a message. Just an idea tho...
Why do that when you can just check to see if the user is already in the channel when you received the 0x01 message from the combined packet. If he is, then display their statstring as "Stat chat."
QuoteBleh. Always use symbols for constants.
You started it.
I might have used SID_CHATEVENT, EID_SHOWUSER!
I was too lazy to look up the right symbols though. ::)
QuoteI think that you're forgetting that the only products which have statstrings set by the client are the ones which cannot join private channels.
Which brings us back to the idea of using a profile field...
Since Sex is used for encryption keys, why not use Age for sending messages?
This would, at the very least, allow you to use muted keys to chat :-)
I know it would be a lot of extra overhead to check the profile strings every few seconds, but I don't care :-P
that would be a good idea indeed, but what about the actual game clients? they can still set and view the age..
and if i remember correctly, you can lookup profiles some 8 or 9 in a row times before flooding, sending requests every second, or second and a half, wouldnt be that bad of an idea...
but then again, youd have to lookup everybodys profile in the channel, and that would suck...
Yea but you dont get a event thingie when someone updates their profile, you'd have to set timers checking, which would make chatting kinda hard...
Alternatively, save yourself a lot of trouble and just use an unmuted key?
Age is blanked out by the server now, BTW. Good thing we stuck with profile\sex? ;)
Bah, you're right, wasn't thinking when I said Age :-)
I guess we'd have to chat using Location. No problem, just start it with '\n'. To the untrained eye, it would seem blank!
QuoteBah, you're right, wasn't thinking when I said Age :-)
I guess we'd have to chat using Location. No problem, just start it with '\n'. To the untrained eye, it would seem blank!
No, with Battle.snp games the text spills over into the space below the edit box if it continues beyond one line.
Yes! Finally, another pointless feature to add to an already pointless-feature-bloated bot! Keep up the good work. Soon we can tally the amount of time we all wasted doing these things, and then compare! The most time wasted wins..
1. Who are you?
2. Most things here are not a waste of time, if you think of it that way, then leave.
3. Why dont you register if you're continuing to post here?
---
No, this is not a flame mods..
QuoteNo, with Battle.snp games the text spills over into the space below the edit box if it continues beyond one line.
This is true, but you can add crlf's in any profile string, so if you add 2 crlf's, after a normal message in the location string, then start with \n or whatever, blizzard game clients will not be able to view it.
Ethbot had statstring chat for a brief period of time - then I realized it was pointless. I can't remember who it was that actually got me to add it, but we used the double cross prefix to denote it was statstring chat(±).
Double cross?! nothx, it's the plus/minus!
That was the wrong symbol. I don't think we used the double daggar(‡) anyways. I believe we went with the single daggar(†).
sigh....