V 3.5 now in feature freeze

[PowerWyrm]

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!)

The crash has already been reported. Myself, I've never been able to reproduce that.

Concerning stair creation, the RNG is known to be seriously biased (same problem with teleport: when you use teleport twice, you almost always end up very close to where you were). When you create stairs deep in the dungeon, it's really common to generate 7-8 consecutive up stairs. That's why for my variant I added a little bit of code to ensure you'll never get more than 5 consecutive up or down staircases (and also ensure that double teleport will never bring you back on the same spot).

[Timo Pietilä]

I guess I never noticed that effect! It's funny what you notice when you're actuvely looking for bugs.

It's new. I didn't know that either, and old versions definitely used light even when you didn't need it if you had lightsource equipped. I have no idea when that was changed.

[Nomad]

Okay, here's another tiny fix for an error in the room_template.txt file. (Maze layout that you can't actually get all the way around. Oops.)

[MattB]

2^7 is only 128, so it's not that unlikely.

Sorry, maths crash!
I powered up the fail rate instead (as that's normally the relevant stat in a long chain of undesirable outcomes). I'm so ashamed.

As for torches, the game is just not penalizing you for taking your light source off when there's no need for it. You'll still use up turns if it's night time.

I guess I never noticed that effect! It's funny what you notice when you're actuvely looking for bugs.

[MattB]

Hm, thanks. Is this with a 'display inven/equip' term window?

yes it is. But the action was done by pressing <{> first (rather than <e>, <n>, <{>).

[With apologies for the punctuation train crash!].

[MattB]

In the day? It's because the sun is up.

Well then, that's OK then!

[takkaria]

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!)

Hm, thanks. Is this with a 'display inven/equip' term window?

[Derakon]

2^7 is only 128, so it's not that unlikely.

As for torches, the game is just not penalizing you for taking your light source off when there's no need for it. You'll still use up turns if it's night time.

[takkaria]

By the way, is there a reason why the light counter on a torch doesn't decrease when you're in town? Jus' wonderin'.

In the day? It's because the sun is up.

[MattB]

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!)

[MattB]

By the way, is there a reason why the light counter on a torch doesn't decrease when you're in town? Jus' wonderin'.

[MattB]

I can still drop things from the object context menu. Can you reproduce this still at your end?

I still cannot drop anything from within the 'i' or 'e' menus.
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.

[Ingwe Ingweron]

I can still drop things from the object context menu. Can you reproduce this still at your end?

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.

[takkaria]

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.

I can still drop things from the object context menu. Can you reproduce this still at your end?

[takkaria]

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.

Oh, thanks for reporting that. I did check that it worked but that was before adding numbers to the list display.

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'?

You'd have to use !D.