ASCII characters are 1 byte.
UNICODE characters are 2 bytes.

1 Bytes = 8 bits.

Maximum values us 2^K-1

255 possible characters.

Signed Value range is -2^(K-1) to 2^(K-1)-1

It can still represent 255 characters, however if you only take the leading positive values than its 127.

Unicode is 2^16-1 = 65535

Having taken courses in computer-related studies in University I would be a little more credible than a wikipedia article thats telling you a unicode character is 64-bits (8 bytes).

UTF-N is a method used to retain the size of the string even though the string may contain a null terminator. UTF-N also allows the grouping of the bytes representing a character to be changed to support different regional codes depending on the inital character range value.

Although the UTF-N still does not prevent misprinting, or improperly implemented algorithms to handle string manipulation.

Rather than opening wikipedia, I suggest you open something like Microsofts Development network website and read the information off of there. The difference is, one is published by real-world developers, and the other is posted by some individual who may or may not have accredited knowledge on the subject.

Here I'll even point you to it:

http://msdn.microsoft.com

Yes I remember! It was a dance emote, I think. Or something like that. When someone does the emote, everyone around them crashed. It was like, back in CB. I only vaguely remember. But yeah, it was this game, haha.

And I'm getting a bit confused by this. Is finding who's not d/c'ed the only way to find out if someone is exploiting the bug? D: Or is there some other way to tell?

dude if u want u can read about ascii and unicode as much as u want. But wikipedia has some real good articles about them.

ascci uses 7bits, not 8. the highest bit is NOT used.

and if its 8bit then there are 256characters. 255 is just the highest value for an 8bit long block. UInt8= 0..255.

and that u point to the msdn. LOL
ascii, unicode are not from microsoft.

In short u are just a beginner, but u think u already know everything. :)

They requested that if we know anything, to please PM them. I'm sure they won't turn down theories or any kind of hint as to what it could be. So if you guys know anything that it could be, please PM it to one of the GMs.

For all of the players of Fiesta!!*dresses like William Wallace*

Attention
 

This is not a bug people, is a hack. I recall that a while ago someone on the forum of outspark posted a few links that dirrected the user to a forum where someone (who will remain unnamed due to the fact that it is very likely it was an impersonator and not the person with the designed forum-name) was clearly trying to sell in that other forum a hack that would crash everyone online as far as he/she called that. THE person was selling a home-made hack that would do just that. AT first i though it was BS but now i recalled that and well..... it is pretty possible seeing how that occurs. Also the hack causes Rebuff Overrun or something like which is the main cause your game will crash. At first it will show u the error than it will just automatically dc u.

Since the gms dont want any help from me anymore
i will just publish the sollution here:

The Message we are talking about has the Id 0x2001.
It build like that:

struct ChatMessage
{
char count;
char message[];
}

The hacker did most likley send a message where the count value is lower then the actual size of the message. I dont knew where the bug exactly is, but i know that the client will crash if the count is to low.


And no that not the message that will actually crash the client, its the message the hacker sends.

Everyone who wants can take it to the gms, he may give me the credit but there is no need :-)

Edit: Just to make it clear: i did not found the hack in the first place, nor do i create such hacks. I also NEVER sell my hacks.

Edit2: i just did 1 test. It was with a string filled with 1024 a's, and a length of 0. Of course the server response crashed my client.

You mean that whole thing with Pr0n?

Academic source. Perhaps you should review the validity of the content first before saying wikipedia is a trustworthy source of information.

A unicode character is clearly not 64-bits - as you so pointed out in your initial post.

7 Bits, initial set.

Two complements signed integer. All positive values are used for the initial set.

8 bit, extended set.

Unsigned integer allowing the use of all values.

256 integral values represented. However, 0 is reserved as a null terminator. 255 possible values. More generally 2K-1.

I point to MSDN because its a credible source. Its not editable by anyone out there.

If you want, I can direct you to the java language where they use unicode as the primitive character type - which is clearly not 64-bit.

Assumptions. Perhaps I dont know everything, but you've demonstrated your lack of knowledge about the subject. Furthermore, when intending to insult someone, you may want to use the English language a bit more appropriately, otherwise it just looks bad on your part.

I got hit by this on Bijou yesterday >.> Luckily in my case I was just dc'ed twice in Uruga. My guild leader got dc'ed 10 times in a row Dx

OMG, plz finally start actually informing yourself. But us stop here.

My last words :-)

Unicode encoding is not an easy feat.

As for Ascii, yes there is an extended Ascii, but its an common error to believe that extended Ascii is an newer Ascii. NO its not. Ascii has and will ever use 7bit +1bit padding on most maschines.


the 0byte is an character in Unicode, Ascii and extended Ascii known as terminator.

And my experience goes back into the times where dos was standard. But im quite happy that i never had to write unicode libraries.
And yes english is not my first language.