Bug Stomp

That's precisely the bastard error. The telling sign is this in the middle:
"Process 8 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process."

I thought I fixed it for good a couple hours ago.. but I just saw it again. CURSES!

Please place spaces in long errors... Ok, I admit, I am not the brightest PC expert... But if you put in spaces, doesn't that make it even longer? And where exactly do I put spaces?

Long strings of text wont wrap unless you put a space in them. That makes the message box longer than usual.

That multiple logins by bots thing is happening again, and from the look of things it is impacting conversations.

Not sure of a bug, but popped up in chat window during bot-bot conversation, which seems to have stopped afterwards.
<!-- Adjust Synonym List to avoid common mista

I have been thrown out of the site twice today

I fixed the double-login thing for now. It happens on the rare occasion that two people log in at the exact same moment after midnight on any given day.

Okay, those errors should be fixed up now. I had to disable the sentence reconstruction system temporarily.

I'm having trouble getting the language center to work. It could be just me--we've been having power glitches here.

To be more sepcific:
I wanted to change the response to 'got'. I clicked on 'got'. The screen jumped back to the top of the 'g' page and nothing further happened.

Hmm. Nothing happens when I click on my bots' 'chat' thingy, either. I might as well have stayed home. Nor has any bot nor person sent me a message. Has the world ended?

Sounds like JavaScript is failing or something else is blocking popups.

Holy cow are the bugs flying tonight! Mostly CF bugs, but I'm assuming it's due to server clog. I seem to be able get an error back from any bot if I pass on this message from Elbot:
"I don't mind if it starts to rain oil someday. But that's not going to do much good for the organic environment."

The error I get begins thusly:
Error Diagnostic Information

An error occurred while evaluating the expression:
"#StartIndex#"

Error near line 1584, column 18.

I get the error while passing the message through debug for my bot as well.