reinitialized the repo, add a .gitignore file to track only h and cpp file, first part of RED DLL code pushed (combat functions for vanilla/expansion).
Gedemon's done all his work in his R.E.D. branches, and left the main branch alone. I think perhaps a new branch could be started (maybe called "Community"), and perhaps whoward69's dll could be merged in as a starting point.
That's not going to happen. Whatever we do will have to be done from scratch. I suggest we come up with a couple of decent tools that would help modders, and build those into it. Then maybe we can get some of the other dll authors more interested. I have some ideas cooking up, and would love to hear anyone else's, also.
There's a project I just circled back to, involving the mass and/or automatic upgrading of units, and obsolete unit notifications and such. I'm hoping that as I dive into it some of the trickier stuff will take some DLL work on my part. We shall see.
Moderator Action: Split done, the community DLL thread is here
Once you've cloned the repository on your computer, first thing to to is to create a new branch for your changes. Do not edit the master branch, this one should contains only the official patches.
Then in your new branch, try to have one branch for each feature, this way anyone can merge a feature in his mod without adding the whole code.
Say you're using the same system as whoward69 to make your DLL configurable before and after compiling, you may have a main branch with only the CustomMods.h modification and everything related to handling the configuration, and then all other branch containing the new features based on the main branch.
Right now I'm connected to your repository but not doing anything with it other than grabbing the base code from there. Initially. My reasoning is I want to play with and understand (and screw up multiple times) my git-hub until I feel I can work with yours and do no harm
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.