<pulling out all the stops...>
AndarianTD wrote...
I've got the "Sanctum Flying System" extracted, packaged and ready to go. This is my first look at participating here, though, and after checking the guidelines in the first post I'm not sure I understand the procedure and format of the Monthly CC Challenge.
A whole barrel full of worms, there... <"can", boss. or "monkeys">
Monkey's can what? Hush, bird. <*raven scowl*>
The primary purpose of the CCC is simply and wonderfully to promote the creation of new content. Beyond that simple mission statement, it is a completely voluntary tradition with some of the most mature, considerate and generous participants I know. Oh, and the dwarf and I as well. <was gonna say...>
The rules, as they are laid down, are more guidelines than legally binding instruments <*don't* get into all the binding instruments again!>
Right.
My point here is to apply the guidelines with sense <no point claiming it's common...>
In regards to proceedure and format, i prefer the new content be emailed to nwncccmakers at gmail because this gives us an archive of entries and allows multiple coordinators to manage it. The format is determined by the content, for the most part, but we do ask specifically that the content be working in game and that we get some screenies to put up on the Vault. We would also like the stuff compressed. The Spirited Lass preferred .rar compression. I prefer 7z and AD hasn't stated a preference that I know of.
One of the things I'd like to point out is that it is the Custom Content *Challenge* rather than *Contest*. We aren't competing and there is no prize except the adulation of this old wizard and some fandwarves.
I'm also wondering if it shouldn't just be put up as a Vault contribution instead. Is there a link that explains what is done with the CC contributions once they're submitted, why a non-Vault link is asked for, and why we would need to be provided with tileset set and itp files ahead of time?
Which leads to the next point: This new content still belongs to the original author! By entering it in the challenge the only right you're giving us is *non-exclusive* first publishing rights <or something>. Particularly with the large and totally awesome entries (like Zwerkules Roman & Arabian Cities) I *ardently* encourage the project get its own page on the vault (and Nexus, for that matter). The quibble there (which comes from some ancient history) is that content in the CCC must be something new, as in not *previously* released on the Vault. Releasing it after the CCC is not only possible but, on my part, encouraged.
The non-vault link was asked for for two reasons - first to help demonstrate the content is not already on the Vault and to provide redundancy in case the gremlins are fiesty on the Vault.
The tileset issue I think was to help coordinate multiple projects modifying the same tileset.
Does the challenge actually try to merge all of the submitted content into a single hak package?
Now that last bit is something of an embarrassment: What we do with the stuff and do we actually try to combine it all?
Heh.
The Goal is to provide the content in builder-friendly form and then to put together a demo mod that highlights all that neat stuff.
We can usually get the Builder's Archive together without too much blood and tears, but getting anyone to build a demo is... well, it's not happening :-P
What I have prepared are the tileset haks developed by Estelindis, a hak containing the flying script system and most of the ancillary resources needed to use it (2DA files, creature blueprints, triggers, etc.), a demo module containing the script source and areas illustrating how to use the system, and a short user's guide. Since it's designed to work within a larger CC system framework, though, it does contain a few items of non-original content, and needs part of an outside hak system to work fully.
In particular, the ridable Pegasus models and portraits were developed by Hardpoints (partly on request for me, actually), and are credited in the documentation. Also, the flying system system is designed to work within the Project Q framework, and relies on q_race.hak to provide the flying phenotype. Although I had a small hand in helping to develop those files, I can't include them as part of a submission. The set and itp files are as Este developed them and aren't subject to change.
I consider things like that derivative requirements to new content.
Since I am considering (actually working on it right now) including several aspects (and models) from Tarot's MapMats, it might not be my place to propound the legitamacy of derivative requirements, but really! We are creating cool new things that depend on cool things other's have made. It's still new content and still advances the state of NwN.
I think that's all to the good.
Although this month's challenge theme did inspire my decision to finally get around to extracting and packaging it for use by others, the format in which I've prepared the submission could be posted as-is to the CC section of the Vault. Can anyone help me understand if perhaps that would be more appropriate, either instead of or in addition to submitting it to the challenge, given what I've described above?
My opinion is to send it in to the CCC and then set up a project page on the Vault. This is seriously good stuff and deserves to be both highlighted in the CCC and given a more permanent presence on the Vault.
But it's really your decision.
<...and hoping the old organ doesn't blow something>
