Featured Blog | This community-written post highlights the best of what the game industry has to offer. Read more like it on the Game Developer Blogs or learn how to Submit Your Own Blog Post
An introduction to two full years of an ongoing discussion series aimed at sharing a multifaceted look at the numerous topics behind traditional roguelike code, design, and more.
Creating roguelikes is a common pasttime among hobbyist game devs. Lower asset requirements free up development time to focus on the true nuts and bolts that make games both entertaining and challenging, i.e. mechanics. As with any type of game, there is a wide range of components and considerations that go into creating a roguelike, and there are as many solutions as there are developers.
That said, the core "roguelike problem set" is also fairly well defined, with most developers having to tackle similar problems that may or may not apply to games outside the genre. As such, it's interesting to look at many different approaches to the same set of problems.
Two years ago I began hosting a series called "FAQ Friday" over on /r/roguelikedev where we ask roguelike developers to discuss a specific aspect of roguelike development as it relates to their own project.
Participation has been strong, and you'll find input from the devs of Nethack, DCSS, Incursion, Cogmind, Armoured Commander, Black Future, Temple of Torment, Shadow of the Wyrm, The Ground Gives Way, Cardinal Quest 2, and a huge range of other games in development you may not have heard of yet.
If you're interested in an under-the-hood look at roguelikes in development, or thinking of developing a roguelike of your own, consider checking out some of these threads:
#3: The Game Loop
#5: Data Management
#7: Loot
#8: Core Mechanic
#9: Debugging
#10: Project Management
#12: Field of Vision
#13: Geometry
#14: Inspiration
#15: AI
#16: UI Design
#17: UI Implementation
#18: Input Handling
#19: Permadeath
#20: Saving
#21: Morgue Files
#22: Map Generation
#23: Map Design
#24: World Structure
#25: Pathfinding
#26: Animation
#27: Color
#29: Fonts and Styles
#30: Message Logs
#31: Pain Points
#32: Combat Algorithms
#34: Feature Planning
#37: Hunger Clocks
#39: Analytics
#40: Inventory Management
#41: Time Systems
#43: Tutorials and Help
#45: Libraries Redux
#46: Optimization
#48: Developer Motivation
#49: Awareness Systems
#50: Productivity
#51: Licenses
#52: Crafting Systems
#53: Seeds
#54: Map Prefabs
#56: Mob Distribution
For a compiled list of many in-development roguelikes and their devs who have contributed so far, see this thread. (Also, many of the same devs who contribute to these FAQs, and more, you'll find sharing progress reports and images in our weekly Sharing Saturday threads.)
We will continue to add more FAQs throughout 2017, introducing new topics every other Friday, and this week we will also begin revisiting all previous topics to give devs who missed them the first time an opportunity to contribute, or for others to share how things have changed for their previous or newer project.
/r/roguelikedev is a great place for beginners and experts alike to learn and discuss roguelike development. Check out our sidebar for tutorials, resources, and tools!
Read more about:
Featured BlogsYou May Also Like
