Determining which scripts are using the most time for processing via hooking...

[mikeggh]

Brief summary of issue / Description of requested feature:

I have created a script to help find portions of Mudlet aliases, triggers, or scripts that are using extensive CPU usage measured in time.

Steps to reproduce the issue / Reasons for adding feature:

1. https://gist.github.com/mikeggh/ae5bb83e435c2e251bcbc395fe7e4c4b
2. Drop that script into a new script in 'Scripts.'
3. Save it, and a window should pop up.
4. Click hook.
5. Do various mudlet activities on your game.
6. Click results, and see which scripts are using the most time.

Error output / Expected result of feature

This is something I had designed to find a problem for someone on their mudlet, and I thought the mudlet team may be interested.

Extra information, such as the Mudlet version, operating system and ideas for how to solve / implement:

It uses internal mudlet hooks, all are legal mudlet language operations, and doesn't require extensive frameworks on top. It could be a little buggy. I was unsure if it would ever be of use outside of my own needs. If there is a need to tidy it up then let me know.

[mikeggh]

This is an example of it functioning...

[ZookaOnGit]

I have added this script to the wiki