If you set an event to inactive e.g. semaphore event, then start MIS2, then run mystic -cfg and make the event active again.... MIS2 will not rescan the config data to pick up the change.
Yes, that is intentional. There will be a CTRL-R to manually restart
the event system when on its tab, and an option to automatically detect changes and reload them.
Or if I don't like how that works I'll just make it automatic without an option for similar to how MIS works. The difference between the two
event systems means that when you "refresh" the event data, you'll lose any "pending" events that you currently have, as the entire system will
be refreshed. MIS1 didn't have pending events, they were just lost if they landed while another event was going.
Sysop: | sneaky |
---|---|
Location: | Ashburton,NZ |
Users: | 2 |
Nodes: | 8 (0 / 8) |
Uptime: | 92:06:14 |
Calls: | 2,122 |
Calls today: | 3 |
Files: | 11,149 |
D/L today: |
48 files (22,099K bytes) |
Messages: | 950,672 |