Information
![]()
Name: Errant Kingdom
Genre: Visual novel, 2DCG, Male protagonist, Female protagonist, Gay, Lesbian, Dating sim, Fantasy, Romance
Version: Part 4 (Prologue & Chapters 1-7)
Censorship: No
Author: Lunaris Games
Last updated: 12 January 2023
Language: English
Made in: Ren'Py
Size: 1,10 GB 7Z / 1,29 GB UN7Z
About game
The Kingdom of Novus has been thrown into disarray, and it's up to you to decide if you’ll help to bring peace, or if you’ll stoke the fires of chaos. Enter a high fantasy world steeped in political intrigue; where magic touches the land and blood turns the wheels unseen. Dishonour & betrayal. Hope & despair. Pick a side, and meet your match.
Changelog
UPDATE NOTES
- This update brings our total word count to 403,325k
- This is the penultimate update! Our next update in two weeks' time will be our epic finale
PATCH NOTES (FIXES)
AMBASSADOR ROUTE
- The end of the previous update was looping the throne room scene after the end screen had finished displaying. Now fixed. If you saved at the end screen this shouldn’t give you any issues.
- Due to a variable being misdefined, if you entered the Raiden & Lucien poly route via Raiden’s romance you will need to replay the previous update from the menu choice, "Lucien would be very upset," in the castle gardens to ensure your Raiden & Lucien poly route triggers in future updates.
KNIGHT ROUTE
- A line of text introducing Lucien to the scene in Maja’s atrium was missing, this is now added.
- A repeated block of text has been deleted from the scene where you either speak to Roux or Erik underneath the tree. There was also a line referring to Erik being present in Roux’s romance route which has now been removed.
- Due to a variable being misdefined, if you entered the Raiden & Lucien poly route via Raiden’s romance you will need to replay the previous update from the menu choice, "As much as you like Lucien?" in the market to ensure your Raiden & Lucien poly route triggers in future updates.
NOMAD ROUTE
- An error where, in the Erik romance route, a variable for a menu option in his cabin was not defined correctly and may have produced an error screen. This is now fixed.
