Shell Shock Live (Can't find damage script)

Also is it possible to open Shell Shock Live in Notepad ++? I tried and it just said stuff about movie frames... idk why. Sorry but one more question. How do you know what to push or what to change in NotePad ++ to see the bytecode. In this tutorial thead video: http://forum.kongregatehack.com/viewtopic.php?f=30&t=303
The person changes a push command to have a 10 at the end and that somehow changes the code to activate the "Slingshot Man". I just want to know how that they knew that "10" would activate "Slingshot Man"?

Since you didn't paste everything, 10 means jump. The 3 bytes that follow the jump specify how many bytes to jump. It has nothing to do with "didDamageWeapon", the code you found probably looks like:

Code: [Select]

didDamageWeapon = ""

So how would I edit the code to equal 100 damage?

*facepalm*

You used Notepad++ because it was easy to use when you had a tool to convert a swf file to p-code and back. This is AS3, flasm isn't usable. So I'm sorry, but you'll have to use your brain.

Let me make this as clear as day: I will not spoon-feed you the answer and I will not answer the same questions over and over. I also don't care for ShellShock live. If you want, learn your way up there or something, but your latest question was already answered.
Tutorials were written for a reason. The reason wasn't so that people can ask the questions covered in them.

I just want to know how that they knew that "10" would activate "Slingshot Man"?

Without looking at the link, I would say they used a combination of observation, intuition, trial and error, and luck.

*facepalm*

You used Notepad++ because it was easy to use when you had a tool to convert a swf file to p-code and back. This is AS3, flasm isn't usable. So I'm sorry, but you'll have to use your brain.

Let me make this as clear as day: I will not spoon-feed you the answer and I will not answer the same questions over and over. I also don't care for ShellShock live. If you want, learn your way up there or something, but your latest question was already answered.
Tutorials were written for a reason. The reason wasn't so that people can ask the questions covered in them.

Ok, I won't post anymore... sorry for being a burden...

You can post. Questions and questioning is good. But before you do, ask yourself these two questions:

• 1. Did I really try? Is there reasoning/logic behind my previous actions?
  2. Was it answered before?
  

I like bytecode because it tingles my logic. You don't see what happens clearly; it's a guessing game. You have to reason with yourself, look at the chain of command, and think how it interacts with each other. It's a nice game to play, better than the game of making sure every single aspect is in clear view.