Go in to game AND start a new game. What exactly did you try? I did:
I do things similarly to JosEPh in that I have my copy of the SVN folder different to my modding and playing folder. I have a Sync program that comes with a compare files component that I use to see when there are changes between the two. I Put my work that I want to commit into my SVN copy then do a final update from the repository which used to tell me if there were any changes that affected the files I was changing. If there were I would inspect those changes and do some testing if they were in conflict. No problems then I commit. Currently I have an incorrect set up which I will fix when I get back.
ditto
It may have happened before, most SVN user with write access mess up something in their first weeks of modding experience, like forgetting to update before committing so that it may be hours or days since they updated when they commit. These kinds of errors can happen regardless of how the modder organize their files.
I was going to ask you what the benefits even are for this. My only concern has been the time it takes to upload or download a given file becoming too long to manage for weak internet connections. So with FPKs the size they are, this is not as much a concern. I'm a little concerned we'll start seeing some bugs as it is now because we found at some point you couldn't have more than some 8 or so FPKs without some things going wrong and fixed things, or so it seemed, by cutting down how many we had. I now wonder if it was a misdiagnosis and an incidental fix took place in the reorganization.
Ok, so this is what bothers me.
So any time you update the mod (fetch), you have to fetch it in the modding folder location and then run the install script? Are you saying that we cannot mod directly into the folder that the mod runs from? (AKA, edit the files and code in the folder which is inside the mods folder) Would take some getting used to, having to run the install script with every adjustment. I suppose it could be done but it doesn't sound pleasant. Adds an extra step for every single most minor change and one easily forgotten leading to wondering why your changes aren't showing up when you run the game.
I'm not sure what you mean by automatically sharing. This is the part that makes me think you're saying we can change files directly in the mods folder version and it will update back to the repository version and vice versa? That there's an automatic copy-over system in place? Even for file deletions?
This doesn't sound too bad, so long as we're not stressing the memory on some systems to demand those systems are maintaining 2 copies of the mod, which isn't a light demand if it's not a fairly modern system. I might need to store the 2nd copy in a D drive instead of the C due to memory limitations on the solid state drive.
Negative. It is ONE copy that appears in two places. It is a form of shortcut. A directory junction means that the actual same directory appears in two places on your file system. If you make any modifications inside that directory those modifications are being done to the same exact files and subdirectories. Not copies, but the actual same files.
You absolutely CAN. However it would not have most of the assets you want to modify, the loose art and source code would NOT have shortcuts in the mods directory, because the entire point is to not include them. XML and python WOULD be there because it is loaded directly.
See my above answers.
Like I said it is one copy just shared, so no extra space.
Well, the whole SVN setup isn't exactly user friendly to being with. I would prefer to just write a tool for our mod that does install and update for them (I think RoM had one). No need for tortoise svn, or copy pasting urls or whatever, and no need to worry what it is actually doing behind the scenes. This tool can also integrate detecting crash dumps and making zips, and linking to the forums/discord etc. etc.
Would this cause any problems with attaching a debug dll to the process successfully?
Some fascinating magic indeed.
I see no reason why? As far as Civ is concerned the linked files are all in the mod folder, it can't tell any difference at all.
Not if the original purpose of this thread is realized and I make the FPK live (tm) system
Forget about the mod folder entirely after running the initial setup, you do everything in the external folder from then on.
If fresh = delete the directories / root then yes.
I can life with the junction method as well i see no problems with using it.
Ok, as I thought. And just to clarify, if we do modify, say, an xml file in the mod folder version, those edits would automatically be also made in the external folder's version of that file right? So you couldn't do that with sources - they'd only be located in the external - but for more basic XML you could?
For whatever reason, if I have a debug dll compiled for the mod and I try to load a game saved on a different mod folder name so I then have to change the name of the mod folder to load their save, the debug dll will need to be recompiled for VS to attach to the process properly. I'm thinking this won't be a problem here because we're not changing operative mod folder/mod names and I think that's the key problem it hits.
In noted that he had another opinion but I haven't researched his option to the extent of understanding as far as this one yet so I can get a full comparative analysis going in my head.
I'm not thinking having to run an install batch after checking out a new repo folder to a non-modules location would be tough to tell people they have to do. I think anyone could probably manage that.
All the files mirrored between the external SVN folder and the working copy folder would actually be the same files, one is just a mirror of the other, so a change in one is the same as a change in the other.
That's how I thought I'm understanding this but I just want to make sure I'm not being stupid and misunderstanding.
You said others might 'not' so I was thinking you were saying the opposite... my apologies.
No i meant that i said exactly that to other modders but they said that additional step is too much to handle.
In the context of these discussions, many of us, self included, can easily get overwhelmed to the point of wanting to just say forget ALL that.
There would be no manual extra step to build FPKs and DLL. DLL is still just like normal in the repo, no extra step there. FPKs are build using the system I propose in the first post in this thread. i.e. entirely automatically. So no manual step there. Only manual step is run one extra script whenever you have done a *clean* check out.
You could but why on earth would you want to! You have one folder structure that does have everything in it, and then another that doesn't, just do all edits in the one that does!
I don't see there being a problem. The actual Mods\Caveman2Cosmos folder itself is NOT a link it is a real folder containing a set of links (Assets etc.). You can change that real folder name to whatever you want to get saves to work.
No you can't sorry. I did add that extra note in an edit on that last post as it might be surprising. However you aren't in a worse place than before because of this limitation. Before you could either have the mod IN the mods directory which is obviously on the same drive, or you could have it on another drive and have to manually copy/export from that drive, which you can still do just fine in the new system.
With the hardlinks you definitely CAN still start the game and load the mod from there, that is one of the reasons for this and not doing a directory restructure: it maintains that capability. /edit maybe I misunderstand what you mean here. There is no script to run after update with this system, only after clean get.
Hopefully that was when the additional step was running a script after every update (which would be annoying), whereas with the junctions it is just running it after every *clean* get. Although those are way more commonly required than they should be (roll on git
).
You won't be able to start C2C without the mod folder being exactly Caveman2Cosmos since PPIO was merged, so going forward there should be no players who have C2C saves made where the folder is named differently.
