Bobsomeness
Pure Bobsomeness
- 214
- Posts
- 10
- Years
- Pallet Town
- Seen Sep 9, 2020
Hey there, PC!
I'm Bobsomeness, and I've been ROM hacking for about a year now.
Now I know there are plenty of tutorials out there to help you make a ROM, from planning the game to scripting it to mapping it (and beyond). This tutorial is nothing like that.
Actually, this isn't really much of a tutorial at all. I recommend you read this whether you are just beginning or you are very experienced.
These are just simple laws, kind of like Newton's 3 laws of motion. One difference? ROM hacking has 5 laws, not 3.
Before we begin, let's check out Oxford's definition of law:
a statement of fact, deduced from observation, to the effect that a particular natural or scientific phenomenon always occurs if certain conditions are present.
In English:
a fact that is always true if certain requirements are met.
Basically, what I'm trying to say is that the following laws are 100% true and will happen if you do everything just right (or wrong).
Well, what are you waiting for? In the words of Mario, "Lets a go!"
1. If an individual takes great offense to criticism, then that individual is not fit to be a ROM hacker.
If you're anything like 99% of the ROM hackers on the planet, then criticism is something that you probably receive a lot. Sorry, but it's the truth. If you can't take the criticism as advice, then I advice you to wake up (Hahaha, get it? ....awkward silence). Criticism is meant to help you. Sure, it stings sometimes. But know that this is natural. Have you ever heard of a US president who wasn't disliked by some one before? Exactly.
Now, that being said, as a critic, you shouldn't judge someone too harshly. ROM hackers are humans too, and are prone to making mistakes. Also, when giving criticism, try to give feedback
that helps the hacker. Saying "The map looks rather bland, why don't you add some trees to it?" is infinitely more helpful than "The map looks terrible, my grandma can draw better than you."
2. For every act of plagiarism there is an quadruple and opposite consequence.
Never, EVER, EVER, steal someone else's work without giving credit. I once saw a hack (not gonna give any names here) that used screenshots from another hack. What is the point of that?
It isn't your work, and if you don't have enough progress to show screenshots, then you shouldn't be posting a hack in the first place. Let's see what Christos has to say about plagiarism in the Progressing Hacks forum:
"Please give credit to any items in your hack where it is due, be it sprites, tile sets or scripts. You are bound to the agreements made by the original poster – for instance, if you cannot give
your sprite to others, don't. If your hack is based off another hack's code base and the original poster has asked you not to give the code base to others, don't."
3. The first hack attempted by a ROM hacker will be a piece of ***** terrible.
Many people will tell you that the first hack someone makes is always a piece of trash. I, myself was told that COUNTLESS times during my first few weeks. At first, I didn't believe them.
You probably don't believe me right now. I got this, you might be thinking. Bobsomeness is just going crazy from all the time he's been putting into his hack. Well, I might be. But that doesn't mean I'm not telling you the truth. Your first hack is just a learning experience. Don't give up at hacking just because you fail your first hack.
Of course, if you have any questions, ask me here or shoot me a VM/PM (whichever you prefer). VM/PMing is probably faster than asking here, because I check my messages every time I log in.
You: What? That's it?!?!?!?!? You said there would be five! There's only three! I told you so, Bobsomeness! You're going crazy!
Me: No, not really. I just want to get back to hacking.
You: (facepalm)
More to come...
I'm Bobsomeness, and I've been ROM hacking for about a year now.
Now I know there are plenty of tutorials out there to help you make a ROM, from planning the game to scripting it to mapping it (and beyond). This tutorial is nothing like that.
Actually, this isn't really much of a tutorial at all. I recommend you read this whether you are just beginning or you are very experienced.
These are just simple laws, kind of like Newton's 3 laws of motion. One difference? ROM hacking has 5 laws, not 3.
Before we begin, let's check out Oxford's definition of law:
a statement of fact, deduced from observation, to the effect that a particular natural or scientific phenomenon always occurs if certain conditions are present.
In English:
a fact that is always true if certain requirements are met.
Basically, what I'm trying to say is that the following laws are 100% true and will happen if you do everything just right (or wrong).
Well, what are you waiting for? In the words of Mario, "Lets a go!"
1. If an individual takes great offense to criticism, then that individual is not fit to be a ROM hacker.
If you're anything like 99% of the ROM hackers on the planet, then criticism is something that you probably receive a lot. Sorry, but it's the truth. If you can't take the criticism as advice, then I advice you to wake up (Hahaha, get it? ....awkward silence). Criticism is meant to help you. Sure, it stings sometimes. But know that this is natural. Have you ever heard of a US president who wasn't disliked by some one before? Exactly.
Now, that being said, as a critic, you shouldn't judge someone too harshly. ROM hackers are humans too, and are prone to making mistakes. Also, when giving criticism, try to give feedback
that helps the hacker. Saying "The map looks rather bland, why don't you add some trees to it?" is infinitely more helpful than "The map looks terrible, my grandma can draw better than you."
2. For every act of plagiarism there is an quadruple and opposite consequence.
Never, EVER, EVER, steal someone else's work without giving credit. I once saw a hack (not gonna give any names here) that used screenshots from another hack. What is the point of that?
It isn't your work, and if you don't have enough progress to show screenshots, then you shouldn't be posting a hack in the first place. Let's see what Christos has to say about plagiarism in the Progressing Hacks forum:
"Please give credit to any items in your hack where it is due, be it sprites, tile sets or scripts. You are bound to the agreements made by the original poster – for instance, if you cannot give
your sprite to others, don't. If your hack is based off another hack's code base and the original poster has asked you not to give the code base to others, don't."
3. The first hack attempted by a ROM hacker will be
Many people will tell you that the first hack someone makes is always a piece of trash. I, myself was told that COUNTLESS times during my first few weeks. At first, I didn't believe them.
You probably don't believe me right now. I got this, you might be thinking. Bobsomeness is just going crazy from all the time he's been putting into his hack. Well, I might be. But that doesn't mean I'm not telling you the truth. Your first hack is just a learning experience. Don't give up at hacking just because you fail your first hack.
Of course, if you have any questions, ask me here or shoot me a VM/PM (whichever you prefer). VM/PMing is probably faster than asking here, because I check my messages every time I log in.
You: What? That's it?!?!?!?!? You said there would be five! There's only three! I told you so, Bobsomeness! You're going crazy!
Me: No, not really. I just want to get back to hacking.
You: (facepalm)
More to come...
