Hello Everyone.

[Jeffery Sergent]

I'm Jeffery. I have been lurking in these forums since 2014 and I am thoroughly impressed with your dedication to this game mod for Civ 4. Even long after Civ 6 was released!

Anyways, I am now studying to become a professional programmer in C++ and Java with my computer science major and I was wondering if you guys were interested in having an extra hand in this project?

 

[billw2015]

Yes more coding help would be awesome!

Go here to see what you would be getting yourself in to: https://github.com/caveman2cosmos/Caveman2Cosmos

There is a quick video guide to getting set up:

There is a discord link in my signature below.

 

[Toffer90]

We welcome any extra hands offered; thanks for taking the first step in reaching out.

Do you have any particular projects/goals/ambitions for C2C, then that is fine, and we would like to hear about it.
If you to begin with just wanna be backup and do small tweaks, and misc stuff here and there, then that's cool too.
We may try to delegate work once in a while, but it is entirely voluntary to accept such delegation. Will usually just be an annunciation like: "this or that needs doing, anyone up for it?"

There is no individual result pressure on this team, we only expect good teamwork, which means showing considerations for other modders work, and that we don't step on each other toes.
Clear and honest communication about what one is doing, or intend on doing, helps a lot in regards to being a good team-member. Being able to discuss and compromise when other modders object to your intent/work is also important.
Introducing bugs one is unaware of on the master repository is something everyone does once in a while; and as long as you are dedicated in clearing it up afterwards then no harm done is how I see it at least.
Us moving over from SVN to git now in the imminent future will make it easier to work with branches which will add another layer of quality control for stuff pushed to the master branch.

Welcome to the team.

 

[Jeffery Sergent]

Thanks Toffer.

Although I do have a few things in mind that I want for C2C. (Mainly more random events with higher stakes and consequences, and also I want to help later implement more of the ideas MrAurze had a long while ago)
I mostly just want to act as a general support person that can help integrate everyone else's work together better. This code of this mod looks like it is all over this place and could use some streamlining.

I hope this modding project will give me plenty of the experience needed to make it in my field. I will try to learn python as well. I will look more at the other helpful info when I have the chance.

I also do not have a discord account, but I might create one soon. Anyways, thanks for the support so far.

 

[Thunderbrd]

Welcome aboard Jeff! As you get settled in, just let us know what you're working on, what your plans are as you go - and keep a discussion on those plans open for us to comment on. Yes, getting on Discord can help a lot particularly for coding. We can't deny there's lots to work on.

 

[Jeffery Sergent]

I have looked at my schedule. It would seem I have bitten off more than I can chew, which is something I do often. I am already stressing over this. It may be a while before I have acquainted myself with everything.

 

[billw2015]

It may be a while before I have acquainted myself with everything.

I know I linked the repo but just to be clear I wasn't suggesting you try to "learn" the code base or anything (in case this is what you mean by acquainting yourself with everything). It is too big and jumbled to do that with really, learning as you go is pretty reasonable. I just linked it for you to get a feel of it.

I mostly just want to act as a general support person that can help integrate everyone else's work together better. This code of this mod looks like it is all over this place and could use some streamlining.

If this is your aim then yeah you would need to understand the code well, you might want to consider starting with more focused goals. For instance we have a large number of errors we found recently, detected by static analysis. These don't require understanding the code base in general, just the areas where the problems are occurring (usually).