Connecting

From Seltanikor
Jump to: navigation, search

This page is a guide to getting set up to play Seltani.

Please be aware that Seltani is currently in beta. Many features are not yet implemented. If you manage to find bugs, please report them to Belford rather than exploiting them.

You will need:

  • About two minutes.
  • An email address.
  • A browser that supports cookies, Javascript, and websockets. (Safari 6, Firefox 11, Chrome 14, IE 10)

To get started, go to http://seltani.net/. (You may wish to do this in a separate tab, so that you can refer back to this page.)

Click “Register new account”. This will take you to a registration page with four fields: Avatar Name, Email, Password, Password again.

  • For Avatar Name, choose something that looks like a name. This will be used to refer to you in generated text such as “Yourname arrives.” or “Yourname crosses the bridge.”, so consider calling yourself e.g. “Ri'neref” rather than “rineref625”.
  • Email should be a real email address, so that password recovery emails can be sent there.
  • Password should be something easy to remember and hard to guess. Never use the same password on different sites.
  • Password again: retype the same password as above.

Click “Register”, and you'll automatically be logged in.

At this point, you should find yourself at an “Information Booth”. The directions in-game will guide you through the first steps of how to play.

Troubleshooting

If you are able to register, but see this error upon connecting:

   The connection to the server could not be opened.

...then either your browser is out of date, or your Internet service is set up to use a web proxy which does not handle websockets. (Privoxy is a web proxy which is known to have websocket problems.)

Try this alternate address: https://seltani.net/ The HTTPS protocol should bypass proxies.

Seltani’s SSL certificate causes Firefox to cough up a warning about “unknown issuer”. I'm using a free cert service, and I guess Firefox isn't entirely happy about that. It works if you accept the cert (add an exception about it in the warning dialog). Chrome and Safari don't complain.

If you're not sure whether your browser supports websockets, try this test service: http://www.websocket.org/echo.html (Test both normal and secure (TLS) mode.)