Reset Password
Existing players used to logging in with their character name and moo password must signup for a website account.
- elaborate 2m
- Dashiva 28s
- Fire 1m https://i.imgur.com/CF2ywFy.jpg
- rogue_moravec 1m
- FairyBlue 12s
- NovaQuinn 1m
- Baron17 8m
- Vivvykins 1m
- Coris5271 2m
- Rangerkrauser 19s youtu.be/FTb97wTsK9g
- jdgmntday 22s
- Brotox 59m
- floored 1h
- Jackserious 2h
- Zweig_Arvel 39s
- Cainite313 13m https://www.youtube.com/watch?v=rtbct2jzLBU&feature=share
- BlazingCoconut 29s
- Warlord203 19s
- Supermarket 12m Chute her! Chute heeeer!
- HolyChrome 4m youtu.be/l8NHebm4nTY
- pfh 5h
j Johnny 3m New Code Written Nightly. Not a GM.
- Varolokkur 1m
- Dani 0s
And 22 more hiding and/or disguised
Connect to Sindome @ moo.sindome.org:5555 or just Play Now

Stuck on Char Gen

I am going through my Char Gen after a long time away from Sindome, and whenever I have to put a description in, it freezes and stops working. Any ideas what I am doing wrong or what I need to do differently?

Thanks in advance :)

Its fine. I was being a newbie and not reading properly.

Thanks :)

To anyone else who experiences this and maybe finds this while looking for help on it, here's what's going on:

When you start the description process, the MOO takes your lines of input one after another and does not echo anything back to you until you're done. It won't look like anything's happening when all you're doing is writing lines of description. When you're finished, enter a single line with nothing but a dot . (period) on it and hit Enter again, this will make the MOO stop taking any more input to your description and return you to regular command-entry mode.

There are other places in the game where the same convention is used, where the MOO expects multiple lines of entry (a line is typing words until you hit the "enter" key, a "line" does not mean typing till you reach the side of the screen and see your words wrap) and then expects a single dot on a line to signal the end of your text input, so, it's good to get used to this early in your career. Entering @history is probably the next place where you're likely to encounter this.

That was what I was doing wrong. I completely misread the help advice after the describe section. It took me a while, but I remembered having the same problem last time and my bad memory recalled what I did wrong last time as well, luckily.