vrt: Email sent. Very grateful
LITHE: if mutant psions' spelldamage is OP, code can be written so that preexisting psion status is removed when transforming. But yes, that change is implied so I've removed noting it in an attempt to keep the list of differences concise
On changing the code to emulate original behavior: I've modified the active system to support multiple actives (still not perfect, can't have multiple actives of the same kind). While this is useful in defining cards, it conflicts with alternate uses of active changing cards being lobo methods
Fixing this isn't impossible: when changing an active, instead of saying "c.active.cast = Actives.destroy" in BE, I'd say "c.active = {cast: Actives.destroy}" but it raises the question of whether the lobo'ing is really necessary for _all_ active overriding spells. Any opinions would be appreciated. To note: Devourer's passive is now an active alongside burrow, so Butterpest would no longer work if BE didn't only overwrite burrow
I personally think stuff like Butterpest is neat, thus that more card synergies like that would be good, and that lobo'ing should be explicit. I've read complaints that active overriding spells were downsizing aether's lobotomize (inb4 aether hate). Still, if there's any active replacements which feel like they should explicitly lobo, do mention
edit active chaining implemented. So "c.active.hit = Actives.vampire" is now "c.addactive('hit', Actives.vampire)" & doesn't lobo scorpions