Author Topic: Client-sided message  (Read 1364 times)

How would I get a client-sided mod to display me a chat message?
Bad example:

Person1: | olajwfo oi3u
Decoded "loving stuff"

and the second message gets created by a client-sided script

newChatSO.addLine( string );

do you mean encrypted chat?

do you mean encrypted chat?

No, he's asking how to add a line to the chat HUD which I already answered above.



do you mean encrypted chat?
Combination of ROT26 and ROT10 is the best encryption.

Combination of ROT26 and ROT10 is the best encryption.
Why is that?

Why is that?
Caesar cipher. ROTn = move all letters n letters "forward" in the alphabet while wrapping. Since there are a total of 26 letters in the (english) alphabet ROT26 be like asking you to spin a ball 360 degrees. ROT10 is the same but for numbers.
« Last Edit: May 26, 2012, 07:39:20 PM by DontCare4Free »

Caesar cipher. ROT26 = move all letters 26 letters "forward" in the alphabet while wrapping. Since there are a total of 26 letters in the (english) alphabet it'd be like asking you to spin a ball 360 degrees. ROT10 is the same but for numbers.
Why not ROT25 and ROT9 then? I know that the one in the middle (either ROT13 or ROT14) is the most common, but aside from that why not the other valid ones?

Why not ROT25 and ROT9 then? I know that the one in the middle (either ROT13 or ROT14) is the most common, but aside from that why not the other valid ones?
Because ROT26/ROT10 is the most efficient both in en- and decrypting! Seriously though, ROT13/ROT5 is the most common because the same algorithm is used both ways.

Because ROT26/ROT10 is the most efficient both in en- and decrypting! Seriously though, ROT13/ROT5 is the most common because the same algorithm is used both ways.
Ok cool

ROT13 is most common, because ROT13 is the same loving thing if applied to a string twice.

why not putting all numbers/letters/brackets/whatever in a long line and doing a ROT32

HEY GUYs, DO A ROT26