Quote:
Originally posted by Python523
sometimes if its an npc like in a level that's crashing it, if you put it up again, it will just crash again, that's why someone like stefan needs to be able to see what crashed it so he can fix it
|
then we need to be able to look at the same thing stefan looks at
if theres some log that says why it was dc'ed
what script caused the error, etc
what command exactly was sent to make it go bonkers so we can figure it out.
its becoming too much of a hassle to have to wait a day or so to get npc-server back up when theres a problem.
itd be so simple
just have it so people with npc-control can use a button to reconnect npc-server
and the button only appears when NPC-Server count==0
since that is a var on RC stats
it could be where the local npc button is, and it disappears when the npc-server is up
and there can be a button also that has NPC-Server Log
that we can see what the problem was when it was DC'ed