Highlights:
Screenshot of the new War Info screen
In the war info screen:
Screenshot of the new Battles table
This proved quite the challenging feature to implement, as I had been lazy early on when it came to mapping the course of a nation’s trajectory through tag switches. See my previous post for a bit more background.
Tracking tag switches is especially important if one wants an accurate war info screen. To illustrate imagine a battle defender:
defender={
artillery=4000
infantry=36000
losses=8231
country="BYZ"
war_goal=3
commander="Leon Tornikes"
}
See that “BYZ” (Byzantium) is the country. If we wanted to look up the commander (eg: to find his fire pips and such) we need to know which Byzantium to search for. It may seem like an odd notion that there could be multiple Byzantiums, but it’s possible. There is a Byzantium at the start of 1444 but they are quickly annexed by the hungry ottomans. Another country could form Byzantium later through tag switching. When this tag switch happens, the initial Byzantium’s history (including a history of their generals) is relocated to the latter’s original tag.
So I set to work on rewriting the query engine to better follow tag switching, annexations, and releasing of countries.
To visualize this improvement in accuracy let’s look at a deficiency in the old version of Rakaly. Below is a true heir of timur run where the player tag switched from Sistan to Delhi and then immediately from Delhi to Mughals. Since Delhi exists at the start, there would be multiple concurrent data points for monthly income even though that shouldn’t be possible when playing single player.
Old version of Rakaly couldn’t track tag switches properly
This is no longer a problem with the update
New version of Rakaly that knows exactly when tag switches happen
Sometimes it’s nice to have an overview of the multiplayer lobby to answer the following:
A player view was added to answer those questions
New players view
Feel free to get in contact via Discord or hi [(at)] rakaly.com