What features would be most important to you in a roguelike library/framework?
I'm taking a stab at generalizing some of the Unity stuff I've done into a general-purpose framework for Unity RLs, and wanted to grab some early opinions from the subreddit.
If you were looking at a roguelike framework/library/template project, which features would be the highest priority for you? How would you want your workflow to be for some common things like creating new creatures/items/skills? Which things would be a deal-breaker if they didn't exist in the framework? I'm especially interested in things you'd consider non-obvious.
Thanks for taking the time to respond!
Posted Feb 14, 2019, 7:14 PM UTC
I think most people love frameworks. Alas, I'm not one of them... I'll give my reasons and then maybe we can come up with some ideas, and then maybe your framework will be the first one that I truly like!
When I code my roguelike, I do it for fun, as an artistic expression almost. The freedom I have when making a roguelike makes it enjoyable. When using a framework, I don't have freedom; my roguelike can only do what the framework lets me do. Thats the tradeoff we knowingly make when using a framework; we get lots of functionality for free, but sacrifice freedom in the areas the framework doesn't yet support.
It also changes the way we program: when coding something from scratch, or when putting various libraries/pieces together, we're figuring out the best and most elegant way to do something we know is possible. When we use a framework, we're often hunting through obscure and arcane documentation to find a way to trick the framework into doing what we want. Some people like that way of programming, but I'm not one of them.
However, there's a big caveat here... if you can guarantee that the user will never reasonably need anything outside the capabilities you offer, then a framework won't feel so constraining. For example, if you made a Unity library that acted like a terminal, and offered the same capabilities, and the user came in knowing that that's all they get, and those are the constraints they agree to, then that's fine. In other words, their expectations are a huge factor. If you make a framework, make a well-rounded set of features, and cut away the features that might raise their expectations for the rest of the framework.
So, all that said, I'm very glad you mention libraries! I love libraries! Precisely because they (usually) don't have this problem. A library is a building block that doesn't spread its cancerous tendrils into the rest of your program. I think that's the most important feature I'd want.
Big question: You mentioned Unity, does that mean that one needs to know Unity to use your framework/library,? Or will that all be abstracted away?
Now, for specifics! I'd personally like:
If your framework/library is mostly a helper/abstraction over Unity, I might like:
I happen to be making a Unity view for my already-somewhat-console-based roguelike, so I've been doing a lot of thinking in this area. I'd be happy to compare notes!
Just booleans, for passable/impassable? Nothing about terrain types, doors, room types, entry/exit points (stairs, etc)?
Sure, why not, since it's a wish list! My roguelike isn't that complex yet =)