LPMuds.net

I did this about 3 years ago, not sure why its not been sucked in, yours or mine, either would be nice
http://lpmuds.net/smf/index.php?topic=569.0

Would be helpful for mudconfig to show the values it sets and their current status.

(Not sure if mine still valid, mudconfig prob changed or gained some more values in 3 years)

Lima Login Flowpath

On player connection to mud, driver calls
object connect()
in /secure/master.c
->    attempts to return the USER_OB as defined by get_player_fname() in master.c
currently this is /secure/user.c as defined in /include/mudlib.h

Driver then calls
private nomask void logon()
in /secure/user.c from its inherited file /secure/user/login.c
->    this calls login_handle_logon(INITIAL_PROMPT, 0); in login.c which handles login using a switch command

NEW PLAYER
private nomask varargs
void login_handle_logon(int state, mixed extra, string arg)
->    This handles displaying the welcome info, getting name and passwords.
Control is passed to userinfo_handle_logon() in /secure/user/userinfo.c after confirming password.

protected nomask varargs
void userinfo_handle_logon(int state, mixed extra, string arg)
->   This gathers gender, email, real name, and webpage then control is passed to sw_body_handle_new_logon() in /secure/user/sw_body.c

protected nomask void sw_body_handle_new_logon()
->   This autowiz's if that flag is set, set the players priv's, and then calls create_body() in sw_body

void create_body()
->    If races are used, this gets the list and passes control to got_entry() in sw_body to let player choose their race.

void got_entry(function when_done, string line)
->   This handles the racial select, or relists them, or provides help information on a race. control is then passed to incarnate() in sw_body.c

private nomask void incarnate(int is_new, string bfn)
->   This function does several things. First it creates a body for them based on their racial pick.
Then it calls reset_parse_info in master.c which calls parse_refresh() (Not sure what this does)
Then it has the LAST_LOGIN_D log my name and ip
Then it sets my gender in the body
Then it saves me
Then it starts my shell
Then it calls enter_game in /std/body.c
->    This sets up cmd hooks, moves me to start room (defined in /std/body/start.c), announces entrance, makes me do a look and updates my health
    Then it runs a .login script for my shell, if I am a wizard
Then it calls init_stats in the /std/m_bodystats.c
Then it saves me again
Then it calls initialize_user which is back in /secure/user/login.c which initializes channels and shows the didlog

Now I am in game in the startroom playing.

It really appears to be Discworld, im struggling to find changes

Just cause I figure there are more folks than me out there who like to know such things, this is the flowpath a new player goes through during loing (hence where you would branch them off or change things to affect such things as racial choices, stat generation, etc).

Player Login flowpath

NEW PLAYER PATH
Driver calls connect() in master.c
/secure/daemon/master.c
object connect(int port)

Driver calls logon() in object returned by connect call
/secure/lib/connect.c
varargs static void logon(mixed foo)
static void InputName(string namen, string kill_me)
static void eventCreatePlayer(string cap)
static void ConfirmName(string ans, string cap)
static void AgeCheck(string ans, string cap)
static void CreatePassword(string pass, string cap)
static void ConfirmPassword(string control, string cap, string pass)
static void InputGender(string str, string cap)
static void InputCapName(string name, string cap)
static void InputEmail(string email)
static void InputRealName(string rname)
static void InputRace(string str)
static void cmdPick(string args)
void eventCompleteChar()
Player->SetRace(raza)
Player->SetProperty("brand_spanking_new",1)
Player->AddCurrency("silver",random(100)+57)
Player->SetRace(raza)
Player->SetPassword(Passwort)
Player->SetGender(Gendre)
Player->SetCapName(CapNamen)
Player->SetEmail(E_Mail)
Player->SetRealName(TrueName)
Player->SetLanguage("Common",100)
Player->SetDefaultLanguage("Common")
this_player()->SetWimpy(20)
this_player()->SetTerminal("ansi")
PLAYERS_D->AddPlayerInfo(Name)
static private void eventEnterGame()


