V 3.5 now in feature freeze
Collapse
X
-
Comment
-
It's possible the polymorphed thing was on a trap or open/broken door. I submitted some fixes for that and a few other things, so they should be appearing in the nightlies soon.Comment
-
I just though that maybe the message should be the usual 'You cannot use that command here', or whatever it normally says.
Of course it could just be the case that there is no point in @ investing in candles for his living room, given that he's hardly ever home. He just has to go outside to read his WoR...Actually no, thinking about it he's carrying a light source so there should be plenty of light in his home (when he's in it, that is).Comment
-
I certainly won't be losing any sleep over it!
I just though that maybe the message should be the usual 'You cannot use that command here', or whatever it normally says.
Of course it could just be the case that there is no point in @ investing in candles for his living room, given that he's hardly ever home. He just has to go outside to read his WoR...Actually no, thinking about it he's carrying a light source so there should be plenty of light in his home (when he's in it, that is).Glaurung, Father of the Dragons says, 'You cannot avoid the ballyhack.'Comment
-
- Numbers instead of labels wil be used when using a command on an object, if that object has an inscribed tag - e.g. if you inscribe something @q0, it'll show up as '0' on the menu instead of its letter
- Inscriptions now use the roguelike keyset if that's the keyset you're using
And while I'm on the subject, one other consideration. The squelch key in the roguelike keyset is ^D. Ideally, how should one inscribe an item using the roguelike keyset to prevent it being squelched? Should it just be a literal '!^D'?Comment
-
So I finally got a chance to try out the roguelike inscriptions (using build 546-gee7b329), and unfortunately it doesn't really seem to work for me. Take staves, for example. If I inscribe a staff with '@Z5', it will show up with a 5 next to it in the list of staves when I press Z, but pressing 5 won't actually select that staff. On the other hand, if I inscribe the staff with '@u5', it will show up with its inventory letter in the list, but I can actually select it by pressing 5. There's a similar pattern for other types of inscriptions where the standard and roguelike keysets differ.
And while I'm on the subject, one other consideration. The squelch key in the roguelike keyset is ^D. Ideally, how should one inscribe an item using the roguelike keyset to prevent it being squelched? Should it just be a literal '!^D'?takkaria whispers something about options. -more-Comment
-
One quick question though...
Is there a reason why the ability to drop an item from within the 'i' or 'e' menus has been dropped? I find it very handy to look at an items abilities/damage using 'i' or 'e' and then instantly drop it by hitting 'd'. I know you can still 'k' it, but that's an extra keystroke (choosing between 'this particular item' or 'all whatevers') and besides, I might not want to squelch it, just drop it.
No biggie though.takkaria whispers something about options. -more-Comment
-
For me, the inability to drop things from the inventory or equipment menu persists, but not consistently. I haven't focused too much on figuring out when it works and when it doesn't, but certainly missiles, artifact, and ego items seem particularly affected. I will try and make note of the keystrokes and items the next time it fails, and let you know.“We're more of the love, blood, and rhetoric school. Well, we can do you blood and love without the rhetoric, and we can do you blood and rhetoric without the love, and we can do you all three concurrent or consecutive. But we can't give you love and rhetoric without the blood. Blood is compulsory. They're all blood, you see.”
― Tom Stoppard, Rosencrantz and Guildenstern are DeadComment
-
However I am using 510-g1b93088 which I suppose is a bit old now.
I've now got used to 'v'-ing the item in question to the left instead.Comment
-
Also, for the second time in a week I've had a crash when inscribing some arrows with {=g @f9}. Unfortunately I wasn't able to reproduce it last time so I didn't report it. But as it crashes so rarely, twice in a week can't be coincedence, can it?
(Mind you, last week I managed to summon 7 up stairs in a row while looking for a down stair. My personal record and odds of about 100,000 to one!)Comment
Comment