Forums Scripts & Popups Strange behavior dll files

it's triggering on the first command because the first command LOADS the dll (it then stays active in memory), which is where those debugging messages come from. I'm not sure why you still don't understand this.