Hey guys, its me again. I know Moustachauve has already informed Tyrsis of the log issue we are having. In case you other guys want to see what the issue was, here's a pastebin of our log: http://pastebin.com/SBT60JNv . In the process of trying to get our plugin to load, we deleted the log our plugin uses, which still resulted in the same error.
We finally got our plugin to load by wiping out all .dll's it needs to run, removing it from the mods folder, deleting all our logs, running SESE clean, then reinstalling our plugin and starting SESE again.
Now for the issue, after doing all of that, I tried to disable our plugin to put our config into effect. I tried "reload" first, which did not register our new config. I clicked "Disable" second, and it completely locked up SESE. I gave it a good 20 minutes before forcing the console closed. When I forced it closed (Ctrl+C on the command prompt), SESE promptly died, then spawned 23 instances of itself, all of which tried loading at once... I am not using autorestart, nor do I have any custom watchdogs watching the process.
UPDATE - You can cancel this. Turns out the http library we are using ended up with a stuck service when we shut our devel server down for updates. I apologize for the late night/early morning email spam. Thank you for the update and keep up the good work.
Hey guys, its me again. I know Moustachauve has already informed Tyrsis of the log issue we are having. In case you other guys want to see what the issue was, here's a pastebin of our log: http://pastebin.com/SBT60JNv . In the process of trying to get our plugin to load, we deleted the log our plugin uses, which still resulted in the same error.
We finally got our plugin to load by wiping out all .dll's it needs to run, removing it from the mods folder, deleting all our logs, running SESE clean, then reinstalling our plugin and starting SESE again.
Now for the issue, after doing all of that, I tried to disable our plugin to put our config into effect. I tried "reload" first, which did not register our new config. I clicked "Disable" second, and it completely locked up SESE. I gave it a good 20 minutes before forcing the console closed. When I forced it closed (Ctrl+C on the command prompt), SESE promptly died, then spawned 23 instances of itself, all of which tried loading at once... I am not using autorestart, nor do I have any custom watchdogs watching the process.
UPDATE - You can cancel this. Turns out the http library we are using ended up with a stuck service when we shut our devel server down for updates. I apologize for the late night/early morning email spam. Thank you for the update and keep up the good work.