Skeetendo

I really appreciate your help.
Well, for the time being then, you could work on maps, texts and define what goes/happens where (also trainer sets would be nice). I'll take care of inserting event data.
I'm working on a map editor which actually I plan to eventually transform in a factotum. I'll post it (or send it to you) when it's at a usable level. I also can send you my old mapping-tool, which too bad isn't really good; can I mail you?

Also, is it ok for you to start thinking up event data definition (number of people in each map, their sprite, etc.)? General storyline and town-map are in the first post, although town map still may vary a bit, if you find it necessary.

I'm not sure but I've heard it's glitchy; also, it's meant to be used on ROMs, while mine will consider the fact that Wood is actually an assembled disassembly (which means it will support side-files, and almost-header-less maps).

Also, NIH.

Last edited by Sawakita (2012-01-04 01:44:56)

This isn't a bad idea, either. And yes, feel free to mail me, though I'd prefer a PM on pkmnhackersonline...

I think 2 minds work better than 1, ya' know Besides, I have  hack of my own (so do you) so I can't even devote all my time into this, but i do wanna help out so Gen 1 hacking doesn't die.

I kinda like IIMarckus's suggestion of making it a community hack. We could give each other ideas and work on it in the IRC channel and whatnot.

I have an idea. Why doesn't Sawakita release the hack in it's current form and then anyone can finish it if they please. Of course, you would think there will be then numerous hacks with the same base but this is untrue since most hacks are never finished. This would be a test to see who can actually finish it fully.

I said that you would think there would be numerous hacks if released openly. However I highly doubt many people would pick up a red hack and finish it.

Anyone willing to contribute here is welcome, thus, thank you.

Same here. A community hack would be my goal, at this point. And also, the IRC is handy when it comes to brainstorming.

When I'm going to release something it would certainly be the source code, rather than the assembled hack.

There are two main reasons:
1. I'd like, or better, I want, that this hack will be made taking advantage of working on a disassembly, rather than on hex editing or anything that is limited by fixed addresses/limits.
2. Releasing the source code would require more effort (even if little) for anyone who wants to put his/her hands on working on it, rather than if I release an assembled ROM.

So, my preference is that this hack will be worked on as a single community, rather than having different people working each one on their own version. And above all, this hack must (maybe a too stong word, but I hope you get what I mean) be developed using the disassembly.

Thanks to anyone who is offering their help, I appreciate it.

1. People are in different timezones all around the board and yet we collaborate a lot of information daily. Even in the IRC channel.
2. Selfish, yes. But this is also the most valid point here.
3. I disagree, An SMWC Production faired rather well. Even though it did have its flaws, SMWCPII looks even better.

I honestly just think you want to try to take the hack all for yourself, judging by the posts, and amount of posts you've made in this thread thus far.

I think this isn’t much of a problem.

The hack will (probably) be kept in a Mercurial repo, so anyone who wants to will be able to fork and create their own version.

Collaborative hacking hasn’t really been done with the right tools. Mercurial is phenomenal for this, and has been a great help in the Pokémon Red disassembly—basically, people can make changes in their own copy, and Mercurial will (almost) automatically merge them together into mine. In fact, I’m trying to determine how to keep Pokémon Wood as a separate branch in the same repository as the Pokémon Red disassembly. That would be pretty cool.

I don’t think that was very nice.

You're right, there's no law to stop you from working on someone else's hack. But there are laws telling you you can't hack someone else's published games. Why would you find it morally wrong to work on someone else's ROM hack, but not on Pokemon itself seeing as that's a bunch of other people's games and it's even protected by law.

I don't think stag was being nasty. I truly do not like community based projects. Plus, mercurial would probably not be the way to go, from what I know it's for mostly programming only. What about all the graphics and maps and features? Perhaps I don't fully understand mercurial.

I had problems using mercurial before too, which would further exclude me from the project. I know I said before I'm sitting this one out, but now you're using mercurial and possibly having the assembly split over several....oh I don't know I'm babbling....

It's Sawakita's hack after all.