How do you plan your hacks?

I've never make my own complete hack (each one less than 10%).
Now I just started a new real project with many thoughts with my firends.
But when really sarted,I found myself hard to plan the hack.
I mean,I enlarged the rom,but don't know which part should or better to do what.
Which part should be maps?
Which part should be scripts?
And which part should be new OW or even new uncompressed pic?(In JPAN's engine)

How do you plan your hacks?Give me some advice...

I start off planning my story, then I separate it into chapters. Then, I complete everything in a chapter, starting with maps, sprites, then scripts. Rinse, wash, repeat till I get what I want for my first beta.

my way is ... to ...
think it make it

This time I'm basing it on a short story I wrote. It's easier for me that way. Then I plan any geographical changes, and usually difficulty of gameplay comes last.

-v-Looks most hackers start with storys,I think I should try...

I have a notebook I carry in my schoolbag. I spend most of my day in school, so anytime I've a free class or something I brainstorm. I've written the story (yeah, novel-style xD) and it's how I plan out my new trainers, towns, etc. It's pretty efficient.

giradialkia said:

I have a notebook I carry in my schoolbag. I spend most of my day in school, so anytime I've a free class or something I brainstorm. I've written the story (yeah, novel-style xD) and it's how I plan out my new trainers, towns, etc. It's pretty efficient.

Click to expand...

I do that too!!Haha,sometimes,my teacher was totally fascinated about my novel~

It's not simple, really. First of all, you must think of a general idea of the storyline. The legendary, what the legendary has to do with the hack, some of the basic characters. Then, to make it easier think of the basic plot, you could make the region.
And then the Plot, the Maps, the Scripts, misc. etc.

My way is:

1. Plot out the basic storyline
2. Configure the characters - without the clothing, etc
3. Think of the places that are about to be visited
4. Pokemon and items involved
5. the features
6. sprites
7. tiles and insertion
8. scripts
9. beta test
10. a version release

That's about it. It's the way I like to plan things. My hack is currently at the 7th stage, thanks to everyone that helps me (and people who help in hacks in general. They play a big role as to how each hack develops).

1. Think of a Story
2. Map the towns for the first release
3. Script the towns for the first release
4. Release a alpha/beta!

When I tried to make a hack I started with a very detailed story telling exactly what would happen in the hack. After that I broke it up into sections that would be released as betas upon completion. For each section I then wrote out what needed to be done first and then followed that. To put it simply I made a story then an outline.

Hmm, easy question answered for me. Well I've only ever started one hack, but its pretty far.

First I think of a great unique story thats never been thought up before.

Next I ask myself "Would I buy this game if nintendo released it?" (yes I would :P)

Next I make a few test maps using imagination and script as I go along.

All the maps after that are drawn on paper using simple things such as v's for trees and squares for building.

Start off with EVERY aspect down on paper, the characters (really important in story telling), the environment (Towns/cities and ect) goals and everything. Even with all that preparation, it never goes as planned 100%

I haven't posted ny hack, but I just make whatever occurs to me whaile on a project. That way I also get the fun of being suprised by the storyline.lol

I start of by writing a complete game script of my hack.
Yes, this means that I end up writing a short novel, lol.

Next, I'll end up taking my ROM, and inserting any and all graphics, that means that I wont be inserting anything else throughout the game, unless it is something that I didn't think of during the creation of the game script.

Now at this point I end up mapping... I'd end up mapping half of the game, I don't like small betas...

From there I move onto scripting, keeping a list of any flags or variables I use in the game. So I don't ever overwrite anything, or use a flag more than once (Unless needed)
Finally, I beta test myself, and release beta 1.

(Though I can't do any of this except writing the script, since the good computer of the house has been sent off to be repaired... (My sister + computers = mobo problems that can't be fixed due to her ruining the diagnostics...))

Mine just sort of came to me
i have no idea how i will go about it
i have the start of the story sorted out
but have no idea for town, city, character names
or anything else like that - but i will get there :)

when i start thinking of a hack i usually write it down on paper
and then the next day i forget about it xD and so i never finish one xD

For Hacks:
1. Story
2. Basic Logistics (Map, Pokemon, Items, Attacks fixable by tools)
3. Changed/Added Features (usually involves scripting or ASM)
4. Spriting (I reverse the order because I have no ability in art.)

For game remakes, the same applies, but steps 1 and 4 are optional.