NUTS 3.3.3 (final NUTS 3 version)

DOCS/about_config

@@ -45,7 +45,7 @@ ban_swearing - If YES then any speech, shouts or emotes said by a user that
 auto_connect - If YES then talker will try to connect to configured remote 
    sites when booted.
 
-logging - If YES then talker will write to the system log.
+system_logging - If ON then talker will write to the system log.
 
 password_echo - If YES then talker will echo passwords at login.
 
@@ -103,6 +103,8 @@ charecho_def - Either ON or OFF. Defines whether characters will be echoed
 time_out_afks - Either YES or NO. If yes then even users who are afk will get
    timed out if they idle for too long.
 
+time_out_maxlevel - Maximum level of user which can be timed out.
+
 allow_caps_in_name - YES or NO. If YES then users can have capital letters in
    their names , else everything gets converted to lower case except for the
    first letter which is always capitalised automatically.

DOCS/compiling

@@ -12,12 +12,12 @@ it seems to work fine though I have not done soak tests on these systems.
 
 To compile:
 
-Linux & AIX: cc nuts332.c
+Linux & AIX: cc nuts333.c
 IRIX & OSF : ditto above?
-HP-UX      : cc -Ae nuts332.c  (you need the ANSI compiler)
-SCO 3.2    : cc nuts332.c -lsocket -lcrypt_i  
-DYNIX 4    : cc nuts332.c -lsocket -lnsl
-Solaris    : cc -lsocket -lnsl nuts332.c  (not guaranteed to work)
+HP-UX      : cc -Ae nuts333.c  (you need the ANSI compiler)
+SCO 3.2    : cc nuts333.c -lsocket -lcrypt_i  
+DYNIX 4    : cc nuts333.c -lsocket -lnsl
+Solaris    : cc -lsocket -lnsl nuts333.c  (not guaranteed to work)
 SunOS 4    : dont even bother unless you have gcc
 
 Running...

DOCS/diffs

@@ -172,7 +172,7 @@ mess so I took it out again. See README for details.
 The talker now passes across the users level on a netlink so the use of 
 rem_user_maxlevel has been changed. This used to apply to remote users who had 
 a local account , it now only applies to those who *don't* have a local account
-users with local accounts have their level set to that of the local account 
+(users with local accounts have their level set to that of the local account 
 regardless) and rem_user_deflevel is only used to backwards compatability with
 older version servers that don't pass the user level.
 
@@ -219,3 +219,35 @@ Altered some of the command levels in .h file and increased MAX_LINES to 15.
 9. 
 Amendments and bug fixes including removing a large lump of code from 
 create_clone() that shouldn't have been there.
+
+
+3.3.3 (November)
+-----
+
+1.
+You now get a + indicator in the prompt if you are invisible. This indicates
+your *local* invisible state, it won't work on a remote site.
+
+2.
+Added time_out_maxlevel option to config file.
+
+3.
+Changed config file "logging" option to "system_logging" and it now takes
+ON and OFF as parameters rather than YES or NO. This is for consistency.
+
+4.
+The minlogin command now boots off any logged on users below the set level.
+
+5.
+Added has_room_access() function to replace some duplicated code.
+
+6.
+Swapped the positions of the help and home commands so that .h is now short
+for .help. This may cause slight confusion if people try to do .h on a 
+remote site to go home as they will be told that they are already on it.
+
+7.
+Bug fixes and general code amendments.
+
+
+*** THE END ***

DOCS/nuts_history

@@ -52,3 +52,5 @@ Chat server  Winter 92  (Original project code - never released)
 3.3.0        September 96
 3.3.1        October 96
 3.3.2        November 96
+3.3.3        November 96 (Final NUTS 3 version)
+

README

@@ -1,4 +1,4 @@
-*** README for 3.3.2 ***
+*** README for triple three (3.3.3 :) ***
 
 Read the DOCS/diffs file for update information.
 
@@ -16,18 +16,19 @@ ups and not only will I not reply to the mail but I will keep a note of your
 email address and I will not reply to *any* mails you send me even if its about
 problems with *my* code. Its your choice. 
 
-I've found out about a problem with the colour on a SCO console. For some 
-reason the terminal reset code does not reset the colours so they stay 
-effective until another colour is specified. No doubt there is a specific code 
-to do a colour reset but at the moment I don't know what it is. If you 
-are using SCO and have trouble you'll just have to make do with colour off or 
-use an xterm under X windows. Sorry. If anyone does know the code could you
-email it to me.
+I know I've said this before but this time I really mean it. This is the final
+version of NUTS 3. I have ideas in mind for a version 4 but thats years away
+so in the meantime this is it :) And to prove I mean it this is the first
+version of NUTS for a long long time without a backdoor in it as I'm sure 101
+hackers will test and find out to be true :)
+
+Unfortunately I still haven't found out what the colour reset code for
+SCO consoles and strict ansi terminals is so if you're using one of these 
+things may look messy. No one mailed me the code and the SCO terminfo 
+translation tools proved less than helpful so theres not much I can do. Sorry.
 
 Now go and read the DOCS/compiling file for info on how to get started if 
 you're new to NUTS and all the other files there will be usefull in time also.
-The auth lookup stuff that was in the readme in the 3.3.1 distribution has been
-moved to its own file in DOCS.
 
 Neil Robertson - November 1996
 
@@ -36,10 +37,8 @@ home page     : http://www.wso.co.uk/neil.html
 NUTS home page: http://www.wso.co.uk/nuts.html
 
 NB: If anyone is also interested in MUDs I've written a MUD system called 
-    Ogham - ftp.ccs.neu.edu:/pub/mud/servers/misc/ogham/ogham260.tar.gz
+    Ogham - ftp.ccs.neu.edu:/pub/mud/servers/misc/ogham/ogham262.tar.gz
     Its not as complex as perhaps LPmuds or Dikumuds are but if you know C and 
     want to set up a low to medium complexity mud then this is just what you 
-    need :) The final release of Ogham + mudlib (2.6.0) was released in early 
-    June but there is now a patch release which will upgrade you to 2.6.1
-    called ogham261_patch.tar.gz but I'm hoping to release 2.6.2 soon.
+    need :) 
 

datafiles/config

@@ -12,10 +12,10 @@ login_idle_time    180
 user_idle_time     600
 ban_swearing       YES
 auto_connect       YES
-logging            YES
 password_echo      NO
 ignore_sigterm     NO
 allow_caps_in_name YES
+system_logging     ON
 colour_def         ON
 prompt_def         ON
 charecho_def       OFF
@@ -28,6 +28,7 @@ rem_user_maxlevel  WIZ
 rem_user_deflevel  USER
 wizport_level      ARCH
 gatecrash_level    ARCH
+time_out_maxlevel  WIZ
 crash_action       REBOOT
 
 ROOMS:
@@ -43,4 +44,5 @@ lg lounge   co        BOTH ACCEPT
 # depends on how the /etc/hosts file is set up and also the resolver.
 SITES:
 talker2    localhost 5002    fred123 
+talker2    spirit 5002    fred123 
 

helpfiles/go

@@ -1,10 +1,12 @@
 
 * go *
 
-Usage: go <room>
+Usage: go <room/service> [<password on other talker>]
 
 This command moves you to another room which must be linked to your current
-one (unless you are a wizard or higher).
+one (unless you are a wizard or higher). If the talker is linked to another
+you can type the service name to move to the other talker if your password
+is the same on the other talker. If it isn't you must supply it as above.
 
 See: move
 

helpfiles/help

@@ -0,0 +1,8 @@
+
+* help *
+
+Usage: help [<command name>/commands/credits]
+
+This shows help for each command as well as showing a complete list of 
+commands and the code credits.
+