Current master post-4.2.2

[PowerWyrm]

I just TO'd the Balrog of Moria, then summoned him on the same level using a staff of summoning.
Should that happen?
Feels weird to me...

IIRC that's a new feature. Looking at the code, the summon function now has a "call" parameter which uses a new method of summoning ("calls out" a monster that is present on the level) and this parameter is set to "true" 25% of the time randomly.

[PowerWyrm]

If you try to use the "l"ook command when using 16x16 tile size and you end up with a panel of size 0, the command will also loop endlessly.

[PowerWyrm]

Using this code everywhere panel dimensions (in particular "screen_wid / 2" occurences) are used fixes the problem:

int screen_hgt, screen_wid;
    int panel_wid, panel_hgt;

    screen_hgt = p->screen_rows / p->tile_hgt;
    screen_wid = p->screen_cols / p->tile_wid;

    panel_wid = screen_wid / 2;
    panel_hgt = screen_hgt / 2;

    /* Paranoia */
    if (panel_wid < 1) panel_wid = 1;
    if (panel_hgt < 1) panel_hgt = 1;

The only remaining issue with this is that the @ isn't visible if panel_hgt = 1 (it's displayed one line below).

[MattB]

IIRC that's a new feature. Looking at the code, the summon function now has a "call" parameter which uses a new method of summoning ("calls out" a monster that is present on the level) and this parameter is set to "true" 25% of the time randomly.

Oh. Fair enough then.
That might call an end to my traditional level-ending of standing on the stairs with a staff of summoning trying to call up some cheap low-level uniques.

[Nick]

IIRC that's a new feature. Looking at the code, the summon function now has a "call" parameter which uses a new method of summoning ("calls out" a monster that is present on the level) and this parameter is set to "true" 25% of the time randomly.

Neat, I forgot I did that

[PowerWyrm]

Neat, I forgot I did that

You didn't, Fizzix did

[Nick]

You didn't, Fizzix did

Well, fizzix did all the work of designing the new method, but I made the tiny change that made it actually appear in the game...

[will_asher]

I just noticed that in the description of arrows it says "35% chance of breaking on impact" but IIRC, the code has a chance of the arrows breaking even if they don't hit anything. Which is it supposed to be? on impact or on firing?

[fph]

Walls are harder than orcs, so they break arrows, too.

[will_asher]

Walls are harder than orcs, so they break arrows, too.

But if it runs out of range and lands on the floor it shouldn't break.

[MattB]

The floor is also harder than most orcs ;-)

[whartung]

The floor is also harder than most orcs ;-)

But the tangential energies of floor impact combined with the integral flex ratios of the arrow material should greatly reduce breakage.

No doubt there should be some friction model based on the floor space tile type to better model the drag coefficient of the arrow (no doubt related to the fletching material, you know, in for a penny and all) to better place the arrow down the hall as it goes sliding after contact.

I leave it as an exercise for others to discern whether there should be any skipping.

[Nick]

But the tangential energies of floor impact combined with the integral flex ratios of the arrow material should greatly reduce breakage.

No doubt there should be some friction model based on the floor space tile type to better model the drag coefficient of the arrow (no doubt related to the fletching material, you know, in for a penny and all) to better place the arrow down the hall as it goes sliding after contact.

I leave it as an exercise for others to discern whether there should be any skipping.

This is a dungeon, it doesn't have a nice smooth floor. It's uneven and rocky, plus there's stuff like rodent skeletons and shards of pottery lying around that players don't notice any more, but that an arrow can break on.

[MattB]

there's stuff like rodent skeletons and shards of pottery lying around that players don't notice any more

or a palantir

[Nick]

or a palantir

Well played, sir