@jgm
Jetkar mentions a curious 'side-effect' with EDDI that I too have noticed that I've not mentioned previously because I needed to carry out a few more tests with it, but at the time there were more important issues to figure out so had'nt gone further with this.
Here's what I believe is happening with EDDI. When EDDI is interupted, such as going into EDIT MODE of Voice Attack then the ((Event Loop)) stops processing the events stored by your netlog monitor, which are still being stored. As the player jumps into different systems these stored events build up. When the player does restart EDDI properly either via closing VA and restarting it or, via reloading the EDDI profile what happens is that we still have those stored events in que waiting to be processed.
Yes, it's possible for the event loop to stop working but that won't stop the events from stacking up. The real solution here is for the event to automatically restart when it is stopped, which is something I'm talking to VoiceAttack support about. If I don't have any luck with this I'll find a way around it, but would rather not as throw away valid events if possible.