Forums

I'm encountering several error messages when trying to create a new match in 0 A.D. on Ubuntu 20.04, specifically with the Zhu version. The errors include "failed to load GUI XML page" among others. Has anyone else experienced similar issues or have any suggestions on how to resolve them? I've tried reinstalling the game and verifying the integrity of the game files, but the problem persists.

This is awesome! Is this actually working? I tried installing it on my a26 version but the button didnt appear at the main menu

It. Looks. AMAZING!!! So what are the next steps? Fix the bug then convert previous articles, then merge? Or should we do a hybrid. Fix bug, merge, work converting articles and add them directly to game? On one hand, we might not want to ship something uncompleted.   On the other hand, this is an open source project. (Joke, don't hit me!) Also, it might be easier to figure out where all the files go in the main game with only a few articles than a billion.

Big news regarding the encyclopedia page! New features: - the ability to put images in the article header. I decided to place the images to the top right and the title to the top left. This saves a lot of space compared to other possibilities and it looks good with images of most aspect ratios. But I will talk more in depth about the implementation in a future post. - the ability to add subtitles. They are fully optional, but really enhance the header's visual appeal (in my opinion). - a button below the title that opens up the the template viewer showing the unit's in-game stats. Its portrait is embedded into the button, so players can visually recognise the unit from in-game as well. - buttons to directly switch to the next or previous article in the same subcategory (to the suggestion of @nifa) They currently do not include any text as I think the arrow sprites are enough of a hint as to what the buttons do. Here is a quick showcase: screen-recording-0ads-encyclopedia.mp4   Other improvements: - fixed GUI scaling on lower screen resolutions (down to 1024x768). This turned out as quite a hassle, but it had to be done eventually. I haven't tested it on large screens (yet), mainly because they usually don't cause problems. If you notice any problem with the GUI scaling, let me know.   As always I packed it into a mod, please try it out, any feedback is welcome! encyclopedia.zip   (unfortunately I have not yet managed to resolve the issue with the crashes, I recommend trying to open it multiple times and supressing the error, if you notice any patterns or have any idea on how to resolve it, please let me know)

.

there is a problem with creating teams rating, which is that it needs a pull request to the lobby code, which is harder to test (easy enough to change though), possibly on top of a mod to the game as well. @Dunedan is the lobby maintainer. last time we had this same discussion he said he would accept a pull request with good enough guarantees it wouldn't breack anything.

Hello folks! I have been hard at work on this, and things are starting to look usable. Here is a (probably incomplete) changelog: The CI works! It is still a bit raw and I deactivated it to save space on Jenkins, but I am now working on improving it. It is the last big chunk of work I have to perform, and then we will be ready to migrate. The nightly build now exists! Get it via SVN at https://svn.itms.ovh/nightly-build/trunk. It is generated from a month ago but I'll update it through Jenkins in the upcoming days. All the documentation was updated and improved during the JDLL event in May where I presented the project and received some feedback. I also improved the Privacy Policy based on feedback. Please head over to the wiki especially BuildAndDeploymentEnvironment. I need help! The glorious FAQ has been defaced by the conversion to Gitea, which uses Github-flavored Markdown. Is anyone interested in working on manually restoring the appearance of the FAQ, adapting it to its new home on Gitea? Please let me know if you wish to help. Basically it would be necessary to 1) cleanup the structure of the page, fix the tables, the raw HTML and hard links and 2) improve the appearance just like it was done on Trac, but using Markdown features instead of Trac features. The git repository now has a script for getting translations straight from the nightly build (the same will be done for Vulkan shaders) Links to changesets in the format [25001] on Trac are correctly converted to 04ec75ed7e on Gitea (and I fixed the commit text in that specific revision) Important Trac keywords (regression, pathfinding, design, ...) now have a Gitea label, but I can't easily automatically convert keywords to labels, so I will add the labels manually after the migration. Thanks in advance for your feedback!