I recently developed a chip that reads the users Worldedit selection when activated and saves it.
It saves this selection as state data so that it has it when the server is restarted.
I have not tried it, but I suspect that if this chip gets reset via rcreset it will fail because it will look for the current Worldedit selection and there will not be one since it doesn't retain it's state data on a reset (by design i know).
It may be nice to allow chips to specify specific state data that needs to be retained across a reset to handle these cases where the requirements to re-activate the chip may not be met because information that was available when the chip initially activated is no longer available.
I recently developed a chip that reads the users Worldedit selection when activated and saves it.
It saves this selection as state data so that it has it when the server is restarted.
I have not tried it, but I suspect that if this chip gets reset via rcreset it will fail because it will look for the current Worldedit selection and there will not be one since it doesn't retain it's state data on a reset (by design i know).
It may be nice to allow chips to specify specific state data that needs to be retained across a reset to handle these cases where the requirements to re-activate the chip may not be met because information that was available when the chip initially activated is no longer available.