Servers Online
Working on upcoming update...; Huge refactoring is in progress;
To paste or not to paste?

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:
1) Most of the people accusing others in pasting don't even understand the concept of using public/shared code.
2) Most of them never wrote a C++ program from scratch.
3) 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.
4) 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 his 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 "You pasted!"/"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.


License Agreement / Terms Of Service


THIS DOCUMENT DESCRIBES A CONTRACT BETWEEN YOU ("THE CUSTOMER") AND NULL CORE LIMITED. YOU MUST READ IT BEFORE DOWNLOADING, PURCHASING OR USING NULL CORE SOFTWARE. BY DOWNLOADING AND/OR USING THE NULL CORE SOFTWARE YOU ACCEPT THIS LICENSE. IF YOU DO NOT AGREE TO THE TERMS OF THIS LICENSE YOU ARE NOT PERMITTED TO DOWNLOAD AND/OR USE THE NULL CORE SOFTWARE.


Common terms used in this document:

  • NCL - Null Core Limited (service provider)
  • NCS - Null Core Software (the software product)

  • DISCLAIMER OF WARRANTIES. NCS AND ANY OTHER MATERIAL IS PROVIDED "AS IS". NCL AND ITS SUPPLIERS DISCLAIM ALL WARRANTIES WITH RESPECT TO NCS, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, IMPLIED WARRANTIES OF MERCHANTABILITY, NON-INFRINGEMENT, TITLE AND FITNESS FOR A PARTICULAR PURPOSE.


    LIMITATION OF LIABILITY. IN NO EVENT SHALL NCL OR ITS SUPPLIERS BE LIABLE FOR ANY SPECIAL, INCIDENTAL, INDIRECT, OR CONSEQUENTIAL DAMAGES WHATSOEVER (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GAME ITEMS OR ANY OTHER LOSS TO ANY ONLINE GAMING ACCOUNTS) ARISING OUT OF THE USE OF OR INABILITY TO USE NCS OR IT'S SERVICES, EVEN IF NCL HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.


    1) PURCHASING

    1. All payments are non-refundable, unauthorized chargebacks will not be accepted, except for the case if the customer is unable to use the product due to hardware identification issues and/or issues related to software compatibility.
    2. Once the customer has purchased the software subscription they may use it until the expiration date if no violations has been made.
    3. NCL will not recover subscription time lost due to maintenance and hardware/software failure related to NCS backend and/or NCL itself.
    4. If the customer has troubles using the automated payment form, they are required to wait a few days to make sure the issue is not related to PayPal maintenance
    5. NCL accepts payments only through official Null Core Project website, any other unlisted payment methods are not accepted


    2) LIABILITY
    NCL is not responsible for any losses the customer may sustain as a result of a Valve Anti-Cheat ban while using NCS or any other in-game bans, including, but not limited to: untrusts, gameserver bans, cooldowns, etc... It is always advisable to be careful and use the NCS on an alternative account. Failure to do so, regardless of how much they may have lost, is the responsibility of the customer. NCL/NCS takes no responsibility for the customer's online gaming accounts as a result of using this website or any software, or data contained within. NCL/NCS may track information related to NCL/NCS usage for statistics. However, the customer's private information is never exposed. NCL/NCS keep the right of terminating/suspending any account without refunding, if fraud and/or illegal activity is detected, including, but not limited to: hacking, scamming, cracking, spoofing and debugging activities.


    3) USAGE

      The customer is permitted to:
    1. Download purchased executable to their own PC.
    2. Share their executable with their friends for demonstrative purposes only. The customer takes full responsibility for every action of the person they share their executable with.
    3. Infinitely reset their HWID via website in the event they upgrade their computer.
    4. Store the NCS executable on their computer or removable media for their own personal use.
    5. Make promotional media related to Null Core.

    6. The customer is NOT permitted to:
    7. Distribute their executable to any third party, except for the case described in paragraph 3B.
    8. Modify their executable in any way.
    9. Spoof the protocol/network traffic used by executables and/or injected game.
    10. Reverse engineer their executable and/or injected game in any way.
    11. Run their loader in sandboxes and/or virtual machines.
    12. Perform any malicious or illegal activities against NCL including, but not limited to: DoS/DDoS attacks, network traffic spoof, etc...
    13. Make media content designed for misinforming potential clients about our product quality.
    14. Perform unauthorized chargebacks.
    15. Resell their account.
    16. Impersonate other members, moderators, or developers of NCL in any way.
    17. Fabricate any kind of data/evidence to substitute other Null Core users.


    4) SUPPORT
    Once the customer purchases the software subscription for any of listed games the customer gets free support and future updates till the expiration date of the NCS license. The customer might want to contact NCL team to report a bug or get help. The customer must make sure they follow these rules:

    1. The customer must contact the team ONLY via specialized website feedback form.
    2. The customer must describe their issue as detailed as possible, attaching links to screenshots and videos, if possible.

    However, NCL might reject the customer's help/support request if the customer:
    1. Doesn't provide enough information about the issue.
    2. Complains about something that can only happen in a single server.
    3. Complains about something that isn't actually a bug.
    4. Complains about something that the customer can't understand/get used to.
    5. Uses external software that is not supported by NCS.
    6. Abuses any of the system faults/exploits.
    7. Asks questions unrelated to issues and/or bugs and/or doesn't consist of technical basis, but theoretical and/or indirect doubts.
    8. Fails to comply with professional ethics.
    9. Fails to fill the feedback form properly.
    10. Tries to spam using the feedback form.
    11. Addresses a non-issue request.

    The customer's request and/or an ability to open tickets might be temporarily or permanently suspended in case they don't follow the rules. Any requests to contact NCL members via 'NCL Team' page and report issues directly will be blocked.


    6) EXTERNAL RESOURCES
    NCL has not reviewed all of the websites linked to its website and is not responsible for the contents of any such linked website. The inclusion of any link does not imply endorsement by NCL. Use of any such linked website is at the user's own risk.


    Violation of these rules will result in the customer's account being temporarily suspended or completely terminated, discontinuation of any further services from NCL and possible legal action if any local or remote laws are violated in the process.


    This license might change in the future without warning.