We're back hotfixing the hotfixes! I apologize to all new players who were greeted with the worst possible first impression, a crash on New Game; a sneaky bug that only occured if you New Game right after launching the build, and slipped through our testing because we typically try to load a savegame first (in which case this crash didn't occur). Lesson learned, testing checklist adjusted, into a brighter future!
– David and the Bladesong team ⚔️
- Fix: Game no longer crashes on New Game
More from Bladesong
Other announcements
Patch 0.3.7578Greetings, swordsmiths! We're back with the next patch, fixing a number of minor issues, improving performance and savegame backups, and introducing the much-requested imperial units! As always, thank you for reporting bugs and telling us what you'd like to see in Bladesong. We're keeping a weather eye on our Discord and the Steam forums , so please keep it coming. Happy swordmaking! – David an…Hotfix 0.3.7508Swordsmiths, it's great to see all of you jump into Chapter 3 right away! Here's our hotfix patch to address the reported issues. Thank you so much for this, please keep reporting anything you find on our Discord . – David and the Bladesong team ⚔️ · Fix: Ezrae's wyvern commissions no longer appears again after victory · Fix: No longer locked out of getting Tuvain as a vendor when you're deep i…Chapter 3: Fire and Thorns update available now!Chapter 3: Fire and Thorns is a brand-new story chapter, introducing a new crew character and gameplay mechanics, opening your forge’s garden, and adding two new sword part sets. In Chapter 3, you face new challenges to reclaim Astrid from her fate, while famine and riots follow in the wake of the warehouse fire. Unravel the dark secrets of the Ashen Hand’s conspiracy and confront one of the Ma…