This page will go over some of the advanced techniques specific to Flash curation. It should explain:
- Using the universal crossdomain.xml (and what a crossdomain.xml does)
- Using the debug projector, checking if a game needs browser (ExternalInterface errors)
- Using flashvars and embed codes
- Finding the SWF version with JPEXS and using old Flash projector versions
- Using Flash APIs such as the Miniclip Gameloader
- Finding and adding SWZs
If you're able to help create this page, please get started!
Fixing the Embed Code
Embedding a Flash game in an HTML can occasionally cause problems with the game that did not previously exist. If a 3D game you are curating suddenly stops working when embedded in an HTML, or strange visual glitches appear in the game, you likely need to fix your embed code. Fortunately, the fix is very simple.
When you are embedding a Flash game in an HTML file, you should nearly always use the
direct wmode parameter. For example, let's say you noticed visual glitches in a game with the following embed code. Changing
direct would fix the problem.
<embed src="someGame.swf" width="900" height="450" wmode="transparent"> </embed>
Finally, if you are curating a 3D Flash game using an HTML embed, you should always use the
direct wmode, because Stage3D (Flash's 3D engine) only works reliably in this mode. For example, if you had a 3D Flash game with this embed code:
<embed src="someGame.swf" width="800" height="600"> </embed>
You would change it to something like this:
<embed src="someGame.swf" width="800" height="600" wmode="direct"> </embed>