https://crawl.montres.org.uk/rcfiles/crawl-git/damerell.rc
Mostly annotated, but feel free to ask me about specifics.
1 Thank
Edit: Oh I forgot to describe what this does but it’s in the comments! Your felid tile changes based on how many lives you have stashed 
{
-- visual felid lives indicator. more felid lives = bigger tiles
--cat1 felid
--cat2 felid_1
--cat4 felid_2
--cat5 felid_3
--cat7 felid_4
--cat8 felid_5
--cat9 felid_6
--cat3 felid_silly
--cat6 felid_silly_1
--cat10 felid_silly_2
felid_tiles = {"tile:felid_5", "tile:felid_silly", "mons:manticore"} -- 0 lives, 1 life, 2 lives
function update_felid_tile()
if you.race() == "Felid" then
crawl.setopt("tile_player_tile = " .. felid_tiles[you.lives() + 1])
end
end
function ready()
update_felid_tile()
end
}
Update felid_tiles to your liking. You can find tiles here https://github.com/crawl/crawl/tree/master/crawl-ref/source/rltiles (felid tiles are in player/felids/)
If you already have a ready() function don’t add another - Instead add update_felid_tile() to your existing ready() function.
We’ve all been here. Tab-tab-tab-tab away in your little chokepoint until you walk into the killspace and eat attacks from multiple enemies.
You might be tempted to tab slowly - tediously making sure that you didn’t advance after every keypress. You might be tempted to just accept that sometimes you’re gonna take a lot of sudden extra hits (especially if you move slowly with chei, statue form, naga, coglin…).
Here’s a simple alternative:
# don't use quiver with autofight_nomove, which we bind to a key below
autofight_nomove_fires = false
#unbind shift-tab from cmd_autofire and bind it to cmd_autofight_nomove
bindkey = [p] CMD_AUTOFIRE
bindkey = [\{-233}] CMD_AUTOFIGHT_NOMOVE
Now tab and p behave normally but I can use shift+tab in situations where I want to attack without throwing or moving!
CMD_AUTOFIGHT_NOMOVE is unbound by default and will fire from your quiver by default. I bound it to shift-tab and turned the quiver off for that command. Because I choose shift-tab, I had to unbind that from CMD_AUTOFIRE (which already uses p so doesn’t need the extra keybind).
Obviously, if you want to bind it to something other than shift-tab, you don’t have to worrying about rebinding cmd_autofire at all. If for some reason the {-233} keycode is different for you: you can find out what you need by starting to create a macro (ctrl+d, pressing shift-tab as the trigger key, noting what the game tells you the keycode is, then aborting the macro creation with esc.
2 Thanks
Am I correct in saying that if I bind autofight_nomove to shift_tab WITHOUT the first line, and say quiver some boomerangs, I can shift-tab whenever I want to chuck boomerangs until something’s in melee range and then start whacking it? I might be even more excited about that than I am about tabbing without lurching into YakPainLand.
If you want autofight_nomove to use the quiver, leave autofight_nomove_fires = true (this is the default, just don’t set it to false like I do) and bind it to whatever you like.
Personally it feels like I burn through ammo too quickly on non-consequential things if I use it like this but you do you!
An aside: I am unsure if the line bindkey = [p] CMD_AUTOFIRE is actually needed in my setup at all. I am unsure how it actually works. Perhaps binding ctrl+shift to another action is enough to unbind it from the original action?
Yeah I was thinking specifically of the coglin^Oka I was playing yesterday, who wanted nothing more than to conveniently stand still and bounce the endless boomerangs provided by divine providence off of stuff until it got close enough to slice; situational feature, but nice to have.
1 Thank