Toxic: To put it in simple terms, I have a problem.

A recent train of thought has guided me to realize that my game has a small issue. First, the good news:
The game will still release, things are going good so far, and this issue does not affect the beta version of the game.
The issue that I have discovered is that of saving- in this case the lack there of. As of now, I haven't found a way for the game to save. If I cannot find a method of saving data, this will lead to one of two things. One- You will have to complete the game without ever closing the window. Or two- I will have to upload the game to some site that will alow a user's data to be saved as a document or online cookie.
Again, this will not affect the beta because I didn't plan on making the beta a savable thing, only a test.
In case you plan to tell me that saving is not possible because this is a flash game (a really big flash game, mind you), when I first had the idea to crate this game I didn't know any other coding language- and I still don't. However, if I can convert this .swf into JavaScript and work on there, I am willing to learn JavaScript and make the game on there.

Now, describe this overly-long dramatic description as dramatically as possible.

Shotgun_Observations: Now, I know you might not like this solution, but I'm not really a tech wizard. I simply use logic. How about you cut it into smaller pieces?

Shotgun_Observations: Or at least make it so the different sections of the game can be accesed through different flash games. Like, leaving a link to the next part of the flash game. It doesn't fix the saving problem, but it would be a temporary fix.

Toxic: @Shotgun_Observations: I've thought about this, and it theoretically would work and would actually make the game run smoother, but then it raises the problem that data such as items and skills wouldn't save between sections. As a temporary solution however, this would definitely be a good alternative to completing the game in one playthrough.

Kazerad: What about codes? Like, old games had them, where you’d be given a code to pick up where you left off. Usually it was per level, but you could easily make the code store inventory and stuff too.

Romann: You ever played cookie clicker ? In this game (and probably many others) you could save the game by :
A) Using cookies. The game automatically does it every minute... The problem with that method is, if the player deletes all their cookies, they would lose all progress. But the a conveniant method.
B) Use a string of characters. Basically, it’s like passwords on old games. However, you need to have your code generate the string.
C) Let the user download a text file in which all the useful data is stored. It’s extremely useful for backups, however, it the player could easily undo something they didn’t want to happen.

Maybe you could use one of those methods.

Romann: *But this is a conveniant method.

AMKitsune: @Toxic: Assuming you're working with actionscript3, try looking up 'shared object' tutorials. They're probably one of, if not the easiest ways of saving and loading data with flash.

Toxic: @Kazerad: I actually have experimented with these kinds of codes and they ended up being a couple hundred different digits. The problem however was I couldn't figure out a way to copy them to the clipboard, as you can't highlight text in flash while it is running. As an alternative, I tried to create a document with the text on it but that wouldn't work either.

POMA: You can automatically copy the code to clipboard.
https://help.adobe.com/en_US/ActionScript/3.0_ProgrammingAS3/WS2F6A31B9-1AE6-4b23-9C12-57A33F4F0516.html

DarthVader: Keep up the good work! I am ready for this game to release!

Streetwind: I once played a flash game that could write save states to local disk, and also load them again, even while living on the web.

Now if only I could remember the blasted thing's name... it must have been at least ten years since then.

Little_ducko: @Toxic: use a password system, like thos old games