Dancing Hoskuld
Deity
Note: this tread is intended for notifying people about changes to the SVN (beta) version of C2C.
All bugs should go in the latest bug thread in the Bug Forum.
Reminder to SVN users: If something seems broke but it was said to be fixed then try deleting the C2C cache files in Assets/Cache.
Documentation for using SVN for C2C
A: Getting started:
1)Download and install Tortoise SVN if you don't already have it (http://tortoisesvn.net/downloads.html)
2) Prepare a folder to contain your copy of the project
4) After it's all copied you are up and running!
A: Getting started: Modders only IE those who are going to update files
1) Get a sourceForge login
2) Tell Koshling what your SourceForge userid is, so he can add you as project contributors
3)Download and install Tortoise SVN if you don't already have it (http://tortoisesvn.net/downloads.html)
4) Prepare a folder to contain your copy of the project
6) After it's all copied you are up and running!
B: Getting the current version into play:
1) Create an empty folder somewhere not inside 'program files'
2) Right click and drag the root folder of your working copy to this new folder
3) Select the 'export without versioned files' option
4) Move the result into your mods folder (and rename it from C2C to Caveman2Cosmos)
A different explanation of this by dusckr87 here.
C: (Modders only) Submitting updates
Modder Hints.
add from here and here.
Other stuff here and here
New May 2014 For information links
Releasing a Patch
See how to here.
All bugs should go in the latest bug thread in the Bug Forum.
Reminder to SVN users: If something seems broke but it was said to be fixed then try deleting the C2C cache files in Assets/Cache.
Documentation for using SVN for C2C
A: Getting started:
1)Download and install Tortoise SVN if you don't already have it (http://tortoisesvn.net/downloads.html)
2) Prepare a folder to contain your copy of the project
- Create an empty directory that will hold your working copy (i.e. - local directory on your machine which will be your 'image' of the central repository - this is where you will make your changes when you want to contribute them and where other people's changes will sync down to). I strongly recommend that this is NOT your 'live' copy in 'program files/firaxis/...'. Mine is in \development\C2C, but the location doesn't matter - just put it somewhere convenient where you have space.
4) After it's all copied you are up and running!
A: Getting started: Modders only IE those who are going to update files
Spoiler :
1) Get a sourceForge login
2) Tell Koshling what your SourceForge userid is, so he can add you as project contributors
3)Download and install Tortoise SVN if you don't already have it (http://tortoisesvn.net/downloads.html)
4) Prepare a folder to contain your copy of the project
- Create an empty directory that will hold your working copy (i.e. - local directory on your machine which will be your 'image' of the central repository - this is where you will make your changes when you want to contribute them and where other people's changes will sync down to). I strongly recommend that this is NOT your 'live' copy in 'program files/firaxis/...'. Mine is in \development\C2C, but the location doesn't matter - just put it somewhere convenient where you have space.
- (Moders only) You can make changes here without effecting anyone else while you are developing them - the rest of us will only see them when you commit them (see later)
6) After it's all copied you are up and running!
B: Getting the current version into play:
1) Create an empty folder somewhere not inside 'program files'
2) Right click and drag the root folder of your working copy to this new folder
3) Select the 'export without versioned files' option
4) Move the result into your mods folder (and rename it from C2C to Caveman2Cosmos)
A different explanation of this by dusckr87 here.
C: (Modders only) Submitting updates
To make changes (once I have added you as a contributor) just edit files in your working copy
to sync them to the repository when they are ready, select them then right-click (in Windows Explorer) and select 'SVN Commit'. Please give a meaningful description of the change in the 'Description' box when doing this.
To pull down other people's changes just do 'SVN update' on the root folder you created in (3) (or any subfolder if you know you are only after specific stuff). So we all stay in date I recommend we all do refreshes on the root quite frequently - before doing so you can use 'Tortoise SVN/Show log...' (usual right-click in Windows Explorer as is all SVN UI) on the root folder - that will tell you about any changes anyone has made so you'll have an idea of what a refresh would get (this list includes the description text for each revision, which is one reason why its important to provide a decent description when you do commits). I generally do a 'Show log' every day when I start (on AND currently since that was the only relevant SVN project until now) to keep up with what people are changing on an ongoing basis.
to sync them to the repository when they are ready, select them then right-click (in Windows Explorer) and select 'SVN Commit'. Please give a meaningful description of the change in the 'Description' box when doing this.
To pull down other people's changes just do 'SVN update' on the root folder you created in (3) (or any subfolder if you know you are only after specific stuff). So we all stay in date I recommend we all do refreshes on the root quite frequently - before doing so you can use 'Tortoise SVN/Show log...' (usual right-click in Windows Explorer as is all SVN UI) on the root folder - that will tell you about any changes anyone has made so you'll have an idea of what a refresh would get (this list includes the description text for each revision, which is one reason why its important to provide a decent description when you do commits). I generally do a 'Show log' every day when I start (on AND currently since that was the only relevant SVN project until now) to keep up with what people are changing on an ongoing basis.
Modder Hints.
add from here and here.
Other stuff here and here
New May 2014 For information links
- Description of terms trunkm Branch ets and what they are used for (here)
- Best practice requires a bit of knowledge about SVN
- Best practice requires a bit of knowledge about SVN
Releasing a Patch
See how to here.