4.0.1 Bugs

[Estie]

They're ordered by tval (bolts, arrows, shots), then by order they appear in object.txt, then by value. If there is a different order that obviously makes better sense, that could be arranged.



One advantage is that you don't have to wield into the quiver, ammo just goes there automatically. The quiver does appear along with the equipment if there's an equipment subwindow open; aside from that, I thought it would mainly need to be accessed when firing, in which case it comes up automatically anyway.

I see that you put a lot of thought into this and I appreciate that. Unfortunately I dont think its better.

Typically, I pick up a stack of ammo to pseudo-id, but most of the time I dont want to keep it because it is inferior to what I have, so I drop it again. This used to be d-x, now its alt-| - scroll - D - confirm. Worst case, the ammo stacked with something already in the quiver and I also have to do substraction to retain 40. Having to type w-x for the few cases where I do want to keep it isnt much trouble.

At first I thought it might be me not being used to the new quiver, but it really just seems to make maintainace more cumbersome.

As for ordering, I always want some low value ammo as default, so now I have to inscribe. With the old system I would sort some low type on top to shoot runners or shrieking mushrooms (h) and pick an appropriate slay or brand for named (f-x); no inscriptions required.

[Nomad]

Typically, I pick up a stack of ammo to pseudo-id, but most of the time I dont want to keep it because it is inferior to what I have, so I drop it again. This used to be d-x, now its alt-| - scroll - D - confirm.

Can't you just use d|x? Or d[right arrow]x?

As for ordering, I always want some low value ammo as default, so now I have to inscribe. With the old system I would sort some low type on top to shoot runners or shrieking mushrooms (h) and pick an appropriate slay or brand for named (f-x); no inscriptions required.

I agree with this - I tend to want my worst ammo as the default so I can happily spam it at random weaker monsters, and the powerful stuff saved in the back of the quiver so I don't waste it until I encounter something worth using it on.

Would it be possible to reverse the value sort, so that instead of the current:

0) Arrows (1d4) {ego}
1) Arrows (1d4) {magical}
2) Arrows (1d4) {average}
3) Seeker Arrows (4d4) {ego}
4) Seeker Arrows (4d4) {magical}

You'd have:

0) Arrows (1d4) {average}
1) Arrows (1d4) {magical}
2) Arrows (1d4) {ego}
3) Seeker Arrows (4d4) {magical}
4) Seeker Arrows (4d4) {ego}

That would put your worst arrows at the front as default ammo and also make it a basic 1,2,3,4,5,6 sort by ascending ammo value, which is a bit more intuitive than 3,2,1,6,5,4.

[Estie]

Can't you just use d|x? Or d[right arrow]x?

I can but then I have to enter a count, too; the way I typed it, I get to use capital D to skip that step. Either way it is longer than before, for a procedure used more often than the one that this way is saving keypresses on - the moving of ammo from inventory to quiver.

[Nick]

I see that you put a lot of thought into this and I appreciate that.

Maybe not as much thought as you think

So, what would be a sensible default behaviour? Based on what you've said, I'm thinking along the lines of:

• Picked up ammo stays in the backpack until it pseudos
• On getting pseudo, the player is prompted for quiver slot to place it in, or d to drop

How does that sound? What do others think? Feel free to suggest your own scheme.

[MattB]

Please no! I much prefer it as it is now!

Although Nomad's adjustment would make me even happier.

[fph]

Please no! I much prefer it as it is now!

Although Nomad's adjustment would make me even happier.

I also like the quiver with its present interface, and Nomad's suggestion seems a good improvement.

Some time ago someone (I forgot who!) suggested to add the inscription =numberg, which means "pick these up until I have number of them". For instance, =40g on (+0,+0) arrows. This would fix the other issue Estie has, and it would also be handy for spellbooks and staffs.

[Estie]

Please no! I much prefer it as it is now!

Although Nomad's adjustment would make me even happier.

So what do you do with all the ammo ? Drop it from your quiver once it is identified ? Spend identify scrolls/charges on everything on the ground ? If so, why do you prefer that over just shoving the wanted stacks into the quiver ?
How exactly do you use ammo ?

I find myself not touching ammo stacks, because while they may be acidic and I´d love to use them, its much more likely that I´d have to drop them again.

[mrfy]

I agree with this - I tend to want my worst ammo as the default so I can happily spam it at random weaker monsters, and the powerful stuff saved in the back of the quiver so I don't waste it until I encounter something worth using it on.

...

That would put your worst arrows at the front as default ammo and also make it a basic 1,2,3,4,5,6 sort by ascending ammo value, which is a bit more intuitive than 3,2,1,6,5,4.

Yes! I also prefer my arrows sorted this way. I would love for this change to be made, or at least made an option.

[Elsairon]

Had 2 crashes. One was an assertion for something like find usable space happened when I was casting a stinking cloud in town. I could not reproduce it, but it crashed in some other way just after that, after I re-loaded the save and was trying to reproduce the crash.

The third re-load and the game seems to be running fine, so far.

[jevansau]

Another vote for worst to best quiver sorting. I don't mind the extra effort to select ammo for special targets, but I want h to use the worst ammo.

The only possible quibble I have is determining what is best. Often ego > good >= normal across tvals. I think my ideal would be:
no slay or brand by increasing damage
slay or brand by type by increasing damage

[Elsairon]

Gnome Mage, looking at a description of a melee weapon I see the following as one of the description inspect lines.

With +0 STR and +0 DEX you would attack a bit faster.

This seems like a needless and inaccurate description, unless I'm missing something?

[fph]

This is really minor: when you zap 2 rods of Do Something (2 charging), you get the message is "that rod is still charging". It should be "those rods are still charging", instead.

[Ingwe Ingweron]

This is really minor: when you zap 2 rods of Do Something (2 charging), you get the message is "that rod is still charging". It should be "those rods are still charging", instead.

I disagree. You are zapping only one of the rod's in a stack, not all of them at once, so the message is correct. The inventory still shows the number in the stack that are charging correctly as well.

[luneya]

I've also been crashing repeatedly, at random moments (reloading the save and doing the same stuff over doesn't reproduce the crash). I've tried running the game fresh from a reboot, with no other programs open; this gave me several hours of trouble-free gameplay, but eventually it started crashing again, without my doing anything particularly stressful. Clearly these crashes are caused by some bug in the game itself.

So, for the technical details, in case they're helpful: I'm running on OSX Yosemite, using the official 4.0.1 mac release, as downloaded from rephial.org. Attached is the dump log from the most recent crash; I didn't bother saving any previous ones, but I doubt they'd show anything more of interest. Heck, I don't know if this one is of any use at all; I'm not a programmer of any sort.

[Nick]

So, for the technical details, in case they're helpful: I'm running on OSX Yosemite, using the official 4.0.1 mac release, as downloaded from rephial.org. Attached is the dump log from the most recent crash; I didn't bother saving any previous ones, but I doubt they'd show anything more of interest. Heck, I don't know if this one is of any use at all; I'm not a programmer of any sort.

Thanks for the report and the log; it tells me that the crash was caused by the trap-triggering code. Sometimes that sort of information is enough, but not this time. If on your next crash you could give me the dump log and the savefile, that would be excellent.