the defaultProjector created by setDefaultProjector in data/damage_types.lua can't handle tables being sent for its "dam" argument.
Note: a previous version of this post was more about me being grumpy than about a bug. I apologize.
defaultProjector can't handle dam tables
Moderator: Moderator
Re: defaultProjector can't handle dam tables
An alternate way of phrasing this is that not all damage types strip damage out of the table before sending it to the default projector. Darkness is one example of a damage type that does this.
This works in default Tome, but prevents creating talents or objects that don't know what kind of damage type they're going to do. Some damage types need a table (or, for all practical purposes, need a table); some damage types will break defaultProjector when sent a table.
This works in default Tome, but prevents creating talents or objects that don't know what kind of damage type they're going to do. Some damage types need a table (or, for all practical purposes, need a table); some damage types will break defaultProjector when sent a table.