Nightcrawler
Guest
|
 |
« on: December 13, 2006, 09:34:27 am » |
|
Since community projects and 'shitty' ideas have been the latest craze around here lately, I thought I'd throw another out there. I won't be around to take part in much discussion on this since I leave on Friday, but I thought I'd get it out before I forgot about it and let everybody else hash it out. You know the old song and dance. Plenty of IPS replacements by several different people. Ups and downs to most. So: New community open source patch format project? Just an idea. Take a look at all the options currently available. What do you like, what don't you like? Why do they seem limited or not success? What can be done better? This would be something that would not rely on one or two people, something that would not die with the developer losing interest. Something that could be actively developed and improved whenever needed. If something like this were to be pursued, it should also involve input some of Acmlm's Board members as I'm pretty sure some of them would be interested(or not) in this as well. I'm just thinking a final collaborated effort to fix this problem is a potential option. It's just a thought. I don't even think large collaborated projects work, but apparently other people think they can, so maybe they can.  |
|
|
|
|
Neil
Guest
|
|
« Reply #1 on: December 13, 2006, 10:43:11 am » |
|
i would just like to point out that ninja is an open format, with all the details published. nothing stoping anyone from writing a patcher for it.
at some point we need to stop reinventing the wheel.
|
|
|
|
|
Tauwasser
Guest
|
|
« Reply #2 on: December 13, 2006, 10:50:57 am » |
|
I'm with Neil on that one. Somebody with enough c-knowledge or whatever can just make another patcher and it's all good  cYa, Tauwasser |
|
|
|
|
Nightcrawler
Guest
|
|
« Reply #3 on: December 13, 2006, 11:31:48 am » |
|
Except nobody will code another patcher for it because the original was written in PHP. And it seems the other people who want to code a patcher don't like NINJA and have their own ideas.
Nobody other than D will touch the codebase to further develop it either. Is it even going to be finished? Nobody even knows. NINJA 2.0 final never even came out.
|
|
|
|
« Last Edit: December 13, 2006, 11:39:19 am by Nightcrawler »
|
|
|
|
Dan
Guest
|
|
« Reply #4 on: December 13, 2006, 12:04:41 pm » |
|
NINJA is fairly decent, but I'm thinking that it could do with a bit of improvement in the NES department. Wasn't there a problem with iNES headers, where it wouldn't log any changes to the headers?
|
|
|
|
|
Neil
Guest
|
|
« Reply #5 on: December 13, 2006, 12:08:08 pm » |
|
Except nobody will code another patcher for it because the original was written in PHP. And it seems the other people who want to code a patcher don't like NINJA and have their own ideas.
Nobody other than D will touch the codebase to further develop it either. Is it even going to be finished? Nobody even knows. NINJA 2.0 final never even came out.
who cares about the codebase. the tech doc on the patching format is accessible to all. there's more to a patching format than the patcher. or do you just want someone to write another ips.exe that has a crc check? |
|
|
|
|
Klarth
Guest
|
|
« Reply #6 on: December 13, 2006, 12:14:04 pm » |
|
I want a patch format that can detect data that's been moved and do an appropriate data insert/delete operation, not just a replace everything option. One that has a description of the patch inside of it, CRC, etc. One that can contain multiple patches inside of one file and an API so you can conceivably build a program that can patch PSX games.
|
|
|
|
|
Neil
Guest
|
|
« Reply #7 on: December 13, 2006, 12:24:27 pm » |
|
take a look at the ninja format then. it supports all the stuff you just listed and more. http://ninja.cinnamonpirate.com/ |
|
|
|
|
MegaManJuno
Guest
|
|
« Reply #8 on: December 13, 2006, 12:27:56 pm » |
|
i would just like to point out that ninja is an open format, with all the details published. nothing stoping anyone from writing a patcher for it.
at some point we need to stop reinventing the wheel.
I fully agree... |
|
|
|
|
Kitsune Sniper
Guest
|
|
« Reply #9 on: December 13, 2006, 01:12:18 pm » |
|
If I could program, I'd write a patcher. And a patch creator.
Maybe I'll try it.
|
|
|
|
|
Klarth
Guest
|
|
« Reply #10 on: December 13, 2006, 03:24:50 pm » |
|
Oh wow, cool stuff. I was thinking about making a format like that but I didn't have the technical know-how to do it. That and I was thinking of making the algorithms myself rather than using publically available programs to create the patches... |
|
|
|
|
KaioShin
Guest
|
|
« Reply #11 on: December 13, 2006, 03:27:41 pm » |
|
So, why don't we just do it then? Any volunteers? As Nightcrawler suggested it would be a possibility to create a patch creator / patcher open source, so it will be maintained by the community.
I'm out though, no time for something like this and I don't have the programming skills.
|
|
|
|
|
Kitsune Sniper
Guest
|
|
« Reply #12 on: December 13, 2006, 04:55:17 pm » |
|
As long as it's open source and portable between operating systems, it's all good. The Ninja patching utility is good, but it's still .NET based so not everyone can use it at the moment... if this was written in C++, though, it would be relatively easy to port between systems, just write an appropriate GUI around it. Or something.
|
|
|
|
|
creaothceann
Guest
|
|
« Reply #13 on: December 13, 2006, 05:33:01 pm » |
|
The name "PIRATE" could be somehow appropriate to the ROM-hacking community. ^_^
But seriously, didn't we have this discussion already? It seems to me like the only way we'll get something done is that 1. someone starts coding his/her format, 2. people add their ideas & wishes, 3. goto 1.
|
|
|
|
|
KaioShin
Guest
|
|
« Reply #14 on: December 13, 2006, 05:36:39 pm » |
|
The name "PIRATE" could be somehow appropriate to the ROM-hacking community. ^_^
Exactly why would this make us pirates? D published the format specs, so that everyone can create his own applications for it. I don't see a problem with using this. |
|
|
|
|
Author