It's more of a refusal on their (your?) part to understand that we may not want WoC's version of a coding standard.
In any case, if the code is documented as you say, then it's an improvement to not being documented at all. But if the mooders of WoC are there to actually help the community, then they'd instead release modcomponents which we have more use for and would prefer instead. But if they're there to promote their own standard, then that's another story.
Well, you know what? They wrote it. They released it. They provided a way for you to retrieve it. I explained to you how to retrieve it, down to the keystrokes necessary.
They didn't have to write it. They didn't have to release it. They didn't have to make it easy for you to find. I didn't have to explain, several times during the course of this thread, how to retrieve it.
All the work has already been done; including giving you a way to find and use it, and teaching you how to do so. You still, obviously, have yet to even try. I don't think you've even looked at the source code; otherwise you would've known about the commenting standard. You would also know how obvious your assumptions sound.
You talk about an oppressive coding standard, like it's stifling your modding creativity. Thus far, the only thing representative of a coding standard in the DLL that I have seen, is:
- Comment out existing code. Deleting it makes it difficult to both apply and revert.
- Follow this tagging scheme for your changes. It makes it easy for humans to spot while scrolling, and it gives the reader all the information they need at a glance.
What coding creativity are you so concerned with? The ability to capitalize the first word of a function? The ability to omit the "p" or "i" at the beginning of a pointer or integer, respectively? The ability to omit the "m_" at the beginning of a Protected class variable? I don't understand what's so oppressive about being courteous enough to follow Firaxis standards before uploading a change to their database.
Your assumptions are, largely, incorrect. As the thread progresses, it becomes more and more obvious that you:
- Haven't looked at the DLL code.
- Will not look at the DLL code.
They aren't forcing a coding standard on you. You don't like their standard? Fine. Don't expect to be able to upload your changes to them. This doesn't, even in the least, obligate them to follow your standard of how they should release thier 1500+ individual changes as individual mod components, just because you're too lazy to do it yourself with the tools they provided.
And it's not an "improvement", like you say. That's been standard with WoC, as far as I can tell, since the project started. It's always been like that. So, again:
It's not that they're refusing to release mod components, it's that you're refusing to even try.
I back this with the facts that you haven't downloaded the SDK, you haven't read their standards in their forums, and that you still insist that it's their duty to go beyond all the tools they're laying out (that they didn't have to) and release each change individually so that you don't have to do numbers one or two.
In closing: Either download the SDK, and get the changes yourself- or don't. Whichever one you choose, stop being selfish. They've already done most of the work for you. Earlier in this thread, while not talking to you, I actually did
all of the work in finding the changed files; but I refuse to post the list of changed files because you need to learn to do it yourself. It is, quite literally, as easy as pressing "Ctrl+F".