ac892006

Would it be possible for JuBot to adopt these strategies ?

I know it would be difficult to update the entire design document overnight but I think you should divide the document into sections and update it gradually . Once a section of the design document has been updated all patch submission or all code alterations must be accompanied by adequate documentation and alteration to design document , otherwise it would only be a matter of time before the design document would go out of date again . I humbly suggest that initially you could start by updating the design documentation relating to the various plethora of xml files such unit attributes , behaviour etc .

I am a student of computer science and engineering from India . Recently I reported some minor bugs with 0ad like sheep running away too fast , wild animals destroying buildings etc . I thought that these bugs were minor and i could use my limited knowledge of c++ and java-script to sort things out on my own and start to contribute to the project and later on once I have grasped game programming I can help the team add the remaining features which are yet to be implemented . But the moment I looked at the design document and then tried getting to grips with the code i was in splits . I found it very difficult just to navigate and find which part of the source code contained which features of the game . Everything seemed muddled up . I was unable to abstract the sections of the code which i would have to modify . As a result I gave up and left it to experienced developers to correct the bug's . Now I personally feel that it is essential to have a thorough design document . The design document should contain the following . 1. All the current and proposed features of the game in detail . 2. Detailed explanation of how each and every current features are implemented . 3. Where in the source code are the features implemented like which folders , sub-folders files corresponding to which features of the game . 4. How have they been implemented using c++ , java-script and XML etc . 5. Future scope of improvement and implementation of yet to be implemented features . If the above mentioned improvements are done then it will become much easier for new programmers to contribute the project . This will be especially help full to 0ad as it can access the vast pool of students who have a lot more free time on there hands especially during the summer and winter vacations . I am sure many students would not mind working 6 to 7 hours a day for a couple of months in a year to help complete the 0ad and there learn a lot about gamee programming . This would also help issues such as manpower turnover by allowing new developers to quickly come to grasp with the project . I hope you will consider my suggestion .

I thank you all for your prompt input on the matter so I did some research . Yes elephants do indeed destroy buildings . So elephants destroying buildings is not a problem . But currently in 0ad Lions and other animals also destroy building which is not possible in the real world . On top of that towers fortresses do not fire arrows at animals even if the animals are destroying them as well as they do not fire upon animals even when instructed (THIS A BUG) . So here is what I intend to do . 1. Elephants can destroy buildings other animals can not . 2 . Towers and forts can fire on animals if attacked or if instructed to do so .

Some of my villagers angered a wild elephant and the wild elephant followed my villagers back to the town center where it killed all the villagers and then started attacking the town center . After a while the town center was destroyed . Now what i am guessing is that this problem is not only with elephants . I think lions and other animals can attack buildings too . So what course of action that should I take . 1 . no animals can destroy building . 2 . only elephants allowed to destroy building