Leaderboard

Mane don't have bones, i know its a thing nowadays to have fluid hair but mane is more a paint over the neck rather than a individual properly rigged hair with gravity physics. Too much high end gaming for a RTS .

OMG... lol haha. @wowgetoffyourcellphone @borg- Stan must be aware, i guess. @Stan` @Nescio @Trinketos @Bigtiger

Yes, he have to committ the files, since the blackout in my country i coulnd't commit and have always Http 408 request timeout To clarify how the horse textures are now: Horses were used to have different texture per rank, now the actor just change the rider and other visual assets (blankets or armors) don't see any reason why a horse change skins like a snake each time he promotes. I wish it could be a way to make horse keep the initial or basic version texture through rank in case in the future we find a way to make horses remain and infantry dismount. That way Horse is just a "Mount" in game therms instead of a full unit version.

A call to modders! HORSE UPDATE IS IN! i'll be glad to help modders to fix cavalry actors in order to keep in sync your mod version to SVN 24. let me know if need help, actors will be broken since all cavalry were replaced to a new mesh, and replaced textures actors lines for a simplified version of variants.

Hi @Nescio and @Itms, I have finished the Unit Listing and am attaching it now. I only found two items that did not have a "Specific" name, a Kush Bireme and Maur siege ram. I'll start working on the in-game documentation until I get some input from the developers on what they need. I am still kind of searching to find out what exists already. If you have any ideas or wants just let me know. Thanks, Dok Unit Listing Alphabetical.txt

Sounds great, thanks again, and take your time, there is no rush!

Not yet the auroch, the model lacks the vertex amount required to have a proper movement of the bodie with the armature. Im planning a sculpting process for the cattle family to have proper breeds, fauna and higher amount of textures.

Thank you for the European, senga, and zebu cattle. Their calves (infant) and the aurochs are not yet finished, I suppose?

Ty, now its fixed. Small bug when exporting with the new blender 2.80 configurations. Comitting fixed ".dae" file soon. Updating milleniumad horses.

we can use fantasy cliché armors? opulent use of colour and ornaments.

If the purpose of a review rule is to ensure that the commit was accepted by one person determined by the repository owner to be reliale and trustable, then this clause only costs more time and requires three instead of two people: If person B was not determined to be reliable and trustable to decide over the fate of a diff by the repository owner, then the postulated purpose of the review is not satisfied anymore (refs 2016, refs Diffusion_of_responsibility). If person B was determined to be reliable and trustable to decide over the fate of a diff by the repository owner, then person B would receive trust in a formalized way distinguishing it from untrusted members, which is equal to providing commit access for that purpose, without involving an additional person. So regardless of that clause, the difficulty is developing developers and developing trust. And as WFG history 2003 to today shows, luck in getting computer science students willing to develop on a daily basis. The process can't become simpler than one person knowing what they do if not sacrificing the objective of the deployment conditions to investigate the correctness of all parts of the development stack. https://en.wikipedia.org/wiki/Waterfall_model#Model https://en.wikipedia.org/wiki/Software_verification It's inevitable that if noone tries hard to disprove the correctness and completeness of a proposal that it will be defective. If each commit adds one or more defects and if the project is not finished until the defects are gone, the process will not converge towards a finished product. If a developer needs a guideline or someone else instructing them how to review a patch, then that rather indicates that the developer lacks the knowledge how to skeptically examine the correctness and completeness of a proposal to begin with. The developers that can determine the ramifications of the patch don't need instructions for that. The developers that can't determine the ramifications of the patch won't benefit from these instructions (because it is necessary to deduce the ramifications of the proposal in order to investigate the correctness and completeness). For code changes, consider a one-line change to the 6000 lines file in UnitAI. Impossible to test it based on any guideline. For balance changes maybe, although it's probably only reifiying what balance testers already do. Receiving 5 times the same bugreport every day for half a year and worse makes one appreciate the silence of users enjoying a balanced bug-free game. Alternatively going offline works too. Balance patches were mostly committed by the Wildfire Games members who were actually playing the game. Reluctancy to commit balance changes is attributable to many reasons, getting artists or programmers to commit balance changes is probably not the most time-efficient or quality-assuring procedure and the reluctancy would be justified in that case. Reviews eat a lot of time, extraordinary much time for reviews outside of the comfort zone. So better figure out who will create good quality without help and let them do their thing. I suspect Wildfire Games members currently don't play the game, there's just a balancing department missing it seems. The question is only whether a balancing department makes sense at all (due to the overlaps with the design department which formulates some existing constraints (DD) and can't operate in the realms of realistic development without knowing the confinements of realistic development). About balance patches in particular, if the more five most trusted players already have eight different opinions on the patch, it's hard not to become reluctant. If those however would cohesively demonstrate for one balancing patch and can substantiate their claims well, one would have to be reluctant to not commit or provide commit access for the ones identifiying as active Wildfire Games developers. Getting someone else with commit access to spend their time is one of two solutions to the stated problem. (https://www.youtube.com/watch?v=SVY0D37FyBU)

https://www.theguardian.com/uk-news/2019/may/09/britains-equivalent-to-tutankhamun-found-in-southend-on-sea https://www.prittlewellprincelyburial.org/ Anglo-saxon burial chamber found.

There's a decal under each tree (something like dirt) it's not very noticeable but enough to help add more blend into the terrain.

From Preview: Medewi 2.0, a TW mod (ignore every other unit in that roster... Way too much conjecture/speculation and plain wrong equipment) This unit didn't actually look so bad. I actually quite like it. Quilted cotton armour for the rider should have long sleeves, and extend down to as low as the knees. Quilted cotton armour for the horse shouldn't extend to their heads.

Yep, i don't know how i get there, neither how i end finding that way of making it works.

there will be another soon, on borg mod xD

Kush Bireme is a Ptol placeholder unit without a specific name for now. We need a large Nile boat to replace it ( @Alexandermb )