Opened 12 years ago

Closed 11 years ago

#715 closed bug (fixed (in master))

Use a better algorithm for magic devices fail rate

Reported by: takkaria Owned by: magnate
Milestone: 3.1.2 beta Keywords: player


An idea might be to plot the existing rates on a graph of player level vs item level first.

Change History (8)

comment:1 Changed 12 years ago by takkaria

Oh, and display it in item descriptions too.

comment:2 Changed 11 years ago by magnate

  • Owner set to magnate
  • Status changed from new to assigned

comment:3 Changed 11 years ago by magnate

New discussion here:

My next job is to create a list of all activatable devices/effects together with their depth (which is currently their difficulty rating), assign putative difficulty ratings, and list the base device skill of each race/class combo at each clev. That should enable a fairly easy attempt at a new algorithm. I feel a spreadsheet coming on.

comment:4 Changed 11 years ago by magnate

  • Milestone changed from 3.1.1 beta to 3.1.2 beta

The spreadsheet is at, but neither of the algorithms is satisfactory. High level magi are too good, and high level warriors are not good enough - so I think this means we need a quadratic approach. Postponing to 3.1.2 as agreed with Takkaria.

comment:5 Changed 11 years ago by magnate

From #angband-dev for posterity:

(17:28:46) takkaria: I think I'd be happy capping at 1 or 2% fail instead
(20:42:37) takkaria: yeah, since AIUI, activation is basically a mechanical or thought based process
(20:42:53) Magnate: So no effect from wounds or blindness, small for poison, fear, berserk, and slightly more for stunning then confusion at the top. Ok?
(20:44:28) takkaria: yeah, I think that works

(with small positive effects from Bless and Heroism, and max fail of 95%)

comment:6 Changed 11 years ago by magnate

(in the same conversation it was agreed that confusion should increase min fail to no more than 25% - though of course this does not help with aiming)

comment:7 Changed 11 years ago by magnate

  • Keywords player added

comment:8 Changed 11 years ago by magnate

  • Resolution set to fixed
  • Status changed from assigned to closed

[fed2198] (SVN r1817)

Note: See TracTickets for help on using tickets.