I tried to make them the lowest possible, but there are still a few prerequisites about your browser:

• It must support frames and Javascript, and Javascript must be enabled in it.
• For the periodic refresh method (see paragraph 2 and 3), it must honour the <meta http-equiv="refresh" ... > tag (case of nearly all browsers).
• The size of the browser window should be at least of 800x600 or you might find it difficult to read the output screen; the interface was optimized for a 1024x768 screen.
• It is also better to use a browser with CSS and streaming support, though this is not a requirement.

The web interface does not make any use of cookies, popup windows or other invasive and annoying "features". It does not use Java either (but a Java MUCK client applet is also available on the main page to connect to Voregotten Realm).

The interface was so far tested successfully with Firefox v0.8 to v3.0 (see the FAQ below about Firefox' configuration, please), Internet Exploder v6, Netscape v7.1 and v4.7 (CSS does not work properly in v4.7 so it does not render the ANSI attributes); please tell me if you are using another browser/version and whether the interface works or not with it, thanks in advance !

Here is the link for the login screen (bookmark it...): Voregotten Realm MUCK - Web access. Enter your character name (or for a guest access enter nothing, or "guest") and your password (none needed for guests), then press the "Login" button (or the ENTER key). After a few seconds you should be presented with the chat window containing the output frame at the top and the input frame at the bottom.
Note that before pressing the "Login" button, you might also want to change the "Screen refresh type": by default, it presents you with what it believes is appropriate for your browser (as not all browsers support streaming), but it can't hurt to try... Streaming would be the preferred method, as it provides for near real-time refreshes (2 seconds or so): Firefox and Internet Exploder 6 do accept this method, but Mozilla and Netscape might as well (depending on their version).

Unless you are a guest, you will be teleported automatically into the Voregotten Park, which is a sort of multi-room vore chat (all rooms are public, they are themed, and adult-play is allowed in them unlike the other public areas of the MUCK). It is of course possible to leave the Park: just type bro to go to the Forest of Broceliande (meeting/socializing area), or use any MUCK command (tport, gohome, etc...) as you see fit. Guests will be allowed to visit the MUCK, but can't enter the Park (this is because their age can't be verified).

It is refreshed automatically whenever needed (i.e. when something is posted or happens in the room where your character is), and a check for this need is made every 5 seconds in periodic refresh mode (i.e. you will see any new message/action at worst 10 seconds after it was issued, loading time included, unless you got a very very slow connection), or in near real-time (2 seconds or so) in streaming mode.
The ANSI colours and attributes are also rendered provided your browser supports cascading style sheets (CSS), which is the case for all the modern browsers.
In periodic refresh mode, the output window will show only the last 256 lines of text, starting from the point when you logged in (if you need a log, use the MUCK logging feature. See news logging). Long lines are automatically word-wrapped into shorter ones (80 characters per line max). The screen is scrolled automatically to the last line whenever a refresh is performed but in between refreshes you may scroll backwards without seeing it autoscrolled again every few seconds (unless the activity in the room is very high, of course).

This is where you can interact with the MUCK and control the chat screen. This frame got the following elements in it:

• The input line: it accepts up to 4096 characters and allows you to send one MUCK command at a time. For example, to say "Hello !", you type: say Hello ! or "Hello !
• The "Send" button: to send the command you typed in, you may either click on this button or press the ENTER key.
• The "Erase" button: when you press this button, the contents of the input line is cleared... and impossible to recover, so beware !
• The "Refresh" button: to reload the output frame independently of the automatic refreshing scheme.
  In periodic refresh mode you may use it if you are very impatient about seeing the result of a command you just sent (such as for displaying a document) and don't want to wait 5 seconds to see it. Note that in this mode the refresh will only occur if there is some buffered data waiting to be displayed, so pressing it will not always result in the output window being reloaded (while it would in streaming mode).
  There are also some occasions when browsers fail to refresh an auto-refreshing frame or break the streaming, like after resizing their window. Pressing this button will restart the auto-refreshing sequence.
• The "Quit" button: you should always press it before leaving the MUCK (i.e. before either closing the window or browsing to another site) as it is the only way to ensure that your character is disconnected properly. Should you fail to 'Quit', your character will stay uselessly connected to the MUCK until it boots it off (which happens after 4 hours of idling).
• The "Help" link: to display this page...

• Is it possible to avoid being teleported into the Park at each new connection ?
  Yes, simply set the zap2park? flag to "no", like this: @set me=_prefs/zap2park?:no

• Why didn't I get teleported into the Park this time ?
  Either you already set the flag as described above, or you logged in as a guest, or you were held into a bellyroom, or you were leashed/anchored (see sm #who), or you did not yet agree to the terms of the AUP.

• You say it refreshes every 10 seconds for the periodic refresh mode, or in near real-time (2 seconds or so) for streaming refresh, but it is so slow here... Why ?
  Well, there may be a couple of problems: first, you are perhaps behind a proxy, and proxies are the Great Evil for web chats, as they simply double the time needed for a refresh to reach you... If you can, disable your proxy (i.e. don't configure a proxy in your browser settings and use a direct connection). Second, my pipe to Internet is not that big... It is 512Kbps downlink/128Kbps uplink, which means that whenever my web server is sending data to users, the maximal bandwidth is 128Kbps... Unlike the telnet access to the MUCK, which I configured to keep a minimum reserved bandwidth with prioritary streams (which is enough to ensure a low lag even under the heaviest loads), I can't make the distinction between the requests for the webchat and the rest of my website (they all use the same port)... To make things simple, let's say that when someone downloads a big file from my web server (or when I upload a big file myself, as this is also my Internet link...), the replies to your requests for refreshing the chat may drop down to a crawl... The conclusion ?  Simple... gimme plenty of money to lease a big pipe to Internet, or use either a MUCK client (preferred), or the Java applets... :-P

• Why do I get a blank page when loging in with Firefox/Mozilla/Netscape ?
  Because the default configuration of the browser does not allow for more than two simultaneous HTTP connections to the same server, and the chat needs for three (in periodic refresh mode; streaming needs only for two and should work, but see below about multi-play)... Just enter "about:config" into the address bar of Firefox/Mozilla/Netscape and scroll down to the "network.http.max-persistent-connections-per-server" key, right ckick it, select "Modify", then enter a number of 3 or more (I'd recommend 6). Note that if you need to connect to VR with more than one character and use the web interface, you will need three (or two for the streaming mode) times as much persistent connections as characters... While you are at it, you may like to increase the numbers in the 3 keys before that one (unless you got a slow dialup connection to Internet, you may safely double the default figures). Once you are done, you must close all the windows of the browser and restart it for the new configuration to be taken into account.

• I do use a browser with streaming support, but after a while the streaming seems to timeout. Why ?
  Because either you resized your browser window, or you are behind a proxy which does not support streaming. In the first case, just click on the "Refresh" button once. In the second case, configure your browser for a direct connection to Internet (disabling any proxy configuration), and click on "Refresh" once.