Only on 12.12.2019 we were allowed to start a new Knightfight game world after a long time. The developments are going on there and increasingly on the MonstersGame Rewrite. We would like to thank all players for patience and feedback. Therefore we are happy to offer you our Christmas special this year as well:
We thank you for your loyalty and wish you happy holidays!
Come prepared when the new KnightFight chapter is opened. In Trutzberge, a new world of merciless battles, arsenals of weapons and fresh guilds awaits you. Choose the good or the bad side. It's in your hands.
Once again we would like to thank everyone who made it to the far north and visited us at the Gamevention. We had a lot of fun and good playing hours with you. Especially thanks for the numerous discussions about KnightFight, MonstersGame and Wizard Tower. We are looking forward to the next event with you.
As promised (even though it took a bit longer, sorry everyone), here are the player-visible/noticeable changes:
Battleground, some of those references have been renamed, but there might still be references to the old term
Shadow energy (+13)now requires an alignment of -38000 or lower
Holy energy (+13)now requires an alignment of +38000 or higher
Shadow energy (+14)now requires an alignment of -43000 or lower
Holy energy (+14)now requires an alignment of +43000 or higher
Shadow energy (+15)now requires an alignment of -48000 or lower
Holy energy (+15)now requires an alignment of +48000 or higher
Shadow energy (+16)now requires an alignment of -53000 or lower
Holy energy (+16)now requires an alignment of +53000 or higher
Shadow energy (+17)now requires an alignment of -58000 or lower
Holy energy (+17)now requires an alignment of +58000 or higher
Shadow energy (+18)now requires an alignment of -63000 or lower
Holy energy (+18)now requires an alignment of +63000 or higher
RE:won't get another
RE:prepended when replying to messages
These are just the most important changes and doesn't include all the changes we've made in our backend. Overall the update consists of 716 changesets so far.
We still have a few bugs left to squash, which surfaced since Sunday. So we will work on getting them fixed as soon as possible.
Meanwhile, our artist is also working on some more new content, but let's not spoil the surprise with details yet... :-)
Next big update: MonstersGame! Although since this is a full rewrite it will land in 2020. We'll keep you posted.
We already announced that we were working on overhauling KnightFight and the big day where we switch to the new version is coming up.
The update will take place on Sunday, 17th November 2019 at 02:00 UTC (which is 03:00 German time) and will result in a downtime of about 3 hours if things don't go according to plan.
Please note that you will be logged out and need to log in again after the update is finished.
Further details on the changes will be announced shortly after the update.
The following information is meant for people who want to know more about the details on how we plan to migrate to the new version.
Essentially, we're going to switch from a bunch of old servers to our new infrastructure with new servers that we already prepared for the update.
Since we're switching everything to HTTPS, we also need proper TLS certificates. To make sure we don't run into issues during the actual update, we already changed the DNS records and generated the certificates and got them signed.
This means that right now, KnightFight is already hosted on our new servers by using HTTP proxies that relay everything to/from our old servers.
We also already changed backups and monitoring accordingly.
The first step is to put a placeholder page on all KnightFight domains, so that visitors know what's going on.
Next up, we're going to set all databases read-only and transfer the old databases to our new deployment.
Once this is done, we're going to apply all migrations that bring the databases in sync with our new code base. While we've already tested this extensively on production data, this is still the point where things might go wrong and it's also the main reason why we scheduled a longer downtime.
If nothing has exploded, we are new simply going to switch the web servers to the new KnightFight version. We're using NixOS, so activating the new configuration is only a matter of seconds.
At this point, the new KnightFight version should be up and running and the following items are left to do: