Tracking systems, combat, and world changes in pre-alpha.
AetherCycle is a first-person action RPG set in a changing fantasy world of ruins, villages, hidden paths, and dungeons. Its systems include fast combat, character leveling, abilities, loot-driven gear progression, and solo or co-op play. This repository records the game’s pre-alpha development and iteration.
This devlog is for players and developers interested in following an action RPG during pre-alpha 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.
- ⚔️ First-Person Combat — Iterating on fast-paced combat against enemies, elites, and bosses.
- 🌍 Changing World — Documenting a world where the Cycle shifts danger, paths, and exploration.
- 🧭 Dungeon Exploration — Building out ruins, hidden routes, villages, and underground areas.
- 🤝 Solo and Co-op — Testing progression and encounters for solo play and online co-op.
 |
 |
 |
| 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 8 GB | NVIDIA RTX 2060 or AMD Radeon RX 6600 XT |
| Storage | 20 GB available space | 20 GB available space on an SSD |
| Additional | DirectX 12 | DirectX 12, SSD preferred |
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 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.
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: 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 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: How do playtests work? A: Invitations are sent out in small weekly waves to project hub members. No separate application is required.