So, anyways, I want to know how to read and write either an SOL or TXT file using Flash (TXT file is much preffered since I can encrypt and decrypt it. Then again, if you can break into an SOL, you can probably also decompile a SWF and find the cypher, but that would be more work)
Any insight on this would be greatly appreciated.
Nevermind, I figured it out. For other people who want to know how to do this, look up SharedObject in your Flash API.
For an example of how to save an SOL file, see my code in the 4th post
EDIT: I'll post my tutorial right here:
~~~Exüberance's Mini-Tutorial:~~~
Let's start by writing to an SOL file. Let's do it by example, and you should be able to see how it works.
Code: Select all
var awryArray:Array = new Array(42, 88, Math.PI);
var isExuberant:Boolean = true;
var namezorz:String = "Exüberance";
var my_so:SharedObject = SharedObject.getLocal("SOLtest"); //This indicates the filename (SOL will be saved as SOLtest.sol)
my_so.data.awryArray = items_array; //next 3 lines are the data saved to the SOL
my_so.data.isExuberant = currentUserIsAdmin;
my_so.data.namezorz = currentUserName;
my_so.flush(); //the flush command actually writes the information to the file
¿ ~TCSO SOLtest itemNumbers 0 @E 1 @V 2 @ !ûTD- adminPrivileges userName Exüberance
And here's another version which does the same thing, but now displays if the process was completed or if Flash failed writing the file.
Code: Select all
var awryArray:Array = new Array(42, 88, Math.PI);
var isExuberant:Boolean = true;
var namezorz:String = "Exüberance";
var my_so:SharedObject = SharedObject.getLocal("SOLtest"); //This indicates the filename (SOL will be saved as SOLtest.sol)
my_so.data.awryArray = items_array; //next 3 lines are the data saved to the SOL
my_so.data.isExuberant = currentUserIsAdmin;
my_so.data.namezorz = currentUserName;
switch(my_so.flush()) {
case 'pending': trace("Writing to file..."); break;
case true: trace("W00T! File saved successfully!"); break;
default: trace("Uh oh! An error occurs writing the file. You are eaten by a grue."); break;
}
Code: Select all
//Well, input worked good... as far as we know. But, did it really write the data correctly?
//Let's find out by retreiving the data... lolcat style!
var I_can_has_data:SharedObject = SharedObject.getLocal("SOLtest"); //opens up the file to read
for (var my_varz:String in I_can_has_data) { //recall that the changing variable in a for..in loop is a string containing the name of the variable in the object, not that value itself
trace("I has a " + typeof(I_can_has_data[my_varz]) + ". It has a " + I_can_has_data[my_varz]);
}
//note how this returns a single object. This is because the data is parsed as a single Data type object, rather than serpatate entries as it appears when writing data to the SOL
//Now let's get the data from that object
/* Commented out for reasons below
for (var mah_objekt:String in I_can_has_data) {
for (var my_varz:String in I_can_has_data[mah_objekt]) {
trace(I_can_has_data[mah_objekt][my_varz]);
}
}
*/
//but wait, we don't need to do this. We know that I_can_has_data will only ever have 1 element, and it will be data. Instead, let's use
for (var my_varz:String in I_can_has_data.data) {
trace(I_can_has_data["data"][my_varz]);
}
//The output to the above 3 lines should be:
/*
Exüberance
true
42,88,3.14159265358979
/*
//I'm in ur code, getin ur dataz.
//Look's like we got all the data! Now you know the basics of using SOLs. Happy coding!
//But, what's this? You say you want to get specific data, not just all the data. Easy! Instead of using the for..in loop, just replace [my_vars] with ["namezorz"] or .namezorz or whatever the name is.
Notice how, you use the same command to open an SOL for reading as you do writing. Isn't flash nice?
A little bit on encryption (no, not RSA. That would be kind of pointless since you're sending the info to yourself)
Now, if you want to encrypt your file so people can't read it, you might want to use a simple form of encryption in which the data is converted to a string, then you shift the ordinal values of the strings around to get different characters. Of course you don't just shift everything up 5, you would shift each number up by a different pre-defined number (ex with numbers instead of letters: Message: 1337 Key: 8532, Encrypted Message: (1+8) (3+5) (3+3) (7+2) = 9869. Notice how the first and last number encrypted are the same, but the first digits of the original number are not. Also, the middle 2 numbers of the original message are the same, but not when encrypted. If the key is as long as the message. (you would "wrap-around" using modulo, of course, and make sure that you never get ordinal value 0 (null character) or bad things happen.) It's impossible to decode unless you KNOW either what the original message is, or you know a range of things the original message could be and you have a lot of time on your hands. Obviously, this won't be secure if you're encrypting a single digit number, so instead you would generate a random number of non-number characters with the number stuck in a random position there, then encrypt that. When you decrypt it, just look for the things that's a number. As I said before, if the person KNOWS the original message, they can hack the key. (ie, if they know their score in the game is 1337, then they see "Score: 9869" in the file, they can easily crack the code. One thing you could do is name score "jskdfhskj" instead of "score", but a patient hacker could still easily figure out which one is the score, by going into the game and only changing the score. But there's lots of simple, easy things you can do that make breaking the code much much harder. But, this is a tutorial about saving and loading files, not basic encryption. One fun thing you could do to prevent the trial-and-error method of breaking the key is make the file wipe all of it's contents if it received invalid input. Also, instead of using the same key all the time, you could generate a key that depends on something like the number of characters in the file, then add some meaningless variable whose sole purpose is to change the length of the file. Nothing is really fool-proof, but you can make it so hard that no one would ever care to do it. It would be easier to decompile the SWF.
