Adrodoc

There is an argument to be made for `spell.broken` not to be read-only to allow easy programmatic breaking of spells. Of course you should not be able to resurrect spells....

The read-only aspect of this request is covered by [`Spell.alive`](https://www.wizards-of-lua.net/modules/VirtualEntity#alive).

For spells I prefer the name `broken` (or `active`) over `alive`, because spells are usually not considered to be living. @mkarneim Do you think we should add `Spell.broken` or `Spell.active`...

the allowance should definately be readonly, but it makes sence to allow users to set the tick limit, which is currently not accessable in Lua. Didn't you also want to...

@mkarneim what do you think about this

We also need to think about the EventsModule and SystemModule, because currently these cause the declaring spell to pause, not the calling spell.

I just took another look at this (in the 1.13 branch), but I just can't figure it out. Somehow this seems to depend on when during a tick the teleport...

See also #244.

I dislike the fact that the function returns two values. From the function name I would expect a single return value. I suggest to split it into: 1. `boolean =...

> > > > If we go this route we can also omit the first function, as it is equivalent to checking whether the second function returns a non-nil value....