More documented examples possible via screenshots?

[rubyFeedback]

So I found this from your reddit link.

If you have some time, could you showcase examples for:

1. character creation
2. combat
3. inventory handling (wearing, removing)

I understand some of it may be empty or not much to show, but I think it would be useful in showing people what can be possible with the engine. Even if the above is super-simple; some of us old people used to know e. g. LPC and the inventory would look like:

"You are wearing a black robe."
"You are carrying a short dagger."

Second then being the inventory, indented one level to the right.

Also, are there events or triggers? For instance, if the character is thirsty etc... triggering automatic drinking.

[LimpingNinja]

Hi there!

Yes, triggers are throughout the mud and documented in trigger_system.md. There is a power hook system, event system, and trigger system built in. Most explained in the old HTML files path.

I'm actually from LPC myself, so I definitely understand. I'm working on two things right now:

1/A new help documentary with basic and mid-level tutorials on how to build. I have most of the documents created, but needing to clean them up.
2/A basic starter lib and a drop-in zone. These will be published separately, I have the zone created and working on the module.

Both should be done in a couple weeks.

For commands, all of the python libraries are under /lib -- documented here: https://github.com/NakedMud/nakedmud/blob/main/doc/game_library.md

This is similar, in a way, to the LPC mudlib concept but in a bit of a different and more controlled form. The "pymodules" are all the modules that either a/ call back to C (much like efuns); or b/ are instantiated and run in python (much like simul_efuns).

You will see in cmd_inform.py the first command programmed is cmd_inventory and cmd_equipment. These are the commands you would use to see what you wear and what you hold. Of course, since NakedMud is "Naked" there isn't any wear_type set up for anything beyond shirt. So to test you could "load o shirt@examples" and "wear shirt" to test. I will add more examples in the starter lib.

Another thing different is the way we store zones here, in LPC it's usually very open but often times mudlibs are arranged with a /d (domains) directory and people put domains in there. In NakedMud you have a /world path and that world has zones that are laid out in /lib/world/world file and the /lib/world/zones directory has subdirectories for each zone.

Items are referenced by @ whether object, mobile (npc), or room. Commands in game for OLC (like rlist, olist, mlist, zlist, tlist) etc. help you view these. You can edit them with <r/o/m/z/t>edit commands as well and reload with <r/m/o>reload and clone with load <o/m/r> name.

At the basis, when you edit with OLC it just creates the python prototype of the object, which is a python script. You can edit it, but if you edit it too much it might not work with the OLC anymore; but if you know what you are doing you can just write the python objects either. An example:

abstract: no
script  :~
  ### The following oproto was generated by oedit
  ### If you edit this script, adhere to the stylistic
  ### conventions laid out by oedit, or delete the top line
  
  ### keywords, short descs, room descs, and look descs
  me.keywords = "cheese, wheel, aged, dairy, food"  + ", " + me.keywords
  me.name     = "a wheel of cheese"
  me.mname    = "a pile of %d wheels of cheese"
  me.rdesc    = "A wheel of cheese sits here."
  me.mdesc    = "%d wheels of cheese sit here."
  me.desc     = me.desc + " " + "This aged cheese wheel has a firm golden rind and creamy interior. \r\nThe cheese has been aged to perfection, developing a rich, nutty \r\nflavor that pairs well with bread and ale.\r\n"
  
  ### numeric values
  me.weight   = 3.000
-

This is an oproto or object prototype, it's simple, another example is scripting. You can add extra code to any object in oedit or whatever command and it would show up in the above prototype as extra code, or you can add a trigger. For example, mysty has a "Greet" trigger attached (mysty_greet) that looks like this:

name: mysty greets new players
type: enter
code:~
  # Entrance script no. 2 - greeting characters. This script is intended to
  # be attached to Mysty (mob vnum 100). When she meets someone for the
  # first time, she will greet that person and flag him/her as having been met
  
  # check to make sure that:
  #   a) this is a PC
  #   b) we've never met the person before
  if ch.is_pc and not ch.hasvar("met_mysty"):
  
    # send different message to different gendered characters
    if ch.sex == "male":
      me.act("say Well hello there, darlin'. I've never had the pleasure of " \
             "seeing your pretty face around these parts. If you need a hand, " \
             "or perhaps a drink, just ask me for help.")
    else:
      me.act("say Welcome to the Stuck Swine! I hope it's to your liking here. " \
      "If you need a hand, or perhaps a drink, just ask me for help.")
    
    # set a variable so we know we've met Mysty before
    ch.setvar("met_mysty", 1)
  
-

Anyways, it seems very complext, but I agree with you overall and I will add examples :-)

[LimpingNinja]

#9

#10

These were created to track.