Author Topic: Multiple people building a module.  (Read 528 times)

Legacy_MadHaTr

  • Newbie
  • *
  • Posts: 14
  • Karma: +0/-0
Multiple people building a module.
« on: December 01, 2012, 09:28:42 pm »


               My brother wants to help me build the module i've been making.  

How do i make this happen, aside from transfering the mod file back and forth?
Is it possible to both work on it at the same time?
               
               

               
            

Legacy_henesua

  • Hero Member
  • *****
  • Posts: 6519
  • Karma: +0/-0
Multiple people building a module.
« Reply #1 on: December 01, 2012, 09:38:35 pm »


               You can't both work on the same module simultaneously.
BUT you can export and import your work. The file for this is called an ERF. In the toolset you can right click on a resource (area, creature, item, placeable, waypoint, trigger etc...) and select export. This will generate an ERF. Then send the ERF to the other person you are collaborating with and they can import it.
You also have an export option up in the menus. This export option allows you to export many different kinds of resources in the same ERF.

Grimlar's Guide to ERFs

Threads
Creating an erf?
ERF Inporting Problems
               
               

               
            

Legacy_Failed.Bard

  • Hero Member
  • *****
  • Posts: 1409
  • Karma: +0/-0
Multiple people building a module.
« Reply #2 on: December 02, 2012, 07:34:53 am »


               Then there's the nwnx method a server like Sinfar uses, where you add the erf to the module through the nwnx_resman plugin, and can then both work on and add to the module while it's up and running as a server.
That method is a bit more advanced, but by far the best system for it if you can manage to set it up, and give your brother limited ftp access to the resman directory.
               
               

               
            

Legacy_Tyndrel

  • Sr. Member
  • ****
  • Posts: 313
  • Karma: +0/-0
Multiple people building a module.
« Reply #3 on: December 02, 2012, 10:25:23 am »


               You can rename your brothers mod (or yours), changing the .mod extension to .erf, ensure the name has no spaces or punctuation and has less than 16 characters, then put it into the erf folder and import it just like any other erf.

When asked if you want to overwrite existing resources you will probably want to say no.  

As usual when doing such things it is best to back everything up first.  

When working on a joint project it is good practice for each builder to precede each resource they create with an initial followed by an underscore ( eg.  T_ ) to prevent accidental overwriting and to identify the author later.

'<img'>
               
               

               


                     Modifié par Tyndrel, 02 décembre 2012 - 10:26 .
                     
                  


            

Baaleos

  • Administrator
  • Hero Member
  • *****
  • Posts: 1916
  • Karma: +0/-0
Multiple people building a module.
« Reply #4 on: December 02, 2012, 06:30:01 pm »


               

Failed.Bard wrote...

Then there's the nwnx method a server like Sinfar uses, where you add the erf to the module through the nwnx_resman plugin, and can then both work on and add to the module while it's up and running as a server.
That method is a bit more advanced, but by far the best system for it if you can manage to set it up, and give your brother limited ftp access to the resman directory.


I use this method also.
I would be building in toolset, while also in my server, and when I build a script, I would ftp it to my server, test it out there, before committing to the final module.

Heck - sometimes I just run them from the externalsources folder - as it is a fast easy way to get around the 16k file limit.

If you and your brother want to work collaboratively, you could run a server at location X
Have a SVN Repository of your external sources - at location Y

Location X would be setup to download/svn update the external sources directory every 10 minutes or so.

Then, when you or your brother have stuff to test out, you just svn commit, and then that way its all version controlled, and self sustaining.