( I Actually dont use the combat system )
"I Just read the codes... Play the example and it gave me an idea for my Combat System that i was really needing."
"Why didn't I use this combat system? I read through it, and it was not going to fit in my game... but it gave me an idea: I adapted the code for my game."
So Thanks a lot xD
Forgive the corrections... force of habit
(seriously, nothing against you, I assume you don't speak English as a first language, so no worries. Chances are I'd do far worse trying to speak your native tongue haha).
So, I haven't tested this yet, as I'm currently at school, using university computers, so I can't exactly just download Game Maker and run these things on it, but I like to take spare time between classes and find decent tutorials and examples to look over for when I get home, then email the links to myself.
Anyway, the actual reason I'm replying to this is because this is -exactly- what I feel people should be doing with these examples. I have a fairly thorough background in programming, and I've found that too many beginners to programming flock to things like this (where an entire, highly specific system has been completely laid out for them) in stead of learning to make the system for themselves.
This is not so much a problem when talking about experienced programmers, as it is a -colossal- time saver (this is generally how "game engines" are used, but with a bit more intensive modification, generally), but when teaching/learning programming, taking such shortcuts is pretty counterproductive, since the understanding of how these things actually work is what tells you when to use them, and how they might need to be modified.
The process you described is known as "reverse engineering." This basically means starting with an end product and learning how it works and how it was constructed by taking it apart and analyzing the individual parts with respect to the object as a whole.
Especially when it comes to programming, reverse engineering rather than "copy-pasting" is usually a much better idea, since certain aspects of the example code may be inefficient overall, or even only inefficient given how you needed to use it, which would require editing, and the learning process is much more in-depth than just taking code, making you a better programmer!
Overall: I'm glad to see at least -someone- on here doesn't just use these as crutches in stead of learning from them, and growing as a programmer. :D