fredriq/fiqrogue

Experimental roguelike using libuncursed

fiqrogue's Issues

libuncursed's SDL interface is kind of broken

While functional, it is flawed. This is not a fiqrogue issue, but libuncursed currently has no dedicated bugtracker. The major one is the fact that it blinks quite a lot, and resizing the window results in a lot of blinking and a major lagspike

Add monster AI and fighting capabilities

The code currently has the capabilities of dealing with several monsters at once, but currently non-player ones just use a dummy AI that walks right unless it's far too the right already in which it walks left. There's also no collision checking for monster-to-monster (there is for "walls"), you can walk right into another monster (and vice versa) and the game wont mind.

It would be nice if other monsters actually chased you around, intent on disposing of you. Also, the reverse should be possible as well.

Fix x/y confusion

Currently, the code treats x as what is normally considered y, and vice versa. Oops.

Noticed when attempting to check for window height using uncursed's "getmaxx".

Message system

Currently there is no message-style output whatsoever. This is rather important to address.

Peer Review

Peer review by Nathan Bhat and Tor Baumgardt

1. Short README. You have made it clear how to install your program (although still a little confused on how to run it), but you should include features and a more in depth project discription. For the uninitiated a term like "rouguelike" might not be in their vocabulary.
2. The commit messages are good and descriptive. I'm wondering if you have small enough commits, being that you only have 17 commits, but I haven't looked into commit sizes.
3. While your current milestones are informative, it would be nice if you had milestones for a lot more of your tasks. It isn't too clear what exactly has happened in the project, and what you aimed to get done. Remember to connect your issues to each milestone accordingly. You have two issues, and they are well done, however you should write issues for most everything you want to do in your program to keep track of what you need to do next. I know you are not in a group so this does seem rather pointless, but good for learning.
4. You have not included any bugs in issues. We don't know if you have any bugs yet, so this might not matter.
5. You have only use branch "master" and you have 0 pull requests so I won't comment on this. Don't worry, it's the same for us ;)

Field of vision

Currently you always see everything. Implement proper vision functionality, add binary lightning and implement walls. The actual FOV itself should probably just use a simple shadowcasting algoritm once the features that make FOV actually relevant is implemented.

Inventory system with objects

Make one.