| … | |
… | |
| 62 | /* Definition for WILL_APPLY values. Replaces having harcoded values |
62 | /* Definition for WILL_APPLY values. Replaces having harcoded values |
| 63 | * sprinkled in the code. Note that some of these also replace fields |
63 | * sprinkled in the code. Note that some of these also replace fields |
| 64 | * that were in the can_apply area. What is the point of having both |
64 | * that were in the can_apply area. What is the point of having both |
| 65 | * can_apply and will_apply? |
65 | * can_apply and will_apply? |
| 66 | */ |
66 | */ |
| 67 | #define WILL_APPLY_HANDLE 0x1 |
67 | #define WILL_APPLY_HANDLE 0x01 |
| 68 | #define WILL_APPLY_TREASURE 0x2 |
68 | #define WILL_APPLY_TREASURE 0x02 |
| 69 | #define WILL_APPLY_EARTHWALL 0x4 |
69 | #define WILL_APPLY_EARTHWALL 0x04 |
| 70 | #define WILL_APPLY_DOOR 0x8 |
70 | #define WILL_APPLY_DOOR 0x08 |
| 71 | #define WILL_APPLY_FOOD 0x10 |
71 | #define WILL_APPLY_FOOD 0x10 |
| 72 | |
72 | |
| 73 | |
73 | |
| 74 | /* However, if you're keeping a pointer of some sort, you probably |
74 | /* However, if you're keeping a pointer of some sort, you probably |
| 75 | * don't just want it copied, so you'll need to add to common/object.C, |
75 | * don't just want it copied, so you'll need to add to common/object.C, |
