Tracking village layouts, clan choices, and battle iterations.
This journal follows Northgard Battlegrounds, a strategy auto-battler with city-building elements set in the Viking world of Northgard. Its core loop combines village development, building placement, divine blessings, and automated warband battles against rival players. This repository documents pre-alpha development and iteration around the project.
This devlog is for players and developers interested in strategy games, auto-battlers, and iterative game development.
🧭 About this repo. A development journal for a project in pre-alpha. It documents progress, tracks known issues, and aggregates feedback. Not a store page, not a distribution channel.
- 🏘️ Village Building — Place structures and develop a settlement around each clan’s needs.
- ⚔️ Auto-Battles — Send warbands into automated battles against rival players.
- 🃏 Fate Cards — Use cards and strategic choices to shape each match.
- 🪓 Viking Clans — Build around distinct clans within the Northgard setting.
- 🙏 Gods’ Blessings — Choose powerful blessings that influence the development of a clan.
![]() |
![]() |
![]() |
| Component | Minimum | Recommended |
|---|---|---|
| OS | Windows 10 (64-bit) | Windows 11 (64-bit) |
| Processor | Intel Core i5-8400 or AMD Ryzen 5 2600 | Intel Core i7-10700 or AMD Ryzen 7 3700X |
| RAM | 8 GB | 16 GB |
| Graphics | NVIDIA GTX 1060 6 GB or AMD Radeon RX 580 | NVIDIA RTX 2060 or AMD Radeon RX 5600 XT |
| Storage | 20 GB available space | 20 GB available space on an SSD |
| Additional | DirectX 11 | DirectX 12 |
1. Open the hub
- The project hub is where devlogs, patch notes, and milestone posts land first: open hub.
2. Link your profile
- Sign in with your platform account using the official sign-in button on the hub.
- Credentials never touch our servers — auth is delegated entirely to the platform.
3. Join a playtest wave
- Playtest invitations are sent in small waves as builds stabilize — usually one wave per week.
- No queue, no lottery: waves are filled in order of signup.
4. Send feedback
- Bug reports, clips, and suggestions are all welcome. Every report goes into the next build's checklist.
5. Credits
- Active testers are credited in release notes.
🧭 This repository is a development journal, not a store page. It documents progress, tracks known issues, and aggregates feedback.
Q: Who is this repository for? A: This repository is for everyone who wants to contribute to the game's development: testing builds, finding bugs, suggesting ideas, and helping the project grow. Here you'll find information about the current state of the game, the playtest schedule, and participation guidelines.
Q: What is this repository? A: A public devlog for a game in pre-alpha. Progress notes, known issues, and changelog entries live here.
Q: Will my progress carry over between playtests? A: By default, yes. Your progress is carried over between playtest waves. However, if you'd like to start fresh and test new mechanics without the influence of old saves, you can reset your progress at any time in the game settings.
Q: Can I contribute code or assets? A: Not directly — the project's codebase remains closed. However, you can shape the game's development through bug reports, suggestions in the Discussions section, as well as asset and fan content contests we periodically run for project hub members. The best submissions make it into the game with credit given to their authors.
Q: How do playtests work? A: Invitations are sent out in small weekly waves to project hub members. No separate application is required.
Q: I found a bug — where do I report it? A: Open an issue using the bug report template. Include the build hash, steps to reproduce, and the log file if you have one.


