Existing players used to logging in with their character name and moo password must signup for a website account.
- cata 40s
- QueenZombean 1m Singing the song that doesn't end, yes it goes...
- Hippo 1m
- Raven 3m I lost myself, in the dark charade.
- Sivartas 13m
- Fogchild1 4m
- Rillem 42s Make it personal.
c Logic 15m
- Dale 24s
- Acupa 2m
- SmokePotion 12s Right or wrong, I'm getting high.
- BubbleKangaroo 1h
- zxq 3m Blackcastle was no ordinary prison.
- NightHollow 50m
- Vanashis 5h
a Mench 2h Doing a bit of everything.
And 28 more hiding and/or disguised
Connect to Sindome @ moo.sindome.org:5555 or just Play Now

I Haz Errorz!
Can someone explain to me what this emans?

So, the client just fucked up and disconnected me. I click on "Reconnect Now" But it takes forever for anything to happen. So, out of impatience, I close the window and try to re-connect.

That's when this comes up on my screen:

"Error: EMFILE, too many open files '/Users/sindome/Servers/dome-client.js/views/connect-as.ejs'

at Object.fs.openSync (fs.js:439:18)

at Object.fs.readFileSync (fs.js:290:15)

at Object.exports.renderFile (/Users/sindome/Servers/dome-client.js/node_modules/ejs-locals/node_modules/ejs/lib/ejs.js:273:12)

at View.module.exports [as engine] (/Users/sindome/Servers/dome-client.js/node_modules/ejs-locals/index.js:86:7)

at View.render (/Users/sindome/Servers/dome-client.js/node_modules/express/lib/view.js:75:8)

at Function.app.render (/Users/sindome/Servers/dome-client.js/node_modules/express/lib/application.js:503:10)

at ServerResponse.res.render (/Users/sindome/Servers/dome-client.js/node_modules/express/lib/response.js:718:7)

at ServerResponse.cls_wrapRender [as render] (/Users/sindome/Servers/dome-client.js/node_modules/newrelic/lib/instrumentation/express.js:165:21)

at exports.connect (/Users/sindome/Servers/dome-client.js/routes/screens.js:9:9)

at callbacks (/Users/sindome/Servers/dome-client.js/node_modules/express/lib/router/index.js:162:11)"

So, anyone care to tell me what all this fancy language means?

I can't say. The same has just happened to me tho.
Thats why we restarted the webclient. :)