Opened 14 years ago

Closed 8 years ago

#57 closed change (wontfix)

Do spells with edit files (like UnAngband)

Reported by: pmac Owned by:
Milestone: Future Keywords: cleanup backport

Description (last modified by takkaria)

There are a small number of genuinely diffent spell types. It would be nice to have edit files like UnAngband? to specify spell levels, fail rates, and action. The current model (spells in p_class.txt in a mysterious order) makes it incredibly hard to add new spells.

process_spell_blows &c, with some modification to allow parse of damage, is the critical component, though some cleanup (making more tables) is needed.

Change History (11)

comment:1 Changed 14 years ago by pmac

  • Milestone set to Future

comment:2 Changed 14 years ago by takkaria

  • Type changed from bug to feature

comment:3 Changed 14 years ago by pmac

I'd like to see this get scheduled for the next engine/gameplay release (3.1.0?). The spell and object code is seriously flaky, especially now that Lua is out.

comment:4 Changed 14 years ago by pmac

(From tak's email)
I would much rather have objects reference spells than I would have spells reference objects as they do now. Otherwise, the lists of numbers are pretty much meaningless to the casual observer.

Also use by-name rather than by-ID links if possible.

comment:5 Changed 14 years ago by takkaria

I think the payoff here is huge-- especially for mouse users. For example, if all items that provide identify can be programatically listed, then you could click on an un-ID'd item in the inventory and have "Identify" as an option.

comment:6 Changed 13 years ago by takkaria

  • component changed from Port-specific to Main game
  • Description modified (diff)

comment:7 Changed 13 years ago by takkaria

  • Milestone changed from Future to 3.0.9

comment:8 Changed 13 years ago by takkaria

  • Milestone changed from 3.0.9 to Future

I think that if the spells are moved to the effects.c framework, then that will do for 3.0.9. So, moving to "Future" again, for now.

comment:9 Changed 13 years ago by takkaria

  • Keywords port removed

comment:10 Changed 11 years ago by magnate

  • Keywords cleanup backport added

comment:11 Changed 8 years ago by takkaria

  • Description modified (diff)
  • Resolution set to wontfix
  • Status changed from new to closed

I don't think this level of customisation is a great idea anymore unless you have a full-blown scripting language. So closing as wontfix.

Note: See TracTickets for help on using tickets.