Basically everything I’ve been doing lately has been in support of the sheet. I’ve reached a fairly comfortable place when it comes to data entry and displaying that to players. I’m not great with the Evennia web stuff, so I’m trying to make sure there are utilities available within the client to view details. I might try to dive in to look at how to display these on the web. Theoretically it shouldn’t be reinventing the wheel since I’m just using python dicts. All of our data entry on Dies Irae was based around loading JSON files which ended up being fairly easy to incorporate into Django. I am fairly sure that’s why Kumakun decided on that route.
I reworked the +info from Dies Irae a little bit and have it displaying the data directly from the dictionaries. It seems to work… better than when we were importing from JSON? Cautiously? One of the big plus sides of nWoD/CofD is that there are fewer stats and, more importantly, fewer stats that are called exactly the same name. The big ones I’ve run into so far have been Mage spells having similar names to merits, but that’s easy enough to work around.
Some examples:
+lookup (the new +info) on its own:

Let’s look at Forces spells:

Let’s take a look at Control Heat:

Now let’s take a look at some Vampire powers. Let’s check out Animalism:

Let’s see what Summon the Hunt does and requires:

As an aside, the bottom is wrong. In this case I’m broadly using the lookup output method I use for Rites/Ceremonies/Gifts/Contracts/etc. for leveled powers like Disciplines. Animalism is tracked by using +stat animalism=<value>. If you wanted this specific power, you would do +stat animalism=3, or +xp/spend Animalism (three times). Then you would have Animalism 3, or the first through third level abilities.
So largely I took the information on Codex of Darkness to quickly fill this out. I’ve gone back through to verify that everything looks copacetic with regards to their book entries.
Oh yeah! I also took the “generic” commands from Dies Irae and put them into a folder. I also stripped out some of the overcomplicated bits from them that often caused them to fail miserably. For instance, I removed any web-based workflow from +finger so that it solely interacts with elements on the character db object. I wrote up a readme file explaining what to remove if you didn’t plan on using the PyReach/CofD system. There are only a handful of commands that rely on other things, most notably the say/emit/pose system and languages. In Dies Irae, and inherited into PyReach, you could speak a different language in poses and emits by using the tilde (~) key. You could, for instance, write out something like…
@emit Listening to John, Soma gives a short, curt nod and responds, “That all sounds workable.” They turn to Sam and say ~Where are we with the plans for tomorrow night on your side?
If I had my language set to Arabic, the text after the tilde and before terminating punctuation (question marks, periods, exclamation points) would display to anyone who also had Arabic set as one of the known languages, otherwise would show a general “something you don’t understand” message if someone did not have that language. This way you could flip back and forth out of the language by alternating between ~ and standard quotation marks.
If you’re not planning to use the language system – for example, if you aren’t using the characters.py
typeclass in PyReach – then there’s a small section in the pose/say/emit commands that you need to comment out, which I explain in the readme. I’m going to have another Evennia developer dummy test this to verify that it all looks okay – a lot of this stuff is Dies Irae code which was worked on a lot, but could be questionable at times – and hopefully would be a good, easy-to-implement command set for people who might be nervous about Evennia due to familiarity with Tiny/Penn.