Are you spending hours and hours on simple scripts? Are people unimpressed with your coding skills? Then look no further, this is the guide for you.
In this brief guide I will list and explain the basics of testing, coding and finishing your mIRC scripts.
- Don't rush your coding
- Don't cramp your coding
- Never steal code from someone else and call it your own
- Always think outside the box
- Use every resource at your disposal to complete a script
- Watch out for dumb errors
- Test with safety in mind
- Quit copying Hollow
- Never give up!
Don't rush your codingIf you have a deadline be calm and code to the best of your abilities. Rushing through complex or even simple code will usually make you prone to more mistakes, which means it will take more time in the long run.
Don't cramp your codingIt makes your coding harder to correct if you make mistakes or add on to it. Sure it looks complex, but real coders know that smooth, flowing, working code is better.
Never steal code from someone else and call it your ownIt doesn't matter how many cool scripts you make, or claim to make. What really matters is if you have the skill or not. If you do not have the skill, acknowledge it and pick it up or simply move on. Stealing someone's hard work with little effort is not how real coders work. Give credit where it is due.
Always think outside the boxThis is easier than it sounds. Some people can do it, some can't. It really helps when you are coding something that has not been coded before.
Use every resource at your disposal to complete a scriptThat's great if you can code something on your own with little help. But it also fine to use scripting resources like hawkee to get advice on how to best complete a script. It saves you time, and you will probably have the code you want. You can also ask on here.
Watch out for dumb errorsI remember when I was writing a script to use sockets in a way I had not yet explored, I couldn't get it to work. I tried over and over and over but it still wouldn't work. I sent the code to a friend who implemented it in a different coding language and it worked! I was frustrated beyond belief, then when I checked my brackets I realized I had one off. The code has worked fine since.
Basically, I am saying that you should always look out for those small bite you in the a** errors that we often get. Remember to cross your t's and dot your i's.
Test with safety in mindIf you're testing a script that k-lines someone or blacklists them or anything like that, have it echo instead of send the command to the server. If it goes wrong, you won't have to explain why every user got killed or banned from the server. Trust me, I know from experience in this area.
Quit copying HollowWe all know Keith did very well in coding Hollow, and that it was well reviewed. Honestly though, I can't tell you how many times I've seen scripts that look like Hollow clones except without good coding. Keith did well with Hollow only because he improved and did something original, and did it well. If you want the praise Keith got, make something new and original. Copying him will not get you the same praise and it will likely draw criticism.
Sorry Keith.
Never give up!One of the most essential rules in life is also one of the most essential rules in coding. No matter how hard your code might seem, no matter how impossible the idea seems, never give up. Never. You will learn from your mistakes in the end, and learn from your successes. That is why never giving up is mandatory to every coder.
---
Well, I hope this guide helped. Let me know what you thought about it by posting a comment below.
