Stan` Posted January 9, 2021 Report Share Posted January 9, 2021 If you applied the patch you shouldn't get that error. The git link gives you A24 (more like a version of it anyway) the commands I gave you bring you back to A23B If you get the same popup but a different error try clearing the 0ad cache. Should be in ~/.share/0ad/cache (delete the folder) Quote Link to comment Share on other sites More sharing options...
BenMount Posted January 12, 2021 Report Share Posted January 12, 2021 Try to edit manually Quote Link to comment Share on other sites More sharing options...
GunChleoc Posted January 17, 2021 Report Share Posted January 17, 2021 (edited) On 09/01/2021 at 10:06 PM, just_a_fan said: BTW, what GitHub-link should I use when cloning the repository with git in order to get A23B? I am thinking using https://github.com/0ad/0ad/tree/535f7881d52ff25cabec5730c051f7552873b324, since that seems to be the commit with A23B. However, clicking on the green button 'Code' gives me again https://github.com/0ad/0ad.git, hence executing $ git clone https://github.com/0ad/0ad.git I will download A24 as before, I assume. That's due to the way git works. First you clone everything, which will put you on the latest version ("clone" command), because you haven't picked a version yet. After that, you can switch to any version you like ("checkout" command), but you always get the complete repository first. You can also save some bandwidth when cloning by using the "depth" parameter, but that would have made things more complicated for guiding you through. Edited January 17, 2021 by GunChleoc Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.