D
Deleted User
Crowd Member
I'm just going to make a big list of things I wish I knew before i got into hacking/Modding No mercy. if any other veterans wanna jump in with their own advice, do so and I'll add it to the first post.
This is being done because there are mistakes and behaviors that I see over and over that are sometimes cringe worthy. People think it is easier than it is, or they think it's some kind of black magic that only the elite can perform. It's neither.
So here we go.
<big><big>1: Do NOT announce a save until you KNOW for a fact you will be able to handle every part of it. It's a LOT more than just wrestler texture mods. In fact, many times, the wrestler textures are the EASIEST part.
Don't believe me? Go ahead and take a good look at all the "elite" texture modders that don't know squat about hacking. I can't tell you how many interesting save ideas and good work I've seen come to a crashing halt because the skills needed to complete the save were not assigned for and covered.
The biggest point with #1 is this: COVER YOUR BASES. MAKE SURE YOU HAVE A FOUNDATION THAT WILL BE ABLE TO COMPLETE THE PROJECT.
2: Do NOT get yourself buried in wrestler mods. This is one of the biggest mistakes people make. They make all their textures first, and then when it comes time to make codes for the movesets and movehacks, they are overwhelmed by the sheer amount of tedious work it takes to program all those movesets.
When I made Showdown, I had a VERY simple rule: As soon as I finish a wrestler texture mod, I would halt all texture work until their moveset was written and completed.
This may not seem like that big of a deal, but you have to trust me, this is easily the BIGGEST mistake I see many people make. I can't count how many good looking projects are dead in their tracks because the wrestlers are not playable, and they have a mountain of code that will never be written.
ONE AT A TIME. ONE DAMN WRESTLER AT A TIME WILL SAVE YOU THE HEADACHE OF BORING BACKTRACKING LATER.
3
o NOT assume the community will spoon feed you tech support or will finish the parts you don't know how to.
Sure, often times you will see a lot of us help each other out with their projects, but usually that's because we've know each other for a long time, and mutually help each other with our stuff.
There's a difference between helping EACH OTHER and assuming others will help YOU. It's a two-way street.
4: LEARN THE BASICS OF HACKING.
If you can rock photoshop, then you have no excuse for not being able to figure out hacking. Sure, there is a period in the beginning where it seems daunting, but hacking is extremely simple once you put forth a REAL effort to experiment and learn.
There is nothing more maddening than seeing someone who is capable of learning the basics of hacking who refuses to because they don't understand it completely as soon as they start. And then they ask others for help simply because they don't want to be bothered with learning a new skill.
Were you a master of photoshop when you started? Of course not. Same with hacking. It isn't magic, it's simply editing numbers. Numbers which have ALREADY BEEN TRANSLATED FOR YOU.
This is easily my biggest pet peeve, we have an online encyclopedia of hacking tutorials and advise but because people get scared of some numbers they refuse to even TRY hacking.
Guess what? HACKING IS EASIER THAN TEXTURE MODDING. THE REASON HACKERS GET A PISSY ATTITUDE WITH REQUESTS AND QUESTIONS IS BECAUSE WE KNOW FOR A FACT YOU HAVEN'T MADE A GENUINE EFFORT TO LEARN IT YOURSELF!
No, really, hacking is fucking EASY. It's swapping numbers. So many of you don't even TRY, even when asked to. There are members who have been in the No Mercy scene for YEARS who still are too lazy to try, and it seriously pisses me off when I see these long time members STILL making requests for basic shit.
GET OUT OF YOUR COMFORT ZONE AND LEARN TO DO BASIC HACKING.
4: Do NOT set a release date.
Why?
Because it NEVER works out.
Kay? Kay. This is self explanatory.
5: Don't get frustrated if the community seems less than excited about your project.
The No Mercy scene is rotten with unfinished saves. We're used to seeing a project announced, have good steam for a couple months, and then end up dead in the water.
We won't get excited until it looks like there's a genuine chance it will be released.
6: Understand, this will take a LONG time.
Even if using templates and other people's codes, you have a LOT of work ahead of you. Sometimes even YEARS of work. If you are not willing to commit that much time and effort, then don't.
7: Compilation saves are cool, but they will never be held in the same regard as a genuine save.
Why? Because the quality is hardly ever consistent. Comp saves are neat, but in the end, are usually bug-riddled messes.
8: LEARN TO USE HACKING TOOLS.
This is kind of an extra point when it comes to learning the basics of hacking. If you can't figure out how to work WldFb's moveset tool.... then you have no place making a save. period.
9: STUDY THE TIME PERIOD OF THE SAVE YOU ARE MAKING.
Keep it as accurate as possible. An accurate moveset will always be noticed, but a quickly made "good enough" moveset will always suck.
Know what you have to make ahead of time.
10: Do NOT announce a save, have ZERO work to show for it, and then proceed to ask others to join your team! Get a portfolio of previews together to show others you will actually be putting in work.
11: DON'T ASK ME FOR HELP.
I only help Gen Hex, WWF Legends, and Wrestling Modders Inc, anymore. If you are a noob and want my help, don't flood my inbox with stupid questions, create a body of work that shows you are worth my, or ANY veteran's time.
</big>
If anyone else has tips, put em in this thread and I will add them to the first post.
This is being done because there are mistakes and behaviors that I see over and over that are sometimes cringe worthy. People think it is easier than it is, or they think it's some kind of black magic that only the elite can perform. It's neither.
So here we go.
<big><big>1: Do NOT announce a save until you KNOW for a fact you will be able to handle every part of it. It's a LOT more than just wrestler texture mods. In fact, many times, the wrestler textures are the EASIEST part.
Don't believe me? Go ahead and take a good look at all the "elite" texture modders that don't know squat about hacking. I can't tell you how many interesting save ideas and good work I've seen come to a crashing halt because the skills needed to complete the save were not assigned for and covered.
The biggest point with #1 is this: COVER YOUR BASES. MAKE SURE YOU HAVE A FOUNDATION THAT WILL BE ABLE TO COMPLETE THE PROJECT.
2: Do NOT get yourself buried in wrestler mods. This is one of the biggest mistakes people make. They make all their textures first, and then when it comes time to make codes for the movesets and movehacks, they are overwhelmed by the sheer amount of tedious work it takes to program all those movesets.
When I made Showdown, I had a VERY simple rule: As soon as I finish a wrestler texture mod, I would halt all texture work until their moveset was written and completed.
This may not seem like that big of a deal, but you have to trust me, this is easily the BIGGEST mistake I see many people make. I can't count how many good looking projects are dead in their tracks because the wrestlers are not playable, and they have a mountain of code that will never be written.
ONE AT A TIME. ONE DAMN WRESTLER AT A TIME WILL SAVE YOU THE HEADACHE OF BORING BACKTRACKING LATER.
3
Sure, often times you will see a lot of us help each other out with their projects, but usually that's because we've know each other for a long time, and mutually help each other with our stuff.
There's a difference between helping EACH OTHER and assuming others will help YOU. It's a two-way street.
4: LEARN THE BASICS OF HACKING.
If you can rock photoshop, then you have no excuse for not being able to figure out hacking. Sure, there is a period in the beginning where it seems daunting, but hacking is extremely simple once you put forth a REAL effort to experiment and learn.
There is nothing more maddening than seeing someone who is capable of learning the basics of hacking who refuses to because they don't understand it completely as soon as they start. And then they ask others for help simply because they don't want to be bothered with learning a new skill.
Were you a master of photoshop when you started? Of course not. Same with hacking. It isn't magic, it's simply editing numbers. Numbers which have ALREADY BEEN TRANSLATED FOR YOU.
This is easily my biggest pet peeve, we have an online encyclopedia of hacking tutorials and advise but because people get scared of some numbers they refuse to even TRY hacking.
Guess what? HACKING IS EASIER THAN TEXTURE MODDING. THE REASON HACKERS GET A PISSY ATTITUDE WITH REQUESTS AND QUESTIONS IS BECAUSE WE KNOW FOR A FACT YOU HAVEN'T MADE A GENUINE EFFORT TO LEARN IT YOURSELF!
No, really, hacking is fucking EASY. It's swapping numbers. So many of you don't even TRY, even when asked to. There are members who have been in the No Mercy scene for YEARS who still are too lazy to try, and it seriously pisses me off when I see these long time members STILL making requests for basic shit.
GET OUT OF YOUR COMFORT ZONE AND LEARN TO DO BASIC HACKING.
4: Do NOT set a release date.
Why?
Because it NEVER works out.
Kay? Kay. This is self explanatory.
5: Don't get frustrated if the community seems less than excited about your project.
The No Mercy scene is rotten with unfinished saves. We're used to seeing a project announced, have good steam for a couple months, and then end up dead in the water.
We won't get excited until it looks like there's a genuine chance it will be released.
6: Understand, this will take a LONG time.
Even if using templates and other people's codes, you have a LOT of work ahead of you. Sometimes even YEARS of work. If you are not willing to commit that much time and effort, then don't.
7: Compilation saves are cool, but they will never be held in the same regard as a genuine save.
Why? Because the quality is hardly ever consistent. Comp saves are neat, but in the end, are usually bug-riddled messes.
8: LEARN TO USE HACKING TOOLS.
This is kind of an extra point when it comes to learning the basics of hacking. If you can't figure out how to work WldFb's moveset tool.... then you have no place making a save. period.
9: STUDY THE TIME PERIOD OF THE SAVE YOU ARE MAKING.
Keep it as accurate as possible. An accurate moveset will always be noticed, but a quickly made "good enough" moveset will always suck.
Know what you have to make ahead of time.
10: Do NOT announce a save, have ZERO work to show for it, and then proceed to ask others to join your team! Get a portfolio of previews together to show others you will actually be putting in work.
11: DON'T ASK ME FOR HELP.
I only help Gen Hex, WWF Legends, and Wrestling Modders Inc, anymore. If you are a noob and want my help, don't flood my inbox with stupid questions, create a body of work that shows you are worth my, or ANY veteran's time.
</big>
If anyone else has tips, put em in this thread and I will add them to the first post.