Add a “magic forge” which is like a magic fountain but with forges. It can generate wherever forges generate randomly. Dipping a nonartifact metal weapon in it always grants it 1 random object property, and then the forge either becomes nonmagic or disappears.

In variants where gods give non-artifact gifts for sacrifices: There should be some sort of scale, or defined thresholds, of the various object properties, materials, and minimum enchantments available from a non-artifact gift. The idea is that having them be completely random is too swingy and incentivizes early altar farming (if you can get an amazing property/material/both off a newt sacrifice as easily as a minotaur, why not just sacrifice all the newts you can?) and allows for possibly early-game-breaking gifts.

It’s not specified what exactly the scale should be based on - your own experience level, the monster difficulty of the sacrifice, the level difficulty or depth of the altar, or something else.

If you use Ogresmasher as your hammer at a forge, the resulting forged object should have a small chance of being imbued with an object property.

The potion of wonder gives both a positive and negative intrinsic when quaffed, and both a positive and negative object property when something is dipped into it.

Food can have object properties which convey some special magical effect that it normally doesn’t. For example, a “food ration of fire” is spicy chili flavored and confers fire resistance for a few hundred turns.

If enlightenment tells you something like “You have [intrinsic] from your [piece of gear you didn’t know the property of], that object property becomes identified on that piece of gear.

Saddles can have object properties that apply to the animal wearing the saddle.

The Soul Forge: a single-level branch off Gehennom that contains a smith. The smith will take two items of the same type and forge them together into one; in technical terms this destroys one of them and imbues the other with whatever object properties the destroyed one had. They cannot both be artifacts, and if one is an artifact, it will not be the one destroyed, so the properties from the other one will be transferred to the artifact.

The smith’s price is based on how many object properties the resulting item will have, increased if it will be an artifact. In dNetHack, the smith would require payment in soul coins, but in variants without those, they may just ask for gold or some other valuable. If paid in soul coins, the requested type of coin would be random but deterministic based on the object IDs of the two items.

Attacking a dead tree with a weapon of fire, or an artifact with fire damage, will burn up the tree.

An object property “of rust”, applicable to weapons, which causes its target’s gear to rust and, eventually, get destroyed.

Shop-owned items with positive enchantment (but not negative) have the enchantment identified, since the shopkeeper is, after all, trying to get you to buy them.

In variants with object properties, items with beneficial properties should also come identified in shops for the same reason.

Dipping ammo in various potions can endow it with a permanent object property related to the potion.

Applying an athame to an item with an object property magically severs the property, which then “falls” and attaches to the topmost eligible item on the floor beneath it.

Artificer role themed around turning items into different or differently powered items.

• They are intended to play similarly to a Healer, with alternate ways of surviving due to having personally low offense. However, their magic doesn’t focus on healing.
• Add a new spell school, “artifice spells”, with the following spells:
  • Transmute: Change the material of an object.
  • Imbue: Consume a wand and endow a different item with an object property related to that wand.
  • Enscribe: As above, but consume a scroll.
  • Reforge: As above, but consume a magical piece of wearable gear.
  • Elute: Consume a magical piece of wearable gear and produce a potion with a related effect.
• Can get up to Expert in artifice spells, Skilled in matter spells, Basic in enchantment spells. Other skill caps are unspecified.

A system termed “named non-artifact properties”. They are unique properties that never generate on more than one item per game, and confer some artifact-like qualities, but are not tied to a specific type of object, and can generate on multiple types of base item. This type of property cannot be wished for, even if properties can otherwise be wished for.

A couple examples:

• Any random ring could generate with a property that causes it to be named “Serpent’s Bite” and gives you a minor poison attack when hitting something with bare hands and the ring equipped.
• A few different types of fruit could generate with a property that causes it to be named “from Eris’s garden” and cause aggravate monster when carried.

“Unstealable” object property, which makes an item with that property incapable of being stolen.

Object properties, one per spell school, which each give you a casting boost in their spell school when the item is equipped (it only generates on equippable items). Should be rare compared to other object properties, and unwishable.

Items that generate with an object property should be eligible for the chance of generating with a name even if they’re only +0.

Add levitation as an object property, so that you can have weapons and equipment that makes you levitate while it’s equipped.

Armor can no longer be enchanted with a +/- number that affects AC. It always behaves as +0 with regard to AC. Instead, using a scroll of enchant armor on it gives it a random object property. A blessed scroll gives a good property, a cursed scroll a bad one, and an uncursed scroll any possible one (possibly including situational, double-edged properties that are not available as either “good” or “bad”).

For variants with object properties, store a bitfield as the property mask in the objclass struct, and a separate one in the obj struct. This lets you define which properties are inherent to the object type (e.g. acid resistance and poison resistance for an alchemy smock) and which abnormal properties it has, which is useful because all alchemy smocks shouldn’t show up as “alchemy smock of poison resistance and acid resistance”.

A small fraction of wearable items are generated with a “trendy” property, which is pre-identified and not hidden from the player. Trendy items have an increased base price and add one charisma when worn.

Object property “curing”: allows the item to be used like a unicorn horn to cure ailments.

“Piercing” object property, eligible on ammunition, which makes them not stop flying or break when they hit a monster, continuing on to possibly hit more monsters behind it.

“Homing” object property, which generates on ammo and guarantees a hit.

Thirsty weapons sometimes gain a point of enchantment when they drain a level from something. Probably only up to a certain maximum.

New object property “sacrificial”. When something bad happens to you (any one bad effect, really), if you have a sacrificial object equipped, the object disintegrates and the effect is nullified.

Armor of lifesaving. Works as expected, saves your life but disintegrates in the process; more interesting than an amulet because it leaves you more vulnerable after disintegrating. This could possibly be an (extremely rare) object property.

New object property “identification”. Generates on containers, and type-identifies any item put into it.

Object properties are more likely to appear on poorer weapons and armor.

New object property, burden. Makes the item heavier than it is normally. Objects with this property generate cursed 90% of the time.

You should be able to wish for object properties in FIQHack, but only on items whose base types aren’t inherently magical.

Greed, a new object property for containers: the container will refuse to open 80% of the time, costing a turn. Either any gold put into the container vanishes permanently or gold weighs nothing when in the container.