#49 closed change (fixed (in master))
Fix object pricing
| Reported by: | takkaria | Owned by: | |
|---|---|---|---|
| Milestone: | 3.1.1 beta | Keywords: | items |
| Cc: |
Description
Current info: http://ajps.mine.nu/angband/wiki/ObjectPricing.
It might be an idea to use the new randart code to calculate prices, see #48.
Change History (10)
comment:1 Changed 14 years ago by takkaria
- Summary changed from Fix level feelings to Fix object pricing
comment:2 Changed 14 years ago by takkaria
- Milestone changed from Future to 3.1.1
comment:3 Changed 13 years ago by andrewdoull
comment:4 Changed 13 years ago by takkaria
- component changed from Project admin to Cleanup
comment:6 Changed 13 years ago by takkaria
- Milestone set to Future
comment:7 Changed 13 years ago by takkaria
- Milestone changed from Future to 3.1.1
comment:8 Changed 13 years ago by takkaria
- Keywords tmj added
comment:9 Changed 12 years ago by takkaria
- Milestone changed from 3.1.1 beta to 3.2.0
comment:10 Changed 11 years ago by magnate
- Resolution set to fixed
- Status changed from new to closed
[19267ef] (SVN r1398) (for wearables and ammo; takkaria says no to extending it to consumables and devices for the time being)
comment:11 Changed 11 years ago by magnate
- Keywords items added; tmj removed
- Milestone changed from 3.2.0 to 3.1.1 beta
Note: See
TracTickets for help on using
tickets.
Unangband does this already, using an object_power() function to feed into the object_value() function.
I have duplicated object_power() and the randart.c power calculations for the moment, but there's a lot of common code here (basically the same routine re-written).