I support this, it is difficult to know what topics are relevant.

That doesn't turn at a specific point.

There is no syntax error there. The issue is more like a logic error where the state variable loses sync with the real property if the user hits escape to forcibly leave fullscreen.

As 3 is easier to code in, since it tells you when it finds an error.

Good idea, horrible execution. You are missing the fact that cookies are read and sent by the client. You can not trust the client with the userid to be logged in as.

as 2: breif, messy, hard to debug, insane event system, evolved into what it is today
as 3: descriptive, easy to debug, easy event system, clearly designed with the full system in mind from the start.

Most people are used to mod 12 clocks, not mod 24 clocks.

If compression makes sense, you shouldn't be using copy and paste to begin with. Just use the Filerefference class and load/save the data as a real file.
If you want people to share their creations online, just make such a system too! If you are a good enough programmer to make something that can be saved in the first place, you will be good enough to be able to written a simple system for letting users upload their creations.
I heard that the NewgroundsAPI has such a system, try asking Tom about it.

Fun fact, framescripts are a part of the class for the timeline they are on. And that class is already in a package, leading to this error.

You have to write the query with special placeholders instead of adding the data in the query string directly. Then you pass this query string to a function that parses it. Then you can bind the placeholders to real values. Once that is done, you can run the query.

Do note that this is slightly more complex. Also, the mysql extension is so old that it doesn't have this already old feature, get a new extension! I recommend the mysqli extension instead.

Not to mention that Flash has a built in compression algorithm implementation for Bytearrays.

I would just use parametrized queries, that way, the data won't even touch the sql command.

Framescripts are a part of the class for the timeline they are placed on.

Your issue is due to not being on the stage when you need to use it. The solution is to wait for the ADDED_TO_STAGE event.

Why are you even using cookies here? The session system is doing a far better job than you are doing with the cookie. For example, it does not let the user tamper with the data.

Indeed, who cares if it is synthetically valid if it doesn't actually work in the end?

To state the issue very clearly:
Outputting a string to the client will not execute it as php code. Yet, that is what you tried to do. Save php code as a file and include that file instead. Using eval also works, but should not be done, due to performance issues.

Things used by the main timeline class is forcibly exported in the first frame. Don't do that.

While it does forget to properly encode the embeded strings in the sql query, it should work.

If root is null, the object is not on the displaylist.

Start it in the constructor for the timeline class. It will only be started once, when the constructor runs.

I personally think that it's stupid to hide layers in order to not get them exported. I just use guide layers instead, since they are never exported, no matter what the settings are.

A* is better for open worlds, since it doesn't waste so much search time most of the time.

flash.geom.Vector3D, exactly what you wanted, and implemented in native code for that extra speed boost.

You are using the wrong operator. You are using the << operator in both cases, but you should only use it in one case.

It's about timing, the os most probably will not have time to send any packets in between the two calls.
Also, there is an algorithm that says that the stream should be idle buffered, Naegels algorithm. It is optional, but defaults to on. I am not sure if flush will bypass that algorithm.

And for the terminating nulls, it is likely due to how strings work in flash or something like that.

I feel like we talked about this like yesterday, it is a bad idea, but possible in as 2, as 3 does not have this bad idea.

The answer is simple:
Because copypaste tutorials is harder when there is more than one file.

TCP is not a packet delivery system, it is a stream delivery system. There is no separate packets. Just a stream of bytes that is added to once in a while.

Your system is flawed from the beginning since it assumes something that outright isn't true. TCP may cause packets to be sent, yes. But all the application sees is a pair of byte streams with no special separation marks.

It is fully legal for multiple "packets" to be joined like this. Or it could hold sending half of one "packet" for 5 sec while letting the rest be sent instantly. Your code has to deal with the fact that it's a bytestream and not packets.

One thing for sure, no standard forbids him from having as he wants it. Each http resource has it's own access rights.

For event sounds, there is the stop type. For streaming sounds, just don't make the layer so long.