Results 1 to 17 of 17

Thread: Redistributable Unit Repository

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1

    Default Redistributable Unit Repository

    As suggested by Fra70 in this thread, I think TWC should establish a repository of units, free for use in any modification.

    Anyone could submit a unit to the repository, with the following components required (I have not modded M2TW so if I am incorrect on anything, please correct me, I am going from my RTW experience):
    1. The texture files for the unit*
    2. Mesh file(s) for the unit (once we can make models)
    3. EDU addition
    4. MODDB additions
    5. Unit Card
    6. UI Icon
    7. Unit description
    8. Screenshot/Render of unit*
    9. Assurance that unit actually loads into M2TW*
    10. Keywords (swordsman, archer, late-medieval, etc., a definite list would have to be created so they they can cross-referenced without any guesswork)*
    11. credits

    Components marked with * are required... it is hoped, however, that as units are used, people can fill out the rest of the components (so, for example, if I upload a swordsman reskin with a screenshot, when someone uses it, they add their UI and unit card to the existing files).

    As for the structure, here is what I am thinking. Members create the unit, add the required files into a .zip file, and name it according to a very strict naming structure. They then send the zip file to a specific member of Hex with an FTP account (or the Registrar of the Mod Registry?). This person then uploads the zip file to the FTP server, and adds a post to the Unit Repository forum, in the appropriate thread (we can organize the units into threads... swordsmen can have a thread, spearmen another, or we can organize by colour, or era, it doesn't really matter in the end... just to save on the amount of threads is better than having a new thread for each one, opinions on this?).
    The post contains the keywords specified by the author, the author, the screenshot/render provided, files/components included, a description of the unit if provided by the author, and the FTP link to the actual file.
    The FTP is accessible by anonymous account, meaning anyone can download.

    Lets say you are searching for a unit, you can search the Unit Repository forum, with "Show Posts," and go through until you find something you like, then download the unit.
    Say, for example, you take the unit, make a unit card for it, and add a reskin to it based on the model you downloaded.
    You can then send the Registrar two zip files; the original unit, with the unit card added, and your name added to the "credits.txt" file as the creator of the unit card. And another zip file, of your new unit, with the original author of the mesh in "credits.txt". Credits.txt would probably end up including who is responsible for each specific component... it would be up to the author of the zip file to provide accurate information.

    Overall, I think such an idea as a unit repository would incredibly aid mod development... there are many "skin packs" that are commonly used, imagine if all of them could be combined, chosen, picked, etc., with much greater ease than doing it ad-hoc and by hand. And imagine if there was a much simpler and straight-forward method for unit release/distribution, instead of releasing everything together when it was ready, it is released one at a time, when each unit is ready... there are many, many units sitting on everyone's hard drive that never see the light of day, because the mod fails, or the unit is no longer needed/purposeful. This provides a very rich architecture for them to be utilized under.

    The system I've devised, I think, is incredibly robust. It requires little coordination; it requires a time investment from one individual, or group (the Hex member in charge, and/or whoever is assigned to take care of the unit-repository FTP), and allows the community to do most of the work themselves, as well as update and add to files and whatnot, to create a living, communative, evolving repository "entity."

    Thoughts?

    EDIT: I just want to add, I think the system I've mentioned can be "diffused." There is no reason TWC's server must host these files, there is every possibility here that the files can be hosted by whatever willing member (myself, general Sun, king edward, apoc, so on and so on) if they have sufficient space, and are able to create the proper accounts.
    Last edited by Professor420; March 04, 2007 at 01:43 AM.
    Count no man happy until he is dead.


  2. #2
    Soulghast's Avatar RAWR!
    Join Date
    Oct 2006
    Location
    Athens, Greece
    Posts
    3,912

    Default Re: Redistributable Unit Repository

    I like the idea, it will be very useful. Can I help? I can do you all the battle_models.modeldb codes and all the EDU codes. What do you think?

    Maybe a team for making units could be established, open to all other user-submitted units, so that the project won't die if people stop donating units.
    Last edited by Soulghast; March 04, 2007 at 02:27 AM.
    Ex-Curator
    Under the Patronage of Perikles
    Patron of Desperado † and Astaroth


    R.I.P Calvin

  3. #3

    Default Re: Redistributable Unit Repository

    Quote Originally Posted by RTR Fan View Post
    I like the idea, it will be very useful. Can I help? I can do you all the battle_models.modeldb codes and all the EDU codes. What do you think?

    Maybe a team for making units could be established, open to all other user-submitted units, so that the project won't die if people stop donating units.
    The beauty is, if such a team is established, or you want to dedicate yourself to making DB and EDU files, you can do that of your own initiative. Such a team, or endeavour, would be fantastic. But anything formal, required, built-in to the idea, etc., I think would be out of the nature of the communitarian or diffused-work/control principles of such a repository. The Repository wouldn't rely on a single team or member to fuel it (only an unskilled group (ie, not even modders necessarily) to coordinate it).

    Quote Originally Posted by Tsar Stefan Dusan IV
    My amendment would be splitting them in two sections:

    * Historical
    * Fantasy & Fun Units
    Handling the fantasy units will be tricky... my feeling is there won't be a ton of them (they are usually done for specific mods, I think, who may be reluctant to contribute to the repository, with good reason). Surely the focus will be historical, but I think fantasy and fun units will be more miscellaneous than a proper category.
    Last edited by Professor420; March 04, 2007 at 01:55 PM.
    Count no man happy until he is dead.


  4. #4
    Maced0n's Avatar Domesticus
    Join Date
    Jun 2006
    Location
    /root
    Posts
    2,420

    Default Re: Redistributable Unit Repository

    This is very good idea. Great
    We should have this idea long time ago..Byt still better ever than never

  5. #5
    Pnutmaster's Avatar Dominus Qualitatium
    Join Date
    Jan 2006
    Location
    Brooklyn, NY
    Posts
    1,572

    Default Re: Redistributable Unit Repository

    I agree whole heartily. With such a unit repository compiled, an open-source ZoR mod could be released to the public in weeks. For M2TW to stand on its own two legs as a compelling TW game, it needs a ZoR system...
    Under the patronage and bound to the service of the
    artist formerly known as Squeakus Maximus
    Stoic Pantheist of S.I.N

  6. #6
    Tsar Stefan Dusan IV's Avatar Loonatic on the loose!!
    Join Date
    Dec 2006
    Location
    Belgrade, Serbia
    Posts
    458

    Default Re: Redistributable Unit Repository

    As I posted in the original thread, I find this idea very inventive and could provide a large variety of units, to be hand-picked by any modder/s who wish to implement them in his/their mod. No more skinner-searching mod, relying completely on one big unit library...

    My amendment would be splitting them in two sections:
    • Historical
    • Fantasy & Fun Units


    I wish the best of luck for this idea, as it is incredibly creative and has huge potential.

  7. #7
    Lord Condormanius's Avatar Artifex
    Join Date
    Dec 2006
    Location
    Derby, CT U.S.A.
    Posts
    6,439

    Default Re: Redistributable Unit Repository

    This is great. I have created several custom units for my mod's Irish faction (i.e. Hobilars (mounted javelinmen), Mailed Hobilars (Mailed Knights on ponies), Dismounted Mailed Knights, Irish Spearmen Irish Warband, Irish Noble Bodyguard, Bonnachts, Gaill Gaedhil). *you can check out screens at my mod's main thread: http://www.twcenter.net/forums/showthread.php?t=85790

    I am happy to share, but I don't know the first thing about uploading files or anything like that.

  8. #8

    Default Re: Redistributable Unit Repository

    Well alright, I'm going to go ahead and propose this formally here, in hope that someone will come along and move it into the Prothalamos in the Curia if you guys like it.

    Curial Decision: Unit Repository

    Total War Unit Repository
    The Unit Repository is a collection of works, submitted by members of the Total War Community, under the Generic Public License. This work is available to be reused in any modification of the Total War franchise.

    The Repository is to be maintained and kept up to date by a Citizen (Chief Warden) appointed by Hex, and any other Citizens (Co-Wardens) the Chief Warden appoints.


    Wardens
    The Hexagon Council will appoint a Citizen to act as Chief Warden, who will have the duties listed hereafter:
    • Uploading new and updated files in a timely fashion.
    • Keeping the forum list of units correct and current.
    • Making sure applicants and entries conform to the requirements set forth in this proposal.
    • Keep the list of keywords current.
    • Arbitrating any ownership or crediting issues.
    • Contacting Authors whose files receive complaints.
    • Appointing Citizens to Co-Wardens to help him in his duties, and/or resigning as Chief Warden if he is unable to fulfill his duties.
    • Following all duties and procedures set forth in this Decision.



    Submission Protocol
    1. Applicant assembles files into a .zip document, with specifications outlined in the "Zip File Protocol" section.
    2. Applicant sends the document to a Warden, who uploads the file to the FTP server, and makes the appropriate post in the Unit Repository Forum.


    Zip File Protocol
    The .zip file will contain the following:
    1. Required: All requisite texture files for the unit
    2. Required: Screenshot and/or render of unit
    3. Required: Assurance that unit actually loads into target game
    4. Required: keywords.txt, as specified by the "Keyword Protocol" section of this Decision.
    5. Required: credits.txt, as specified in the "Credits Protocol" section of this Decision.
    6. Mesh file(s) for the unit.
    7. EDU additions required for the unit.
    8. MODDB additions required for the unit.
    9. Unit Card for the in-game Unit Description Scroll.
    10. User Interface Icon for the in-game Battle UI.
    11. Unit description, either for the Unit Description Scroll, or an informal description.



    Keyword Protocol
    The applicant will describe his unit by choosing any number of only the following words:
    [A list of keywords will be given here after discussion in a Curial Committee]

    If he seeks additional keywords, he must request so of the Warden, who will then add the keyword to the above list.


    Credits Protocol
    Every uploaded file must contain a text file listing all credits, named "credits.txt". Inside, will be listed the credited person(s) for each of the zip file's contents. If the work is derivative of someone else's, it is expected that it will be stated as such in the credits.

    All work submitted to the Repository is licensed under the GPL, and any work that is a derivative of any Total War asset is restricted by the respected EULA (End User License Agreement) as well.


    Forum Protocol
    A forum will be created for the Unit Repository, only postable by the Wardens. Inside, there will be a series of threads arranged into groupings based on [the decision of a Curial Committee]. Each unit will have its own post.

    The post will contain the keywords specified by the Applicant, a full-size image of the unit, a direct link to the file on the FTP server via an anonymous FTP account (no username or password required), the name of the Applicant, the files included, and any additional information requested by the Applicant or deemed by the Warden.


    Removal Procedure
    If a file is found to be illegal or deceiving in its contents or credits, it is to be taken down by the Warden. The Warden is to seek explanation from the Applicant, and restore the file or not at the Warden's discretion.

    If a file receives a sufficient amount of complaints as deemed by the Warden, for issues of substandard quality, he is to discuss the File with the Applicant for possible removal, at the Applicant's discretion. If the Applicant is not available, the decision is left to the Warden.


    Count no man happy until he is dead.


  9. #9

    Default Re: Redistributable Unit Repository

    Given that this is due to pass pretty soon, I'd start setting up a committee to discuss specifics of implementation.
    Count no man happy until he is dead.


  10. #10
    Halie Satanus's Avatar Emperor of ice cream
    Join Date
    Nov 2005
    Location
    London
    Posts
    19,971
    Blog Entries
    1

    Default Re: Redistributable Unit Repository

    Another one.... in the likely event that the same people would apply (or be cajoled) i wonder if what we need is a permanent TW commitee, oh wait we had one didn't we...bahhh!!.

    Anyway what do you think of expanding this, ie; a mod research forum with the unit repository and a map repository built in, Do you think this will get used much beyond the skins objects and animations threads??. I'm not so sure, perhaps expanding it a bit more would get people more interested, ie; community mod prodjects as with the trivium group, I'm not going to resurect that per se, but it might be an idea to set something like that up.

  11. #11

    Default Re: Redistributable Unit Repository

    I'd rather just keep the focus on what we have now and make sure it works before expanding it... expanding it may bring in further people, but if it cannot be sustained now then it certainly will not be as a larger enterprise.

    My suggestion is we need to first figure out who can host the files. I have lots of space, I know CNSW does, General Sun may or may not be willing, I'm not sure. TWC could also host some I think. Any handful number is enough for now, no need to go overboard. I suppose Hex will need to choose a Warden as well, and then we can get started pretty quickly, as soon as the FTP accounts are created and configured. We'll also need a quick reference guide and FAQ for the repository (curial legal-speak can be scary and is certainly not time-efficient for the end-user).
    Count no man happy until he is dead.


  12. #12

    Default Re: Redistributable Unit Repository

    Do MODDB files cover new animations the unit may require?

    Also, might I suggest that each entry be for a specific unit model and animations if necessary? The model is the important part; the underlying chassis. Each entry could be the model, with subcategories of accompanying skins, unit cards and EDU entries.

    This would keep things a lot cleaner.
    Under the patronage of Simetrical. I am but a pawn in his evil schemes.

  13. #13

    Default Re: Redistributable Unit Repository

    Just an update.

    I've done some preliminary testing, and I've been working on the RUR (redistributable unit repository) some, but I won't have time to finalize it all until two weeks... shortly after that it should be ready to roll.
    Count no man happy until he is dead.


  14. #14
    Halie Satanus's Avatar Emperor of ice cream
    Join Date
    Nov 2005
    Location
    London
    Posts
    19,971
    Blog Entries
    1

    Default Re: Redistributable Unit Repository

    That's pretty good timing i think, in a couple of weeks a few members might have got to grips with Milkshape editing.

  15. #15

    Default Re: Redistributable Unit Repository

    I'm having terrible problems learning to add a unit, as my modeldb code always seems to be wrong (M2TW is cooler than MTW, but swapping out units with semi-generic models/skins is much more difficult), but I have several EDU and Card additions I'd like to offer out freely, both on the unit-balancing for additional historical units, that aren't strictly necessary but might make good flavor units as mercs.

    Will collaborate and start donating units with anybody who can help me figure out why my model code is always wrong...

  16. #16

    Default Re: Redistributable Unit Repository

    Well I can't figure that out for you,

    But I did start adding units, actually its progressing fine. I look forward to those additions when you choose to submit them. Hopefully in a couple weeks when school ends I will finish uploading a sufficient amount of units... I wish people were more organized in their releases...
    Count no man happy until he is dead.


  17. #17

    Default Re: Redistributable Unit Repository

    I know the feeling. I've just finished round One of grading, and am in the lull before my students' term papers hit...

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •