By displaying "<DISABLED>" instead of the command-line in the event list.

It appears this was written for RTWall to detect BBS numbers with.

- Have getsvar() join arguments with spaces for strings
- Fix fg/bg in @readstring/@readnum
- Special-case NIL in readstring (this is where it's documented)

- Set default values for world.dat so it can be created with new()
- Add `r0 to start of the default more string
- Create the world file if it doesn't exist (for globals)
- Fix stupid error in @do trim
- Support all the different @clear commands
- Support the different @key commands properly
- Support @name command
- Only @say is still required for the NPC "stuff" that nothing uses
- Fix blank line skip looking for @begin after @if...then do
  Was looking for comments starting with ; only
- Add try/catch around maint call in case it doesn't exist
- Don't load rules.ref if there's a REF passed on command-line

Was broken the same way as Christopher Robin's House.

Previously dumped you on an uninitialized map, not returns you to the
hundred acre wood as intended.

In general, LORD2 ignores errors and continues, but various things
will cause exceptions to be thrown.  Instead of tracking all these
down and suppressing them, log them to error.log and continue.

Since we're doing this, we can now throw Error()s whenever we
detect an issue in REF files, so add some of these in.

See if this resolves rjwboys reported error:
threadwrap.h:204:42: error: expected expression before ‘do’
 #define protected_uint32_init(pval, val) atomic_init(pval, val)

Hope to address error reported by rjwboys via IRC when using
gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.12)
 from ansiterm.cpp:22   /user/include/c++/5/bits/c++0x_warning.h:32:2
error #error this file requires compiler and library support for the ISO C++ 2011 standard. This support must be enabled with the -std=c++11 or -std=gnu++11 compiler options.

Calling @routine blew up the stack, so presumably this needs to be
done everywhere.

This excludes votes and polls automatically.

e.g. ANSI.SYS doesn't appear to support it

I'm not sure how long this has been like this, but the last_msg
of a sub-board can be a super high number (e.g. in the billions), so using
that value as the highest message offset would cause tons of message index
read failures and just cause this loop to interate unneccessarily through
tons of non-existent messages. Also, this code is utter crap.

SBBS v3.19 introduces a built-in FileBase class. To resolve this
conflict, rename the soon-to-be-deprecated FileBase object to
OldFileBase.

This option fixes the fact that the following two lines sometimes
place the variables in different scopes at the top-level of included
scripts:
var x = 1;
y = 2;

I plan to use this to experiment on if this is what's causing much
of the remaining scope chain weirdness... it certain explains some
things we've been seeing (and possibly even things like the METHODJIT
issues DigitalMan saw yesterday).

Enabling in sbbs/jsexec is a much bigger lift, but this change may
end up being all upside... the docs have suggested this option always
be set since it was originally introduced, and now that I understand
scopes better, it's pretty clear why that is.

May fix an issue when dead players enter the game?

METHODJIT (JägerMonkey) is doing weird stuff with xtrn_sec.js when
enabled, so don't introduce that noise.

This was the bit that irritated me the most about CNW, so I fixed
it.

You can copy this whole thing over your LORD2 install, or copy/symlink
the JS files in here and run it here.

Complete New World is a massively expanded LORD2 world, but it has
not been nearly as well-tested with the JS implementation.