AoEZone or how to cry and complain about volunteer work while doing nothing yourselfWololoKingdoms, or how to make native AoE2 version as buggy as HD one
The result now is that ppl play with 3 different versions of WK on Voobly. Isn't that awesome?
Not to mention those who hasn't the HD version (why would they pay for a game they already paid for?), who can't update themselves.
Updated on the Community GitHub: https://github.com/AoE2CommunityGitHub/WololoKingdoms/releases/tag/5.7.4The auto-updater is messing up somehow. For now, I've uploaded a new version here with the auto-updater disabled: https://github.com/Jineapple/WololoKingdoms/releases/tag/5.7.4
I don't directly have access to the aoe2communitygithub unfortunately.
I'm sorry for the trouble. Hopefully this one works decently enough.
5.7.4 please, the other version is bugged.
Delete the old installation in your aoc data mods and re-install the latest version. The one from earlier today was bugged for everyone with that message.
https://github.com/Jineapple/WololoKingdoms/releases/tag/5.7.4
@Nicov
They do good work, and WK is overall a good thing to AoE2 (thanks to the volunteers), but the way those updates are implemented doesn't seem good to me. Yesterday we had RTSL and got notified just 10 minutes before game that we have to play on 5.7.3. St4rk had ghost units on his stream and players told that the version was laggy in game (is this good for tournament games?)
And today there is two updates in a row, leading to incompatibility between players.
Seems worth to mention, so that such problems doesn't happen in the future. Notifying those who implement those updates of such problems is important. Please don't be so hasty.
I keep having this annoying "An error occured trying to save the data file. Error Message: stoi" at 98%. What do I have to do?
You're right that the update process for this has been messy. We thought we could coordinate the release with 5.8, but that was delayed. Then there was the idea to have 5.8 as a separate "pre-release" data mod, but that also wasn't possible due to the circumstances. This affected changes to the installer, which was then done in limited time, leading to the khmer bug in 5.7.3.
Obviously having two updates is something we try to avoid but in this case with a clear gameplay bug there's not really another way.
Right now, I'm the only one who has things set up and the programming knowledge to do the code changes. Having another person (or more) to help with that and maybe also tackle some of the more basic issues (such as the occasional freezing) would of course be a big help.
Please do a fresh download of 5.7.4 from the github to make sure you have all the correct files. Then it should work.
Edit: @Nicov Are you on the 5.7 patch on Steam? If you are on the beta instead, that would cause this issue.
Hmm.. Installer is running until 14/22% and not responsing then. I was trying for 20 times, no reation. What should I do?
Thanks, it worked after 3 minutes waiting!Usually, just leave it alone and it "recovers". The installer is still working, it's just not pushing updates to the graphical interface often enough, making windows think it's not responding.
14% and 22% seem to be common percentages where the installer appears to freeze. Usually you can leave it alone here and it will eventually recover. I would suggest for anyone who has this issue to leave the installer alone for about 10 minutes, then check again if it has made progress. You'll likely see it jump from 14% to 22%, then to 69%.Hmm.. Installer is running until 14/22% and not responsing then. I was trying for 20 times, no reation. What should I do?
Coastal is still the default. Although I like the way you think...Does this WK version set Baltic as default map?