MU Soapbox

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Muxify
    • Mustard

    Coder needed for nwod 2.0 mu

    MU Questions & Requests
    6
    25
    6935
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Thenomain
      Thenomain @Thenomain last edited by

      The core code should be updated. Please let me know if I missed something or if something changed between WoD and CoD and I missed it. Thanks.

      “If you wish to make an apple pie from scratch, you must first invent the universe.”
      ― Carl Sagan, Cosmos

      S 1 Reply Last reply Reply Quote 0
      • S
        Sammi @Thenomain last edited by

        @Thenomain said:

        The core code should be updated. Please let me know if I missed something or if something changed between WoD and CoD and I missed it. Thanks.

        Will do. You'll see some pull requests if I find anything. 🙂

        It seems mostly straightforward, but I have one question. In "0 - Introduction.txt" you say,

        Tags are meant to be used by higher game systems to determine validations. ... Tags are never used for storage.

        In "1c - Tags.txt", the first words are

        Tags for the Core WoD stats.
        (Later, use this for page number and note references)

        Those two statements of intent sound conflicting, unless I'm thinking more broadly than you were about what constitutes storage.

        Thenomain 1 Reply Last reply Reply Quote 0
        • Thenomain
          Thenomain @Sammi last edited by Thenomain

          @Sammi

          That's a note to self. I'll probably have a 'reference' object for the notes et al. What it's meant, though, is that &tags.<statpath> are not to store data, only references. What I consider a "reference" may not be consistent but a tag in my code is a way to determine if a trait has a certain flavor. A template it belongs to, if it's chargen-only, if it's physical or mental, etc.

          I have thought about splitting out some of those things. Say a 'templates.<statpath>' attribute for 'werewolf.rahu' or 'human.ghoul.stigmatic' or in rare occasion something like 'changeling.darkling.shadowsoul'.

          The point of pulling 'tags' from the main data dictionary is to not hit some of a Mu*'s hard limitations, and to ease up on the lbuf limitation for analyzing a statpath. I really should have an object for raw stats, one for prereqs and tags, and one for references and notes. Maybe. Maybe not.

          Anyhow, the old system had &page.<statpath> which was kind of a note, except sometimes it got out of hand. 'wod.56-8|ctd.12-3|wtf.argle-bargle', you get the idea. I haven't re-implemented it fully for reasons that remain "it's work".

          “If you wish to make an apple pie from scratch, you must first invent the universe.”
          ― Carl Sagan, Cosmos

          1 Reply Last reply Reply Quote 0
          • boneghazi
            boneghazi last edited by

            Youre amazing theno, thank you!

            The road to hell is paved with adverbs.

            Thenomain 1 Reply Last reply Reply Quote 0
            • Thenomain
              Thenomain @boneghazi last edited by

              @nyctophiliac said:

              Youre amazing theno, thank you!

              Wait for the praise until you try to install it. The best I can say at the moment is that it's available.

              “If you wish to make an apple pie from scratch, you must first invent the universe.”
              ― Carl Sagan, Cosmos

              1 Reply Last reply Reply Quote 0
              • 1
              • 2
              • 2 / 2
              • First post
                Last post