Tracking combat, command, and alternate-history systems.
Noblemen: 1941 is an action-strategy game set in an alternate-reality 1941 shaped by World War II and a global plague. This repository records pre-alpha development work around third-person combat, unit command, resource management, fortifications, and multi-faction campaigns.
This devlog is for players and developers interested in tactical combat, alternate-history warfare, and ongoing indie 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.
- 🌱 Pre-alpha development — A public record of early implementation, testing, and iteration.
- 🎯 Third-person combat — Combat systems include armor penetration, bullet physics, suppression, and morale.
- 🪖 Unit command — Recruit, deploy, and direct infantry, armor, artillery, mechs, and other units.
- 🏗️ Battlefield strategy — Build defenses, capture locations, manage resources, and use tactical pause.
- 🌍 Alternate-history setting — A dark 1941 conflict combining historical influences with fictional factions and technology.
 |
 |
 |
| Component | Minimum | Recommended |
|---|---|---|
| OS | Windows 10 or newer | Not published |
| Processor | 2 GHz or faster processor | Not published |
| RAM | 4 GB | 8 GB |
| Graphics | Not published | Not published |
| Storage | 2 GB available space | 2 GB available space |
| Additional | Not published | Not published |
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: 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: 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: 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.
Q: Can I record gameplay and share it? A: No. Recording, streaming, and publishing screenshots of playtests is prohibited — build content is not final and is not intended for public distribution. Please respect this rule so that playtests remain comfortable for all participants.