Noah Ryan

I am using it with good success! I still plan to do more with this at some point but I am using this library to generate levels for my roguelike,...

I have never tried using that option. I'm glad to hear about a speed boost- always welcome even though its been fast enough for me so far.

This is surprisingly tricky. Which keys are held is known to the input system, but this system only reports a single InputAction result. I don't really want to allow multiple...

Another idea is to just check for use-mode, and tell the display system which slot is in use. This is not the same as a held key, but should give...

I realized that we do have the information we need in the display system, and I implemented this concept. It works for both cursor mode and use mode items and...

This change will likely involve: types.rs new UseAction variant UseSkill actions.rs handle_skill, on skills that use use-mode, needs to set settings.use_action to UseSkill, log a UseAction msg, and change state...

There should be a more general discussion of use-mode and skills- we talked a while back about converting all skills to use-mode, but we will have to look through their...

Currently need to implement: level.rs calculate_use_skill to determine reach and directions of use-mode per skill. actions.rs finalize_use_skill to determine the result of using a skill with a chosen direction.

I'm made some progress on a branch where skills can enter use-mode. However, I'm not clear on how this will work exactly. We may have had this conversation before, and...

I have a branch with this concept implemented, as a proof of concept. It is not complete- all skills use the next tile over from the player instead of a...