This is an (extended) ASCII representation of text.
It corresponds to, in this case, the characters forming the string "local Songs ".
Strings are lists of characters. In Lua, a character is exactly one byte, which is a fundamental unit of computer memory. One byte can be any of 256 values; so ASCII* assigns one character to each of the numbers 0 to 255.
You can make strings by making a list of those character points.
Using string.char(byteValue) you make a single character from a number; using string.byte(character) you make a number from a single character.
The purpose of this most of the time is for scripters to attempt to obfuscate their code from people trying to read or modify it.
It is easy to undo this, though, so it's not particular effective, except that people not immediately familiar with it cannot understand what to do.
Since these strings can't actually be executed on their own, they need to be run through loadstring; since ROBLOX doesn't allow bytecode anymore, this text needs to be (more or less) human readable.
So, we can always crack any amount of simple string manipulations like this trivially:
local floadstring = loadstring;
function loadstring(s)
print(s);
return floadstring(s);
end
Asterisk:
Technically, what Lua uses is not ASCII. ASCII actually only assigns 128 characters, not all 256;
ROBLOX uses Windows 1252 I believe. The text inside of that used for Lua code, which is limited to the newlines, tab, letters, and basic math, are the same in most single byte formats (including ASCII).
That means the extensions are essentially just cosmetic (think Wingdings).
3 comments
Oh yeah, I've seen an old CFrame door use something like that. My guess is it's an outdated way of setting a target CFrame or such.
deatherapy is referring to CFrame's nature of being a 3x4 matrix. While it's not smart to, you can explicitly define CFrames by listing their 12 defining numbers. The quoted values are not a valid CFrame though, so this guess is wrong.
ooh an old post by thee death caster, EPIC