The player selects a walkable tile within a given range that has to be next to an obstacle, and then they have to choose a target tile that they are going to land on. One of the skills that I thought of was "leap and bounce", a purely movement skill. Besides the basic "handle", "move" and "skip turn" commands, I implemented a "look" command, and a more complex one, "leap and bounce".
#Keeperrl creatures not generating mana code#
So currently, the relevant code is messy and verbose. I'm currently trying to implement a few slightly complex skills, to see what abstractions will be needed. Commands can be arbitrarily complicated but ideally they should use the same, modular user interface to fill them. AI should fill the parameters by itself, while the player should fill the parameters using the GUI. walking (direction), looking at (tile), attacking (entity) etc. Here's a video that shows a few of the below : arrows, homing arrows, highlighting and self-propelling!Įvery action that entities can perform needs typically one or more parameters. This week's work was mostly user interface, plus a bunch of miscellaneous things. LICEcap: An easy way to record gifs of your roguelike in action.REXPaint: ASCII editing tool for art, mockups, mapping, design.Get motivated!įAQ Friday: Discuss specific approaches to various aspects of development.įeedback Friday: Play a designated WIP roguelike and give feedback ( dev sign up instructions). Sharing Saturday: Share your progress (screenshots, changelogs, bugs :D). Tutorial Tuesday: An annual learn-to-make-a-roguelike series! Next one is not until June 2022, but check out the records for samples across many languages and libraries. Discuss WIP roguelikes and a broad range of RL dev topics.
A community of active roguelike developers.
0 kommentar(er)