Yeah, we caught some of that today when liveupgrade rename'd the dir containing .svn which broke svnup for a moment, had to patch that too to copy .svn/ back to /secure/upgrades/files/

Ok, some folks might appreciate a little example of why Bits are good to use.  The below example is for your standard room. This is not in DS, just an example, and is not public domain, but is so simple that you can make something like it without copying it.

Ok, so first I have a room.h file where I define my bits.
/******************************************************************************
File: room.h
Desc: Headers, bit, and flag settings for rooms.
******************************************************************************/

// Room bit inheritable
// The room_bits object has all room specific bit and flag settings.
#define ROOM_BITS               "/lib/room/room_bits"

// These are toggled bits for each room.  Usage is:
// void RoomBits_SetBit(int bit);   // set a bit
// void RoomBits_ClearBit(int bit); // clear a bit
// int RoomBits_TestBit(int bit);   // test if a bit is set
#define ROOM_BIT_SAFE_ROOM      0       // Room is safe: no combat, no spells
#define ROOM_BIT_INDOORS        1       // (unused)
#define ROOM_BIT_NOMOB          2       // NPC's cannot enter
#define ROOM_BIT_TUNNEL         3       // Only one player in room at a time
#define ROOM_BIT_NOSMELL        4       // Scents are not left in the room
#define ROOM_BIT_NOPRINTS       5       // No prints are left in the room
#define ROOM_BIT_NOTRACK        6       // Nothing can be tracked
#define ROOM_BIT_PRIVATE        7       // Can't teleport/trans into room
#define ROOM_BIT_NO_ATTACK      8       // Room is no attack
#define ROOM_BIT_NO_MAGIC       9       // Room is no magic
#define ROOM_BIT_NO_STEAL       10      // Room is no steal
#define ROOM_BIT_NO_SUMMON      11      // Room is no summon
#define ROOM_BIT_NO_TELEPORT    12      // Room is no teleport
#define ROOM_BIT_NO_SCRY        13      // Room is no scry
#define ROOM_BIT_SOUNDPROOF     14      // Room is cut off from lines, tells
#define ROOM_BIT_DEATH          15      // Player dies if they enter
#define ROOM_BIT_NO_AIR         16      // Gasp!  Need air to breathe!

Now that they are defined, when you create a room_bits.c that your LIB_ROOM (or base room) would inherit:
/********************************************************************
File: room_bits.c
Written By: Nevin
Desc: File to control room bit and flag settings in one location.
Much cleaner than before and provides for a standard method of
setting information for rooms.
********************************************************************/

#include <room.h>

string roomBits = "";           // room bit string var

/********************************************************************
Room Bit Code
********************************************************************/
// Sets a room bit
void RoomBits_SetBit(int bit)
{
   roomBits = set_bit(roomBits, bit);
}

// Clears a room bit
void RoomBits_ClearBit(int bit)
{
   roomBits = clear_bit(roomBits, bit);
}

// Tests a room bit
int RoomBits_TestBit(int bit)
{
   return test_bit(roomBits, bit);
}

Why create the room_bits.c? You don't have to, you can just include it in your base room, this is just for cleanliness sake.

Ok, so what do we gain by doing this? It saves a lot of memory over time, since one bit can hold 64 values (0 to 63) in just one character in the string.

Plus, in the old way, for each of the properties in rooms.h you would either need a seperate function (ie getIndeors() setIndoors() etc) or you would need to set each property (set_property("indoors",1));

By using bits though, you get one simple call to set them and one simple call to check em, and it takes up less memory and just looks cleaner. (RoomBits_SetBit(ROOM_BIT_NO_ATTACK)

You see if a bit is set with RoomBits_TestBit(ROOM_BIT_NO_ATTACK) and you can clear it with the clear_bit call.  This also makes code a lot easier to read as well.

Just my 0.02

Apparently some folks were deleting their posts and this upset Crat so he removed edit till he can fix it, but doesnt know when the fix is coming.