this is completely intentional so that any changes in the event get picked up. otherwise i have to figure out the change between the first and second state, and that is quite difficult to do accurately. By triggering the negation and then reapplying it, then you get the same effect anyway, except i dont have to wrestle with a third set of code for each and every action. take for example what happens if you are charging per word and require at least 50 words? it needs to be able to take back the old credits and check to see if you didnt edit it to below 50 words (and if you did, to issue an error) this issue plagued vbcredits 1.x