Pasted! That's something you'll hear all the time you meet HvH kids. The point is that they all take HvH seriously, like sport or competition for money. They don't really get that simple fact it's only an online game. Here's some personal statistics:
Most of the people accusing others in pasting don't even understand the concept of using public/shared code.
Most of them never wrote a C++ program from scratch.
Most of them don't know the difference between virtual/non-virtual functions and other terms such as abstract class, or even how to simply dereference the pointer and perform other basic language operations.
Most of them would not be able to write a program on a piece of paper without using internet/hints and get it compiled from the first try.
Now, if we get back to the term
pasting, I would want to clear some things out. The reality is that there is no much public information on how to make cheats, except for
bases (completely compile-able projects without basic feature set, but only some kind of project skeleton). There're also lots of public
pastes containing simple aim bots, trigger bots and ESP. Now, how it usually happens with something I call
bad pasting: Some guy thinks he's a good coder and decides to write a cheat. He's trying his best to study, but fails due to lack of public knowledge, and apparently he's unable to reverse binaries and handle SSDK2013 due to large amount of data in it. Such person, soon or later, comes to a really simple conclusion:
"How about I paste somebody's base, add some half-working features, rename it to %insertnewpastenamehere% and call it mine! No one will ever understand I pasted it, muhahahaha!". And he pastes the project, fills it with publicly available features and releases it by uploading to some unknowncheats. Then he receives a bunch of complains about
cheat causing BSODs, but instead of fixing it (how badly should you write the cheat so it causes BSOD?) he just starts to shit-talk everybody who criticize the cheat and being objectively correct. After getting large amount of negative feedback, this person will say something like
"Me > You! If you crash, lag, miss or BSOD with my cheat - you're looser/you suck/%insertgenerickidresponcehere%!". At this moment of time such person will go sexual and believe in his/her own lie of his/her cheat being NOT bad, but instead all users experiencing problems being bad. Nice logic, huh? Continuing to do so will result in inferiority complex, inflated self-esteem and huge desire of showing off by shit-talking other people. The irony is that no matter how hard that person will try - he/she will never get better, since such people can't study on their own mistakes. Another fact is that if you ignore such people in your life - they will vanish, because they feed on attention and surrounding hype.
Now let's look at another example of
good pasting: You want to make a cheat, but never done this kind of programming and instead of showing off, you have the aim to improve your knowledge base and you really interested in researching this yourself. You can even paste the entire project, compile, rename it, do whatever you want, but you will never act like you created that. You will study on this project by changing some lines of code and checking how that affected the functionality. After getting some strong knowledge on how things are done and how they work, you start creating your own project (or even continue changing the original one) rewriting feature-by-feature by yourself. You may fail large amount of times during development, get a bunch of crashes and performance issues, but the point is that sweet satisfaction, when you finally made something completely yourself.
From this point I will talk for myself. I'm kind of perfectionist person, and I never use something I don't completely understand. Even if I take some functions from SSDK, I always analyze them, re-factor them, fix code style/layout, add Hungarian notation, and only then I can technically call it mine. Though if somebody asks me if I pasted, I can clearly answer: yes, I pasted lots of SSDK functions, algorithms, etc... The reason for that is that firstly, I use SSDK since 2009, and I'm pretty familiar with its code layout, functionality and so on, and secondly, why inventing the bicycle? If somebody asks me
"Did you paste your cheat?", I answer
"No.", if they ask me
"Did you paste projectile prediction?", I answer
"Hell no.", if they ask me if I pasted at all, I answer
"Yes, I pasted encryption algorithms, entity management system, entity SDK, all the SSDK headers and some *.cpp files from game/client folder.". I don't see anything bad in pasting something you completely understand. If there would be someone asking me to explain how this and that thing works - I would immediately answer in details. So, as you can see from what I'm talking - I don't think pasting is bad, I think it's bad in case of getting easy profit without any understanding on how it works.
P.S.: The thing I don't really get is why random people who can't even C++ keeps on screaming
"Your cheat is pasted!". They didn't even see your cheat in action, never used it nor seen the sources, so why windbag around if you can't even prove your POV? I guess the answer is in their attempt to self-assert by humiliating others due to large amount of complexes. I can only wish such people to grow up faster.