News: 11 March 2016 - Forum Rules
Current Moderators - DarkSol, KingMike, MathOnNapkins, Azkadellia, Danke

Author Topic: Version Control and Romhacking  (Read 4244 times)

RedComet

  • Hero Member
  • *****
  • Posts: 3166
    • View Profile
    • Twilight Translations
Version Control and Romhacking
« on: March 28, 2012, 01:07:51 am »
So I've recently discovered the miracle of revision control (yeah, I know I'm  late to the party :P) and I'm wondering if anyone uses it for their romhacking projects? I know I'm definitely going to be using some sort of revision control from here on. Not looking for suggestions or anything.  I just wanna see what people are doing.
Twilight Translations - More than just Dragonball Z. :P

Ryusui

  • Hero Member
  • *****
  • Posts: 4989
  • It's the greatest day.
    • View Profile
    • Tumblr
Re: Version Control and Romhacking
« Reply #1 on: March 28, 2012, 01:20:25 am »
For Breath of Fire 2, I just saved old versions of my patch to separate directories. >_>

With Nanashi no Game, the project mastermind had a freakin' SVN set up. Took some getting used to, but worked pretty well. :3
In the event of a firestorm, the salad bar will remain open.

Gideon Zhi

  • IRC Staff
  • Hero Member
  • *****
  • Posts: 3518
    • View Profile
    • Aeon Genesis
Re: Version Control and Romhacking
« Reply #2 on: March 28, 2012, 01:46:53 am »
I just wanna see what people are doing.

My project structure hasn't changed since... god, since probably before Front Mission Gun Hazard in 2003. And you've seen what it looks like (i.e. a mess.) But it's what I'm comfortable with, so nyaaaaah!

KC

  • Full Member
  • ***
  • Posts: 209
    • View Profile
Re: Version Control and Romhacking
« Reply #3 on: March 28, 2012, 03:12:15 am »
I use SVN for all my projects, too. It's very handy, if you take enough care and commit changes often. You will have an easy time figuring out where any issues were implemented, as you can go back to any previous version with just a few clicks.
It's of course also useful for exchanging data. Give everyone involved access to the repository and you'll never have to manually send or replace files again, you just update and it's there. I also give the translators all the necessary data so that they can always build the most recent version of the game themselves, allowing them to test changes right away.

Nagato

  • Jr. Member
  • **
  • Posts: 41
    • View Profile
Re: Version Control and Romhacking
« Reply #4 on: March 28, 2012, 03:57:59 am »
For the past few years I've pretty much force every project I work on that didn't have some kind of solid leading behind it to use a form of revision control if I was going to put any serious effort into the project. I've never had anyone complain about it in the end either, since it takes only an hour or two to train people on the basics. I remember the horrors of trying to swap files through email and IRC and something inevitably getting lost. Never again. I also use SVN for any serious projects I'm working on even if I'm working alone. For that I usually just use a single private repository. Just having the diffs for every version has been helpful.

Assembla has allowed you to create free, private SVN and Git repositories (which can be set to public later if you wish to share it with everyone) for the past two years or so now so in my opinion there really isn't any reason not to use some kind of revision control. There's also Github and Bitbucket if you want something else but I don't think they allow projects to be private.

If you're reading this and you don't already use some form of revision control, go try it out. Seriously. It only takes a few seconds to create a repository on Assembla and then maybe an hour or less to get familiar with Tortoisesvn if you're on Windows. It's a small price to pay for making your project much more organized and easier to work with as a group.

MathOnNapkins

  • Forum Moderator
  • Hero Member
  • *****
  • Posts: 637
  • Who ya gonna call
    • View Profile
    • Arc-Nova - Rohmackin' and Chiptunin'
Re: Version Control and Romhacking
« Reply #5 on: March 28, 2012, 12:55:44 pm »
I've recently begun using it, and I have to say I'd have a hard time going back to not using it. Even if I don't use a lot of the features, I really hate losing work (I lost a week's worth once). And with TortoiseSVN being so easy to use on Windows, there's really little reason not to. I also hear git is pretty easy to use too, though I'm not very familiar with it. I used to back things up between computers with a USB drive and manually merge changes to keep things up to date, while making full backups occasionally as my only history. That is such a chore compared to just comitting some changes and being done with it.

justin3009

  • Hero Member
  • *****
  • Posts: 1623
  • Welp
    • View Profile
Re: Version Control and Romhacking
« Reply #6 on: March 28, 2012, 03:16:04 pm »
I need to find a better organization method.  All I do is just have multiple copies of the file dictating what day and time it was last modified.  If anything else is necessary, I add a short description to the file name as well.
'We have to find some way to incorporate the general civilians in the plot.'

'We'll kill off children in the Juuban district with an infection where they cough up blood and are found hanging themselves from cherry blossom trees.'

DaMarsMan

  • Hero Member
  • *****
  • Posts: 1288
  • Bring DQV
    • View Profile
    • DQ Translations!
Re: Version Control and Romhacking
« Reply #7 on: March 28, 2012, 03:20:50 pm »
I used to use SVN but once I started using git/mercurial I'll never go back... All my rom hacking projects are revision controlled.

rastsan

  • Guest
Re: Version Control and Romhacking
« Reply #8 on: April 01, 2012, 05:00:09 pm »
Haven't used svn.  Thinking about using it for the 6 or 7 projects I am just the hacker for.  Though implementing that for nds files may be challenging for those who only translate text/spreadsheet files and image editors who won't work with any other software other than their preferred image editor. 
Strangely its only the projects that I don't really do anything but insert others work that this might be useful for. 

I prefer to debug after every change for my own projects though.  If any problems arise I want to fix them right away and not deal with them later.   
I think I may stick with an image and text repository. 


Pennywise

  • Hero Member
  • *****
  • Posts: 2259
  • I'm curious
    • View Profile
    • Yojimbo's Translations
Re: Version Control and Romhacking
« Reply #9 on: April 01, 2012, 08:25:13 pm »
I actually setup a SVN with Assembla, but I haven't actually used it and in fact Assembla keeps telling that they're going to delete it for it several months now. I'll probably never use the SVN as I have yet to do something stupid and haven't really lost or saved over any of my work.

Spikeman

  • Hero Member
  • *****
  • Posts: 1063
  • *unce unce unce*
    • View Profile
    • None at the moment, check out my Last.fm page instead?
Re: Version Control and Romhacking
« Reply #10 on: April 01, 2012, 09:03:23 pm »
I'm going to second the recommendation of Git over SVN. You might check out the Open Source rom hacking thread I made recently, there's a lot of links to projects, so you can get a good idea of how things are laid out.

Also check out my signature, there's a few links to my projects hosted on Github.
Open Source Hacking Projects: Guru Logic Champ, Telefang 2, (Want more? Check out my GitHub!)