When I take some actions using this awesome script, the ModLogActivities hack won't log them. If I use the standard procedure (using vB standard actions) to delete, close threads actions DO get logged by ModLog hack.
I haven't had the chance to take a look at the code Mas*Mind, and I wondered if you simply call vB functions or does the hack actually make the modifications itself (that would explain why ModLog hack doesn't "trap" the actions).
Thanks for you're work Mas*Mind, you made a great hack!
...Axel