Correct. I've seen this happen before ... but that was a host error...The host stopped the writing because it was eating too much bandwidth and so only player data stopped xD
We had something like this happen before with Logblock, it wasn't saving logs, after clearing the tables, it fixed it.
You wouldn't have any idea anyway.... Only sk or another admin with console access could find out what's going on...
ALRIGHT... We get the point. I can kinda guess what had gone wrong. I was on last night when there was a scheduled server restart and I tried to join in after the server restart and the server held my connection (for some weird reason it didn't timeout so I had to cancel it) and the server wouldn't respond to any requests afterwards. So perhaps some persistent thing that is loaded on server start had screwed up. LB has a max table rows setting for a good reason. Some SQL systems (mySQL is prob the only thing LB supports) have max table sizes which some hosts can impose to reduce database sizes.
maybe, just maybe, this will reset my position so I can join without dying... I wouldnt even care if I lost mah TC research anyway, as I gave up on TC. and I would know what to put in and all. EDIT:fixed the most ridonculous mistake ever...
