Home
Original Guide from 'RalaKimus':
Ralakimus wrote:EDIT 1: I decided to revise this to make it better. Thanks to Lips2k8 and TheInvisibleSun for pointing things out.
EDIT 2: I decided to add how to properly make a hack and not just how NOT to make one.
EDIT 3: I revised it one more bit and added some new stuff.
NOTE: THIS IS FOR ANYONE NEW TO HACKING A SONIC GAME
Hello! I will teach the things to NOT do when hacking a Sonic game.
#1: Palette Hacks and Noob Palettes
It's OK to start out just editing the palettes, but DO NOT RELEASE the hack if it's only just a palette hack. And PLEASE, do NOT make the palettes have random colors and such, they can be really irritating to see. Don't try to make the player's eyes bleed with unfitting colors that just irritate us.
#2: Messing up on level design and object placement
It's OK to have Sonic hacks that just have level design changes as long it is done well, like Sonic 1 Alt, which is a hack with only level design changes and is well done. If you don't know how to make a proper level yet, follow this guide to changing the level design. If you intend to make a hard and challenging game, it's not a good idea to just spam badniks everywhere and call it "hard and challenging". Make sure, the object placement is at proper places and not spammed, glitched up or even blocking the way to victory.
#3: Just changing art and text and NOTHING ELSE
Similar to palette hacking. It's OK to start off with this, but don't release it if it's just an art hack.
#4: Stealing code from others
This is BAD, no kidding. First of all, when stealing code from another, you can get into a lot of trouble with the original coder.
Example: Stealing Selbi's code and calling it yours.
This is a bad idea. Plus, we don't want more of the code to spread. Create your own code and original moves and what not.
In fact, you can be banned from here if you do so.
#5: Going onto tutorials and such and just copying and pasting the code
You're NOT learning anything. You'll need to learn from the tutorials, or else you won't have any idea what you're doing. Plus, if it's code for a homing attack or something, then it's best to keep it off your hack. Code on tutorials is probably better for learning the basics of the code and how to make it work.
#6: Editing the ROM in Hex to Add New Badniks, Objects, Moves, etc.
I don't recommend using hex editing as a method of hacking Sonic games if you are just starting out. I recommend that you start out with a disassembly.
That means, you can't use Sonik Sprite or Esrael Sonic Editor II in disassemblies.
Using a disassembly allows you to get a better understanding how the game is made and it's much easier to edit and you don't get lost as much as using hex to add new stuff.
If you don't know how to use assembly, follow this guide to get a basic grip on it.
There ARE programs for disassemblies, like SonED2 (Level editing), SonLVL (Alternate to SonED 2), SonMapEd (Art, Palettes and Mappings), etc.
#7, Rushing on the Hack
You're not in a race. Take your time with your hack. Doing so will result in a sloppy hack that isn't fun to play.
#8, Telling other Hackers to "do the work for you"
It's YOUR hack, YOU do the work. This forum isn't here for telling you the code for the Ultimate Super Move for Sonic or whatever for you to copy and paste. This is here to answer questions you have if you're stuck on a certain part of your hack.
If you are stuck on something in your hack, first try to figure out the problem yourself. If there isn't any luck, look to see if your question has been answered, that way the forums aren't flooded with the same exact question. If there isn't any answer anywhere, don't hesitate to ask the question and some pro hackers can probably swing by and answer your question.
#9, Using code from ASMtoSegaGenesis/OuricoDoido
That site is frowned upon on here. That site has users like OuricoDoido that share and steal code that programmers like Selbi or MarkeyJester programmed. Like what I said above, stealing code is bad and you can be banned. So, do NOT follow guides on that site or from that specific user or maybe some other users that do.
Conclusion for How NOT to Make a Hack
Note: Things such as palette, art and text editing is great for starting out and learning how it works. If it's just a text edit, or a palette and art hack with NOTHING else added, it's best not to release it, but it can be used for personal reference to help yourself when needed.
Before I completely conclude this here, I just want to say, there was a user named Green Snake who made a hack. His hack was infamous for being one of the worst hacks the Sonic Hacking Community has ever played, AKA The hack of shame. People claimed that it had stolen code from Megamix, it had slightly butchered collision, and other stuff that made this particular hack the hack of shame. So therefore, do NOT follow in his footsteps, don't make another hack of shame.
Well now here you have it, a guide for how NOT to make a Sonic hack. If you have any questions, feel free to reply.
How to ACTUALLY Get Started with a Hack
I will teach you how to get started with a disassembly! What you newbies can do to get started with hacking a Sonic game.
#1, Following these guide here and using these programs
Guides:
1a. Guide for SonMapEd (How to make mappings, palettes and art for disassemblies)
Programs: SonMapEd
1b. SpritePlotter Guide (Alternative to SonMapEd)
Programs: SpritePlotter
2a. Guide on SonED2 (For SonLVL, Use the help files.)
2b. Sonic Retro Thread on Level Design (How to properly make a level)
Programs: SonED2, SonLVL
3. 68k Motorola Assembly Guide on Sonic Retro (The basics of the assembly to use)
Programs: Any Basic Text Editor (I recommend that you get one that supports highlighting)
4a. nineko's MIDI to XM to SMPS Guide (Sonic 1 Only, Making Custom Music, Easy)
Programs are listed in the guide
4b. MarkeyJester's SMPS Guide (Sonic 1 Only, Making Custom Music, Harder than the above)
Programs: Any Hex Editor
I recommend that you start with the 1st on the list to get started with working with disassemblies, then you can continue on down the list from Art and Level editing to Actual ASM editing and Music editing.
#2, You can look at examples to get a better understanding of something, but not for copying and pasting/stealing
I say that it's OK to look at examples and tutorials to help you learn how ASM works.
It's still not OK for copying and pasting/stealing.
#3, If you are unable to do something, just ask
If you have a question, try to experiment first to see if you can solve it yourself. If you can't try to find an answer for yourself, then look it up and see if it was a previous question that has been answered. You can look through the Q&A forums or this thread. If there is no answer for your question, don't hesitate to ask us! We are here to help!
#4, You don't have to do this alone...
It's OK to have contributors help and support your project. As long as you give credit, it's alright.
#5, Here are some tips and tricks you can use:
- Always make backups. You'll never know what may go horribly wrong with your hack...
- Don't overload the ROM, it causes slowdown,and it could possibly overwrite some stuff that may been very important!
- More are on this thread.
#6, Try to keep it as original as possible
That means don't try to clone Sonic Megamix, Sonic ERaZor or whatever hack is out there. Make up your own stuff and you'll most likely get praised for your original ideas!
#7, Take your time and put a lot of effort into it
There isn't any deadlines or races for when making a hack. Take your time to let every part of your creativity flow from your mind to your hack. Also, don't be lazy. Put a lot of effort into it to make it work right and well. We don't want rushed sloppy things in hacks, we want well thought out and decent things in hacks.
Ultimate Conclusion
I hope this helps you for when you start to make your first hack. Try to follow these tips and you'll probably produce a decent hack that people will have fun playing.
Thank you for taking the time for reading this.
