Really diggin' the site. Diggin' changing memory. I only have a few aob's under my belt, but they're legit insofar as I know. I like the scouring and demystifying that comes with digging through a SWF file.

That being said, what does one do when one opens a file in one's decompiler of choice and the raw data is unavailable? You know, when the buttons are grayed out and unselectable? I searched Google and the forums here and read every thread containing "aob", but the links in every single one were all dead and the overwhelming majority of the posts dealt with the more entry-level stuff.

So, two parts:

(1) Does anyone have an AS3 opcode cheat sheet? Googled and found none, but I saw it/them mentioned in a thread on here, so surely SOMEone on here has to have one.

(2) How does one circumvent this protection in a more holistic way? Is there a tool that can be used to "unlock" the file before loading it in a decompiler, or does this just come down to patient excavation of root variables?

Thanks in advance

Damn, can't believe I missed the bytecodes. I looked at them earlier I must not have read them carefully enough because it didn't register what they were. Yeah, those are what I was looking for.

I have not tried Yogda before, but from the look of it it's probably what I need, whether I recognize it yet or not. Looks like I have some homework for tomorrow.

The most recent game I ran into this hiccup with was Get Off My Lawn on Kong. Just beat it (go figure) so I don't particularly need the AOBs, but I still have the SWF on my desktop so I'll fiddle with that tomorrow. Thanks, though. That looks to be what I've been missing.
 

Man, this is not my day. I typically use Trillix, but sure enough I just opened the flash in SoThink and the aobs come up just fine. 9_9 Maybe I'm just going bananas. Thanks, everyone.